+1 On Thu, Oct 23, 2014 at 7:01 AM, Berner Martin <martin.ber...@qualitasag.ch> wrote:
> Hi Romain > Ok. Think I live with TomEE+ for JAX-WS-Projects and TomEE-JAXRS for the > Rest of our Applications. - Quite simpler :-) > > About Footprint: didn't check differences between same App running on PLUS > vs. JAXRS. Only thought because of view more jars potentially loaded and so > using more RAM, blabla .. :-) > I'm happy with TomEE anyway :-) Grate Project! > > Martin > > > > -----Ursprüngliche Nachricht----- > Von: Romain Manni-Bucau [mailto:rmannibu...@tomitribe.com] > Gesendet: Donnerstag, 23. Oktober 2014 10:08 > An: users@tomee.apache.org > Betreff: Re: migrating jax-ws Application vrom TomEE-Plus To TomEE-JAXRS > > 2014-10-23 9:52 GMT+02:00 Berner Martin <martin.ber...@qualitasag.ch>: > > Hi Romain > > > > do you have/know a concrete Sample? > > EJB is not a must have. Configuring with CDI would be the better Joys > for us anyway. > > > > Not yet and cxf integrated CDI only for 3.x so will not be working out of > the box AFAIK but lookup then delegation should be easy. > > > Shure I know the other way around it is done with now work. But TomEE+ > is not EE6 certified which is one argument and the other is, that most of > our applications, expect two, runs on JAXRS which has also the smaller > footprint. > > > > Mainly curiosity: > 1) do you have figures of this footprint difference if you speak about RAM > (not sure disk difference is important enough to be an argument ;))? > 2) EE6 certification: it is not certified cause we add JMS, connectors > etc...but before releasing we ensure same tests pass for plus distribution > and jaxrs one so why is it a drawback? > > > > > Martin > > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Romain Manni-Bucau [mailto:rmannibu...@tomitribe.com] > > Gesendet: Donnerstag, 23. Oktober 2014 08:21 > > An: users@tomee.apache.org > > Betreff: Re: migrating jax-ws Application vrom TomEE-Plus To > > TomEE-JAXRS > > > > Hi > > > > You need to define the webservice as a pojo, configure it in web.xml > with cxf servlet, import cxf jaxws jars and finally delegate to the > stateless if you really need an ejb. > > > > Side note: harmonizing on tomee+ is clearly easier since it is no work > migration normally Le 23 oct. 2014 07:54, "Berner Martin" < > martin.ber...@qualitasag.ch> a écrit : > > > >> Hi, > >> I have a JAX-WS Application working perfectly on a TomEE-PLUS. > >> SOAP-Webservice correctly recognized by Annotation in a EJB: > >> > >> @Stateless > >> @WebService(name = "LBEQualitasService", > >> portName = "LBEQualitasPort", > >> serviceName = "LBEQualitasService", > >> targetNamespace = > >> "http://wsdlc.business.fsho.com/";) > >> @XmlSeeAlso({ > >> ObjectFactory.class > >> }) > >> public class LBEQualitas implements ServicesPortType, Serializable { > >> private static final long serialVersionUID = > >> -1959730900195946000L; > >> > >> > >> For harmonization reason I'd like to let them run on TomEE-JAXRS. > >> > >> Is there a simple sample, how to do such a "migration". > >> I know it's not as simple as just deploy the relevant cxf-jars with > >> the Application. > >> > >> Best Regards > >> Martin Berner > >> > -- Daniel Cunha (soro) <http://www.cejug.net> Blog: http://www.danielsoro.com.br Twitter: https://twitter.com/dvlc_ GitHub: https://github.com/danielsoro LinkedIn: http://www.linkedin.com/in/danielvlcunha
