Thanks for posting guys (gals?), the additional insight helps a great deal.

asack, I can assure you I've practically memorized that portion of the wiki!  
Admittedly, reading and understanding are two different things.  What you 
stated, about packaging the war and a jar of all ejbs together inside an ear, 
is what I've been using per the wiki.  Unfortunately, it's still not working.  
From my original post, I've placed my persistence.xml file in the META-INF 
directory of my ejbs.jar file in that setup.  Here's my application.xml file:

  | <?xml version="1.0" encoding="UTF-8"?>
  | <!DOCTYPE application PUBLIC
  |    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
  |    "http://java.sun.com/dtd/application_1_3.dtd";>
  | <application>
  |    <display-name>Alpha (Voltaire) Enterprise Application</display-name>
  |    <module>
  |       <web>
  |          <web-uri>Voltaire.war</web-uri>
  |          <context-root>/Voltaire</context-root>
  |       </web>
  |    </module>
  |    <module>
  |       <ejb>ejbs.jar</ejb>
  |    </module>
  | </application>
  | 

And here is the faces-config.xml file (is there a reason the use of managed 
beans would be a problem, as long as I do the proper context lookup from a jsf 
file?):
<?xml version="1.0" encoding="UTF-8"?>
  | 
  | <!DOCTYPE faces-config PUBLIC
  |   "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
  |   "http://java.sun.com/dtd/web-facesconfig_1_1.dtd";>
  |   
  |   
  | <faces-config>
  |     <application>
  |         <locale-config>
  |           <default-locale>en</default-locale>
  |         </locale-config>        
  |     </application>
  | 
  |   <factory>    
<application-factory>org.apache.beehive.netui.pageflow.faces.PageFlowApplicationFactory</application-factory>
  |   </factory>
  | 
  |     <managed-bean>
  |             <managed-bean-name>rmBean</managed-bean-name>               
  | 
<managed-bean-class>com.test.gems.requirements.RequirementsManagerBean</managed-bean-class>
  |             <managed-bean-scope>session</managed-bean-scope>
  |     </managed-bean> 
  | </faces-config>

Now, if I were to use an ear configuration like elkner, would the following 
work?
application.xml:
<?xml version="1.0" encoding="UTF-8"?>
  | <!DOCTYPE application PUBLIC
  |    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
  |    "http://java.sun.com/dtd/application_1_3.dtd";>
  | <application>
  |     <display-name>Alpha (Voltaire) Enterprise Application</display-name>
  |     <module>
  |             <web>
  |                     <web-uri>Voltaire.war</web-uri>
  |                     <context-root>/Voltaire</context-root>
  |             </web>
  |     </module>
  |     <module>
  |             <ejb>entities.jar</ejb>
  |     </module>
  |     <module>
  |             <ejb>ejb-interfaces.jar</ejb>
  |     </module>
  |     <module>
  |             <ejb>ejbs.jar</ejb>
  |     </module>
  | </application>

I would assume the managed bean file would remain the same.


>From this posting:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76538&view=next
I'm wondering if the ordering of deployment is a problem.  Should I alphabetize 
my application.xml file so that the war is loaded before the ejbs?  Ejbs before 
war?  

This wiki listing: 
http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/entityconfig.html#ear
states that, at least as of RC4, the Java EE 5 format is not supported.  Also, 
the section on referencing the global jndi shows a persistence unit "manager1" 
that scopes a particular entity manager...is this different than the 
"requirements" persistence unit I listed in my first posting?  In other words, 
do I need to include both those particular properties is whatever data source 
I'm registering?  None of the RC5 examples/tutorials show these being used, and 
I presumed these were newer than the documentation.  Instead, they all include 
the "hibernate.hbm2ddl.auto" and "hibernate.dialect" properties.  Do I need a 
separate hibernate and jndi factory PUs?


elkner:
Thanks for your reply--that implies that JBoss is in fact compliant with the 
J2EE spec regarding ears, contrary (depending on the version) to what asack has 
mentioned.  Which version are you using?  I know I asked if anyone had this 
working with the latest version, but I should have specified an RC rather than 
something like a nightly build of 5.0 alpha.   Also, you don't have a war 
packaged in your ear...would the addition of the war be the part that would 
cause a problem?  

I'd be very interested in seeing the application.xml (if used) of someone using 
a war to successfully access ejbs (either using the /lib/.jar configuration or 
just stuffing everything into /<all-ejbs>.jar).  

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931353#3931353

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3931353


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to