>Are you talking about vendor specific deployment descriptors? If so,
there
>shouldn't be a problem having them all bundled, as JBoss AS will ignore
the
>WLS specific DD for example. However, if you need different
configurations
>(the same file but in a different flavor) that's a different story.
Yes, that is part of it. I was not aware that you can combine them.
For example. Here is an example of one of our EJBs. Are you saying this
can be combined? I apologize if this is a newbie question. I'm SCM
person not a Java one. Thanks for your help!!! David
jboss.xml:
<jboss>
<enterprise-beans>
<session>
<ejb-name>myServiceLocal</ejb-name>
<local-jndi-name>ejb/myServiceLocal</local-jndi-name>
</session>
<session>
<ejb-name>myService</ejb-name>
<jndi-name>ejb/myService</jndi-name>
<container-invoker-conf>
<optimized>true</optimized>
</container-invoker-conf>
<port-component>
<port-component-name>EventService</port-component-name>
<port-component-uri>/my-ejb-service/*</port-component-uri>
</port-component>
</session>
</enterprise-beans>
</jboss>
weblogic-ejb-jar.xml:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90";
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd";>
<weblogic-enterprise-bean>
<ejb-name>myServiceLocal</ejb-name>
<local-jndi-name>ejb/myServiceLocal</local-jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>myService</ejb-name>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>ejb/myService</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
