-
1. Re: ear deployment order
ioparra Sep 26, 2003 4:57 PM (in response to ioparra)The eardeployer is reading the application.xml into a hashset and is iterating over the hashset. That iterator loses the ordering in the hashset.
I've posted in the Deployment section for changing hashset to arraylist. -
2. Re: ear deployment order
raja05 Sep 26, 2003 6:19 PM (in response to ioparra)Can you try having a depends clause in jboss.xml so that the beans depend on each other,
For e.g, Bean B can have a depends like
jboss.j2ee:jndiName=BeanA,service=EJB
and bean c can have
jboss.j2ee:jndiName=BeanB,service=EJB
-Raj -
3. Re: ear deployment order
ioparra Sep 29, 2003 1:08 PM (in response to ioparra)Thanks Raj. I'm figuring since the EJB become Mbeans, this depends part will work.
That'll mean I'll have to modify my xdoclet results after the descriptors are generated. Oh well..
As far as my previous statement, making the metadata use an ArrayList instead of a HashSet won't work. Ultimately, the Ear deployer sets each jar a subdeployer in set list. This set is also a hashset. Ordering is lost there to. :)
Thanks Raj!
-Ivan -
4. Re: ear deployment order
raja05 Sep 29, 2003 1:25 PM (in response to ioparra)One thing u can do instead of tweaking the descriptor is maybe use a XDoclet merge file instead of letting XDoclet create the file for the Beans which have dependencies. Too bad Xdoclet cant generate them.
One way or other, you have to generate the XML :-(