Correct. We used JSR181 annotations and are exposing three end points in one .ear (.war contained in an .ear). XFire is pretty agnostic to the container it runs in, which is why you've heard mention of Jetty, Tomcat, etc. We used Spring 1.2.x and XFire 1.0 (haven't upgraded yet) without much of any problem.
Cheers & good luck in your evaluation, Brice On 2/7/07, Fred Lamuette <[EMAIL PROTECTED]> wrote:
For consuming and exposing web services at the web container level? > -----Message d'origine----- > De : Ruth, Brice D [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 7 février 2007 21:39 > À : [email protected] > Objet : RE: [xfire-user] Jboss-ws alternative > > I cannot speak much to how xfire/ejbs work together in JBoss, > but xfire itself runs fine in JBoss 4.0.3/4.0.5, no problems here. > > Cheers, > Brice > > -----Original Message----- > From: Fred Lamuette [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 07, 2007 2:30 PM > To: [email protected] > Subject: [xfire-user] Jboss-ws alternative > > > Hi all, > I'm evaluating several soap stacks, and xfire is particulary > attractive. > > But I have constraints : > - Jboss 4 but jdk1.5 and ejb3 extension > - stateless ejb3 end point > > Has someone feedbaks about integration of xfire in jboss ? > Thank you. > R > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- Brice Ruth Software Engineer, Madison WI
