RE: OT: Web Services
Good point Peter. I'll see if I can fit this in, though my work will be more migration from XFire to CXF, and using another filter to intercept ws calls, rather than the Tapestry filter, so not sure if it really counts as "integrating" with Tap. The code I've inherited is using a lot of Spring beans, though I've injected some T5 services into those ... Regards, Jim. -Original Message- From: Peter Stavrinides [mailto:p.stavrini...@albourne.com] Sent: 30 August 2010 14:36 To: Tapestry users Subject: Re: OT: Web Services ... sorry to leach on this thread, but perhaps a short blog on integrating Metro or CXF with Tapestry would be useful. cheers, Peter - Original Message - From: "Kristian Marinkovic" To: "Tapestry users" Sent: Monday, 30 August, 2010 16:22:40 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: OT: Web Services hi, i use a (JaxWS)HttpServletRequestFilter service to intercept WS calls to my application. it will only intercept calls that have the url pattern of the provided WS that can be configured. and i'm using metro too. we switched from cxf to metro because it was easier to work with jaxb-binding overrides... g, kris Von:Peter Stavrinides An: Tapestry users Datum: 30.08.2010 14:59 Betreff:Re: OT: Web Services Hi Jim I evaluated quite a few Java WS stacks and was between CXF and Metro, but in the end I chose metro, but to be honest there was very little to choose btw the two... so I would suggest those two as the leading Java WS stacks. Both support maven and are very complete in terms of how much of the web service set of standards they support. Metro implements JAXWS 2.1 and JAXB2.2, so if the marketing babble is to be trusted its 'meant' to be higher performing and more extensible, but I haven't tested that claim yet. In any event it has an impressive array of security features. It also ships with the standard glassfish installation, which means no server configuration is needed if you go that route, I installed it though with Tomcat, it was as easy as executing a script... not too hard at all. Depending how you wish to approach you applications, you can use annotations for the meta programming, and avoid a lot of the messy xml. I found it to be really clean and the closest to Microsofts .Net platform implementation which is IMHO a very good implementation of Web Services ...at least more impressive than anything I have seen in the Java community, but I feel the gap is closing slowly. To integrate with Tapestry I simply overrode Tapestry filter... I am not aware of any more elegant approach, although I made a few inquiries on this list in the past. Cheers, Peter - Original Message - From: "Jim O'Callaghan" To: "Tapestry users" Sent: Monday, 30 August, 2010 10:52:44 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: RE: OT: Web Services Kalle, Daniel, Thanks for the responses. Good to know that there are positive experiences with CXF. It's probably the front-runner for me at the moment, but will keep an ear open for any other feedback. Looking at my original query I can see that it looks like I am focusing on generating WS clients - I should have said "providing interfaces for a system" rather than "interfacing with a system". Regards, Jim. -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 30 August 2010 03:43 To: Tapestry users Subject: Re: OT: Web Services Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >>
RE: OT: Web Services
This is stellar stuff guys - you're saving me a lot of headaches. Thanks. Regards, Jim. -Original Message- From: Peter Stavrinides [mailto:p.stavrini...@albourne.com] Sent: 30 August 2010 14:36 To: Tapestry users Subject: Re: OT: Web Services ... sorry to leach on this thread, but perhaps a short blog on integrating Metro or CXF with Tapestry would be useful. cheers, Peter - Original Message - From: "Kristian Marinkovic" To: "Tapestry users" Sent: Monday, 30 August, 2010 16:22:40 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: OT: Web Services hi, i use a (JaxWS)HttpServletRequestFilter service to intercept WS calls to my application. it will only intercept calls that have the url pattern of the provided WS that can be configured. and i'm using metro too. we switched from cxf to metro because it was easier to work with jaxb-binding overrides... g, kris Von:Peter Stavrinides An: Tapestry users Datum: 30.08.2010 14:59 Betreff:Re: OT: Web Services Hi Jim I evaluated quite a few Java WS stacks and was between CXF and Metro, but in the end I chose metro, but to be honest there was very little to choose btw the two... so I would suggest those two as the leading Java WS stacks. Both support maven and are very complete in terms of how much of the web service set of standards they support. Metro implements JAXWS 2.1 and JAXB2.2, so if the marketing babble is to be trusted its 'meant' to be higher performing and more extensible, but I haven't tested that claim yet. In any event it has an impressive array of security features. It also ships with the standard glassfish installation, which means no server configuration is needed if you go that route, I installed it though with Tomcat, it was as easy as executing a script... not too hard at all. Depending how you wish to approach you applications, you can use annotations for the meta programming, and avoid a lot of the messy xml. I found it to be really clean and the closest to Microsofts .Net platform implementation which is IMHO a very good implementation of Web Services ...at least more impressive than anything I have seen in the Java community, but I feel the gap is closing slowly. To integrate with Tapestry I simply overrode Tapestry filter... I am not aware of any more elegant approach, although I made a few inquiries on this list in the past. Cheers, Peter - Original Message - From: "Jim O'Callaghan" To: "Tapestry users" Sent: Monday, 30 August, 2010 10:52:44 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: RE: OT: Web Services Kalle, Daniel, Thanks for the responses. Good to know that there are positive experiences with CXF. It's probably the front-runner for me at the moment, but will keep an ear open for any other feedback. Looking at my original query I can see that it looks like I am focusing on generating WS clients - I should have said "providing interfaces for a system" rather than "interfacing with a system". Regards, Jim. -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 30 August 2010 03:43 To: Tapestry users Subject: Re: OT: Web Services Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > - To unsubscribe, e-mail: users-unsubscr...@t
Re: OT: Web Services
... sorry to leach on this thread, but perhaps a short blog on integrating Metro or CXF with Tapestry would be useful. cheers, Peter - Original Message - From: "Kristian Marinkovic" To: "Tapestry users" Sent: Monday, 30 August, 2010 16:22:40 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: OT: Web Services hi, i use a (JaxWS)HttpServletRequestFilter service to intercept WS calls to my application. it will only intercept calls that have the url pattern of the provided WS that can be configured. and i'm using metro too. we switched from cxf to metro because it was easier to work with jaxb-binding overrides... g, kris Von:Peter Stavrinides An: Tapestry users Datum: 30.08.2010 14:59 Betreff: Re: OT: Web Services Hi Jim I evaluated quite a few Java WS stacks and was between CXF and Metro, but in the end I chose metro, but to be honest there was very little to choose btw the two... so I would suggest those two as the leading Java WS stacks. Both support maven and are very complete in terms of how much of the web service set of standards they support. Metro implements JAXWS 2.1 and JAXB2.2, so if the marketing babble is to be trusted its 'meant' to be higher performing and more extensible, but I haven't tested that claim yet. In any event it has an impressive array of security features. It also ships with the standard glassfish installation, which means no server configuration is needed if you go that route, I installed it though with Tomcat, it was as easy as executing a script... not too hard at all. Depending how you wish to approach you applications, you can use annotations for the meta programming, and avoid a lot of the messy xml. I found it to be really clean and the closest to Microsofts .Net platform implementation which is IMHO a very good implementation of Web Services ...at least more impressive than anything I have seen in the Java community, but I feel the gap is closing slowly. To integrate with Tapestry I simply overrode Tapestry filter... I am not aware of any more elegant approach, although I made a few inquiries on this list in the past. Cheers, Peter - Original Message - From: "Jim O'Callaghan" To: "Tapestry users" Sent: Monday, 30 August, 2010 10:52:44 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: RE: OT: Web Services Kalle, Daniel, Thanks for the responses. Good to know that there are positive experiences with CXF. It's probably the front-runner for me at the moment, but will keep an ear open for any other feedback. Looking at my original query I can see that it looks like I am focusing on generating WS clients - I should have said "providing interfaces for a system" rather than "interfacing with a system". Regards, Jim. -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 30 August 2010 03:43 To: Tapestry users Subject: Re: OT: Web Services Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org ---
Re: OT: Web Services
hi, i use a (JaxWS)HttpServletRequestFilter service to intercept WS calls to my application. it will only intercept calls that have the url pattern of the provided WS that can be configured. and i'm using metro too. we switched from cxf to metro because it was easier to work with jaxb-binding overrides... g, kris Von:Peter Stavrinides An: Tapestry users Datum: 30.08.2010 14:59 Betreff: Re: OT: Web Services Hi Jim I evaluated quite a few Java WS stacks and was between CXF and Metro, but in the end I chose metro, but to be honest there was very little to choose btw the two... so I would suggest those two as the leading Java WS stacks. Both support maven and are very complete in terms of how much of the web service set of standards they support. Metro implements JAXWS 2.1 and JAXB2.2, so if the marketing babble is to be trusted its 'meant' to be higher performing and more extensible, but I haven't tested that claim yet. In any event it has an impressive array of security features. It also ships with the standard glassfish installation, which means no server configuration is needed if you go that route, I installed it though with Tomcat, it was as easy as executing a script... not too hard at all. Depending how you wish to approach you applications, you can use annotations for the meta programming, and avoid a lot of the messy xml. I found it to be really clean and the closest to Microsofts .Net platform implementation which is IMHO a very good implementation of Web Services ...at least more impressive than anything I have seen in the Java community, but I feel the gap is closing slowly. To integrate with Tapestry I simply overrode Tapestry filter... I am not aware of any more elegant approach, although I made a few inquiries on this list in the past. Cheers, Peter - Original Message - From: "Jim O'Callaghan" To: "Tapestry users" Sent: Monday, 30 August, 2010 10:52:44 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: RE: OT: Web Services Kalle, Daniel, Thanks for the responses. Good to know that there are positive experiences with CXF. It's probably the front-runner for me at the moment, but will keep an ear open for any other feedback. Looking at my original query I can see that it looks like I am focusing on generating WS clients - I should have said "providing interfaces for a system" rather than "interfacing with a system". Regards, Jim. -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 30 August 2010 03:43 To: Tapestry users Subject: Re: OT: Web Services Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: OT: Web Services
Hi Jim I evaluated quite a few Java WS stacks and was between CXF and Metro, but in the end I chose metro, but to be honest there was very little to choose btw the two... so I would suggest those two as the leading Java WS stacks. Both support maven and are very complete in terms of how much of the web service set of standards they support. Metro implements JAXWS 2.1 and JAXB2.2, so if the marketing babble is to be trusted its 'meant' to be higher performing and more extensible, but I haven't tested that claim yet. In any event it has an impressive array of security features. It also ships with the standard glassfish installation, which means no server configuration is needed if you go that route, I installed it though with Tomcat, it was as easy as executing a script... not too hard at all. Depending how you wish to approach you applications, you can use annotations for the meta programming, and avoid a lot of the messy xml. I found it to be really clean and the closest to Microsofts .Net platform implementation which is IMHO a very good implementation of Web Services ...at least more impressive than anything I have seen in the Java community, but I feel the gap is closing slowly. To integrate with Tapestry I simply overrode Tapestry filter... I am not aware of any more elegant approach, although I made a few inquiries on this list in the past. Cheers, Peter - Original Message - From: "Jim O'Callaghan" To: "Tapestry users" Sent: Monday, 30 August, 2010 10:52:44 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: RE: OT: Web Services Kalle, Daniel, Thanks for the responses. Good to know that there are positive experiences with CXF. It's probably the front-runner for me at the moment, but will keep an ear open for any other feedback. Looking at my original query I can see that it looks like I am focusing on generating WS clients - I should have said "providing interfaces for a system" rather than "interfacing with a system". Regards, Jim. -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 30 August 2010 03:43 To: Tapestry users Subject: Re: OT: Web Services Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
RE: OT: Web Services
Thanks Davor - am leaning towards CXF. Regards, Jim. -Original Message- From: Davor Hrg [mailto:hrgda...@gmail.com] Sent: 30 August 2010 08:47 To: Tapestry users Subject: Re: OT: Web Services I used CXF to generate java code from XSD-s, CXF is easily used with maven, but in the end most newer WS engines use JAXB for data binding. JAXB is not perfect, and it took me a whole week to make rules for jaxb to get desired output. To be fair, he problem was not jaxb here but a very bad XSD, so I had to try all JAXB tricks and plugins to get it done well. .. bla .. bla .. what I mean is: CXF is just fine. I've only used old axis before and it was a pain... On Mon, Aug 30, 2010 at 4:43 AM, Kalle Korhonen wrote: > Second that. CXF is the successor to XFire and its solid. > > Kalle > > > On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig > wrote: > > I know of many projects using CXF without complaints. I'd say that CXF > is > > probably a good way to go. > > > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > > wrote: > > > >> I'm aware this is off topic, but since there are so many people on the > list > >> with a broad skill set am hoping I can learn from their experiences / > >> heartbreak. I am evaluating various WS stacks for interfacing with a > >> system > >> - currently I am using XFire as it requires very little configuration > and > >> performs quite efficiently. XFire appears to qualify every xml element > >> with > >> a namespace, bloating the payload considerably, or, if using the patch > from > >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / > >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack > >> they have positive experience of? My constraints are quite liberal - > java > >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any > good? > >> I > >> want to find something with good performance obviously, minimal config, > and > >> hopefully something that consistently defines package level namespaces > at > >> an > >> envelope level and reuses them. > >> > >> > >> > >> Many thanks, > >> > >> Jim. > >> > >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
RE: OT: Web Services
Kalle, Daniel, Thanks for the responses. Good to know that there are positive experiences with CXF. It's probably the front-runner for me at the moment, but will keep an ear open for any other feedback. Looking at my original query I can see that it looks like I am focusing on generating WS clients - I should have said "providing interfaces for a system" rather than "interfacing with a system". Regards, Jim. -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 30 August 2010 03:43 To: Tapestry users Subject: Re: OT: Web Services Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: OT: Web Services
I used CXF to generate java code from XSD-s, CXF is easily used with maven, but in the end most newer WS engines use JAXB for data binding. JAXB is not perfect, and it took me a whole week to make rules for jaxb to get desired output. To be fair, he problem was not jaxb here but a very bad XSD, so I had to try all JAXB tricks and plugins to get it done well. .. bla .. bla .. what I mean is: CXF is just fine. I've only used old axis before and it was a pain... On Mon, Aug 30, 2010 at 4:43 AM, Kalle Korhonen wrote: > Second that. CXF is the successor to XFire and its solid. > > Kalle > > > On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig > wrote: > > I know of many projects using CXF without complaints. I'd say that CXF > is > > probably a good way to go. > > > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > > wrote: > > > >> I'm aware this is off topic, but since there are so many people on the > list > >> with a broad skill set am hoping I can learn from their experiences / > >> heartbreak. I am evaluating various WS stacks for interfacing with a > >> system > >> - currently I am using XFire as it requires very little configuration > and > >> performs quite efficiently. XFire appears to qualify every xml element > >> with > >> a namespace, bloating the payload considerably, or, if using the patch > from > >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / > >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack > >> they have positive experience of? My constraints are quite liberal - > java > >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any > good? > >> I > >> want to find something with good performance obviously, minimal config, > and > >> hopefully something that consistently defines package level namespaces > at > >> an > >> envelope level and reuses them. > >> > >> > >> > >> Many thanks, > >> > >> Jim. > >> > >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
RE: OT: Web Services
Martin,
Thanks for all the details. I hadn't considered the client generation at this
stage, and was planning on just relying on the published wsdl for business
consumers to use whatever package they wanted to generate a client from the
public wsdl - perhaps this is not a realistic expectation. None the less
thanks for the pom excludes / targets. They should prove useful if I go down
that route. I'm leaning toward CXF at the moment as I think it won't be a huge
step from XFire
Regards,
Jim.
-Original Message-
From: Martin Strand [mailto:do.not.eat.yellow.s...@gmail.com]
Sent: 29 August 2010 19:07
To: Tapestry users
Subject: Re: OT: Web Services
On Sun, 29 Aug 2010 19:35:11 +0200, Jim O'Callaghan
wrote:
> I'm aware this is off topic, but since there are so many people on the
> list
> with a broad skill set am hoping I can learn from their experiences /
> heartbreak. I am evaluating various WS stacks for interfacing with a
> system
> - currently I am using XFire as it requires very little configuration and
> performs quite efficiently. XFire appears to qualify every xml element
> with
> a namespace, bloating the payload considerably, or, if using the patch
> from
> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable /
> inconsistent namespace qualifiers. Can anyone recommend a good WS stack
> they have positive experience of? My constraints are quite liberal -
> java
> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any
> good? I
> want to find something with good performance obviously, minimal config,
> and
> hopefully something that consistently defines package level namespaces
> at an
> envelope level and reuses them.
>
>
> Many thanks,
>
> Jim.
I've been using axis2 for several years to generate clients for a few 3rd
party web services (I presume you're talking about client code)
Can't really say I would *recommend* it because it was a pain to get it
working with Maven and I haven't even bothered to go through that again
with 1.4.x or 1.5.x so I'm still using 1.3.
But, it's very simple once you set up the build - Maven will generate
POJOs in target/generated-sources/... and when you invoke methods on those
POJOs everything "just works".
The axis2 1.3 POMs are a mess though so there are lots of excludes here to
get rid of unnecessary dependencies:
org.apache.axis2
axis2-wsdl2code-maven-plugin
some-service
wsdl2code
${basedir}/src/main/wsdl/some-service.wsdl
com.example.service
com.example.service=com.example.service
sync
some-other-service
wsdl2code
${basedir}/src/main/wsdl/some-other-service.wsdl
com.example.other
com.example.other=com.example.other
sync
...
org.apache.axis2
axis2-kernel
1.3
avalon-framework
avalon-framework
backport-util-concurrent
backport-util-concurrent
javax.mail
mail
javax.activation
activation
javax.servlet
servlet-api
commons-fileupload
commons-fileupload
junit
junit
org.apache.woden
woden
org.apache.geronimo.specs
geronimo-jms_1.1_spec
xml-apis
xml-apis
org.codehaus.woodstox
wstx-asl
annogen
annogen
Re: OT: Web Services
Second that. CXF is the successor to XFire and its solid. Kalle On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: OT: Web Services
I know of many projects using CXF without complaints. I'd say that CXF is probably a good way to go. On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan wrote: > I'm aware this is off topic, but since there are so many people on the list > with a broad skill set am hoping I can learn from their experiences / > heartbreak. I am evaluating various WS stacks for interfacing with a > system > - currently I am using XFire as it requires very little configuration and > performs quite efficiently. XFire appears to qualify every xml element > with > a namespace, bloating the payload considerably, or, if using the patch from > http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / > inconsistent namespace qualifiers. Can anyone recommend a good WS stack > they have positive experience of? My constraints are quite liberal - java > 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? > I > want to find something with good performance obviously, minimal config, and > hopefully something that consistently defines package level namespaces at > an > envelope level and reuses them. > > > > Many thanks, > > Jim. > >
Re: OT: Web Services
On Sun, 29 Aug 2010 19:35:11 +0200, Jim O'Callaghan
wrote:
I'm aware this is off topic, but since there are so many people on the
list
with a broad skill set am hoping I can learn from their experiences /
heartbreak. I am evaluating various WS stacks for interfacing with a
system
- currently I am using XFire as it requires very little configuration and
performs quite efficiently. XFire appears to qualify every xml element
with
a namespace, bloating the payload considerably, or, if using the patch
from
http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable /
inconsistent namespace qualifiers. Can anyone recommend a good WS stack
they have positive experience of? My constraints are quite liberal -
java
1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any
good? I
want to find something with good performance obviously, minimal config,
and
hopefully something that consistently defines package level namespaces
at an
envelope level and reuses them.
Many thanks,
Jim.
I've been using axis2 for several years to generate clients for a few 3rd
party web services (I presume you're talking about client code)
Can't really say I would *recommend* it because it was a pain to get it
working with Maven and I haven't even bothered to go through that again
with 1.4.x or 1.5.x so I'm still using 1.3.
But, it's very simple once you set up the build - Maven will generate
POJOs in target/generated-sources/... and when you invoke methods on those
POJOs everything "just works".
The axis2 1.3 POMs are a mess though so there are lots of excludes here to
get rid of unnecessary dependencies:
org.apache.axis2
axis2-wsdl2code-maven-plugin
some-service
wsdl2code
${basedir}/src/main/wsdl/some-service.wsdl
com.example.service
com.example.service=com.example.service
sync
some-other-service
wsdl2code
${basedir}/src/main/wsdl/some-other-service.wsdl
com.example.other
com.example.other=com.example.other
sync
...
org.apache.axis2
axis2-kernel
1.3
avalon-framework
avalon-framework
backport-util-concurrent
backport-util-concurrent
javax.mail
mail
javax.activation
activation
javax.servlet
servlet-api
commons-fileupload
commons-fileupload
junit
junit
org.apache.woden
woden
org.apache.geronimo.specs
geronimo-jms_1.1_spec
xml-apis
xml-apis
org.codehaus.woodstox
wstx-asl
annogen
annogen
xalan
xalan
stax
stax-api
jaxen
jaxen
commons-io
commons-io
org.apache.httpcomponents
httpcore-niossl
org.apache.httpcomponents
httpcore
org.apache.httpcomponents
httpcore-nio
xerces
xercesImpl
org.apache.ws.commons.axiom
OT: Web Services
I'm aware this is off topic, but since there are so many people on the list with a broad skill set am hoping I can learn from their experiences / heartbreak. I am evaluating various WS stacks for interfacing with a system - currently I am using XFire as it requires very little configuration and performs quite efficiently. XFire appears to qualify every xml element with a namespace, bloating the payload considerably, or, if using the patch from http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / inconsistent namespace qualifiers. Can anyone recommend a good WS stack they have positive experience of? My constraints are quite liberal - java 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? I want to find something with good performance obviously, minimal config, and hopefully something that consistently defines package level namespaces at an envelope level and reuses them. Many thanks, Jim.
