Steps to reproduce:
- Create any application targeted WebSphere server
- Open any server specific DDs under Configuration Files node
- Switch to XML mode
- Try to validate its XML
- RESULT: The following output is shown:
XML validation started.
cvc-elt.1: Cannot find the declaration of element 'ejbbnd:EJBJarBinding'. 
XML validation finished.
Nowdays we have no *exact* schema for WebSphere DD (IBM doesn`t provide it in
We would create it manually on the basis of information collected from various
Let's do it later.
By "in free access" I assume you mean they're not on the web or under a freely redistributable license?
Can't they just be loaded from the properties\schemas directory under the installation directory
selected when adding the app server to the Servers list? Is it really all that much different
to the way the j2ee.jar is located for compiling the java code?
There's a whole bunch of .xsd files under
C:\Program Files\IBM\SDP70\runtimes\base_v6\properties\schemas on my machine, including
the webapp ext & bnd ones. The advantage of locating these relative to the j2ee platform
settings is that if there are any incompatible changes in the schemas between WAS versions,
validation can be done with the appropriate set for the target environment. The down side
is that changing to a different server type (e.g. Tomcat) means you can no longer validate
any existing ibm-web-bnd.xmi etc. files in the project, but that's no worse off than the
Hmm... last updated Jun 5 2006. Is it LATER yet? :-)
By "free access", the issue is IBM's copyrights and what the distribution rights are. Barring evidence to the contrary,
it is reasonable to assume that IBM does not grant free distribution rights to these files.
That said, it is possible to construct a server plugin that dynamically adds WebSphere's DTD's to the DTD Registry in
the IDE from a known location in a WebSphere install provided by the end user.