Hello all,
Since 4 days I'm struggling with websphere to deploy an
ear file. I've used XDoclet 1.2b2 with the following options:

...
      <ejbdoclet
         destdir="${build.generate.dir}"
         excludedtags="@version,@author"
         ejbspec="${ejb.version}"
         mergedir="${src.resources.dir}/xdoclet"
         force="${xdoclet.force}"
      >
         <fileset dir="${src.ejb.dir}">
            <include name="**/*Bean.java"/>
         </fileset>

         <remoteinterface/>
         <homeinterface/>
         <deploymentdescriptor destdir="${build.dir}/META-INF"
          useIds="true"
         />

         <websphere
            xmlencoding="UTF-8"
            destdir="${build.dir}/META-INF"
            validateXml="false"
            useIds="true"
         />
      </ejbdoclet>
...

After analyzing the DD generated by XDoclet here is what I've found:
In the ibm-ejb-jar-bnd.xmi file I've got those tags:
...
   <ejbJar href="META-INF/ejb-jar.xml#ejb-jar_1"/>

      <ejbBindings
         xmi:id="Session_bnd_1"
         jndiName="ejb/AdminDispatcher">

         <ejbRefBindings xmi:id="EJBRefBnd_1" jndiName="ejb/Admin">
            <bindingEjbRef href="META-INF/ejb-jar.xml#EJBRef_1"/>
         </ejbRefBindings>
         <ejbRefBindings xmi:id="EJBRefBnd_2" jndiName="ejb/IdentityManager">
            <bindingEjbRef href="META-INF/ejb-jar.xml#EJBRef_2"/>
         </ejbRefBindings>

         <enterpriseBean
            xmi:type="ejb:Session" href="META-INF/ejb-jar.xml#Session_1" />
      </ejbBindings>
...

and in ejb-jar.xml:
...
<ejb-jar id="ejb-jar_1">

   <description><![CDATA[No Description.]]></description>
   <display-name></display-name>

   <enterprise-beans>

      <!-- Session Beans -->
      <session id="Session_AdminDispatcher">
         <description><![CDATA[]]></description>

         <ejb-name>AdminDispatcher</ejb-name>

         <home>fact.ejb.admindispatcher.AdminDispatcherHome</home>
         <remote>fact.ejb.admindispatcher.AdminDispatcher</remote>
         <ejb-class>fact.ejb.admindispatcher.AdminDispatcherBean</ejb-class>
         <session-type>Stateless</session-type>
...

Conclusion:
-1- according to a the SampleApp.ear file (part of WebSphere 4.0) and the DD inside,
shouldn't "xmi" be replaced by "xsi"?

-2- Why are the IDs used in ejb-jar.xml and in ibm-ejb-jar-bnd.xmi
different?

Thanks for any comment,
Loïc




This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

                ---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to