The way I've done it a few times is to just have the axis2 service make ejb client calls. There are a few ways to handle the deps issue, but keep in mind you can have an AAR with only the services.xml , therefore putting your service / pojo classes in lib along with all the rest of the deps. You can also use spring inside the AAR to handle the ejb stuff.
HTH, Robert On 12/27/06, Brian Quirk <[EMAIL PROTECTED]> wrote:
Hi - I've reviewed the online documentation and this mailing list, but still have a few questions as to the best way to integrate axis2 with an existing J2EE application that is packaged as an EAR. The end goal is to expose some of the POJOs that are packaged in the EAR. FWIW, the POJOs tend to have a lot of dependencies on additional framework code (caching, data layer, 3rd party jars, etc) contained within the EAR. To a newbie like me, it would appear that these dependencies make dropping .AARs onto the axis2.war (outside of the EAR) prohibitive. I figure this is a common scenario so I'm curious as to how others have introduced axis2 into an existing enterprise application. For example, should I rebuild axis2.war with my .AAR included and then add axis2.war to my EAR so it can take advantage of the shared resources? To give you an idea of where I'm at -- I have successfully deployed the axis2.war in exploded format on weblogic 8.1 and executed some of the sample web services. Thanks In Advance, -Brian __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
