I'm using Sun's petstore WAF to develop a new app and have come across some strange behavioral issues when dealing with some of its components with JBoss.
There's a main Controller SFSB that creates a users SFSB that basically controls the whole EJB interactions. The packaging is broken down into several small jars which contain mostly somegroup-ejb and somegroup-ejb-client.
It seemed to be working pretty well until my last deployment. There's one somegroup-ejb jar that fails to initialize properly (i.e., no data is returned and no error is thrown) unless the code is changed every time it's deployed. I think it has something to do with the stateful sb controlling the facade. It seems like it references the session dir and pulls up the old class.
Has anyone experienced anything similar? Does anyone know if there's a way to stop this from occurring? Is there something that I may be doing wrong?
Any help is appreciated.
Thanks, Graham [ April 20, 2006: Message edited by: graham king ]
I've been trying to separate the components into logical groupings. This being the first time I've ever used CMP's I made a severe mistake. I referenced the problem ejb in both ejb-jar.xml deployment descriptors and by doing so created the ever living un-maintainable ejb.
So I factored it out of one of the jars which was overkill in the first place and all is well.
[ April 20, 2006: Message edited by: graham king ]
HA - [ April 20, 2006: Message edited by: graham king ]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com