RE: Web site look and feel....
Hi, The entry page looks good to me, it's different after all ! - though the users docs pages are still styled by Confluence. I'm quite happy with Confluence styles too but unfortunately, as you mentioned, it appears all the proper formatting is lost after a given page has been edited - at least in the JAX-RS space :-) If there was some Confluence fix available then may be we could still continue using Confluence styles, otherwise +1 to introducing new styles. cheers, Sergey -Original Message- From: Daniel Kulp [mailto:dk...@apache.org] Sent: Tue 8/11/2009 9:22 PM To: dev@cxf.apache.org Subject: Web site look and feel I'm sure a couple of you have noticed that the upgrade that infrastructure did to confluence a few weeks ago has caused some trouble with the html export, particularly with code samples. Every time someone edits a page that contains code samples, I seem to have to re-export the entire space to fix it again. Quite annoying. One fix is to properly define our own styles and templates and such. This also has the advantage of making it look better. Basically, make it not look like a confluence space. I've copied the CXF space over to a new space (not the docs space) and have been playing with adapting the ServiceMix style sheets and layouts and such to CXF. (I like the SMX blue colors. I also played with the camel/activemq design, but I like the earth tones less) (then again, I'm VERY color blind, what the hell do I know about color?) Anyway, would everyone take a quick look at: http://cwiki.apache.org/CXFTEST/ And let me know what you think? If people are OK with it, I'll get everything switched to using it.Feel free to add/edit pages in that space to see how it would look, copy pages from the docs, etcWe can tweek it more later if need be, but I think we need to get something in place soon to work around the export issues. Thanks! -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Handling collections with Aegis in JAX-RS
Hi Benson I can't make the Aegis tests writing/reading collections working in CXF JAX-RS. I've found that AegisProviderTest#testReadWriteComplexMap is still @Ignored, it might've passed for you because it was @Ignored :-) I've also added testWriteCollections() (which writes ListAegisTestBean) to AegisJSONProviderTest. I also updated DataBindingJSONProviderTest, one of its internal classes to return ListBook. AegisJSONProvider extends AegisElementProvider, DataBindingJSONProvider extends DataBindingProvider which actually (in this case) delegates to Aegis DataBinding. AegisJSONProviderTest fails at the write time, it can't find the mapping for List. DataBindingJSONProviderTest fails early at the Aegis DataBinding initialization time for the same reason. I thought Lists were supported by default ? I haven't found any exam[le showing how a type mapping for Lists can be created. Can you please, whenever you have a chance, have a look at these tests ? thanks, Sergey
Re: How to disablle Aegis schema validation
It's off by default, isn't it? On Tue, Aug 11, 2009 at 11:58 AM, Sergey Beryozkinsergey.beryoz...@iona.com wrote: Is there a property which can be used to disable Aegis schema validation ? thanks, Sergey -- View this message in context: http://www.nabble.com/How-to-disablle-Aegis-schema-validation-tp24920473p24920473.html Sent from the cxf-dev mailing list archive at Nabble.com.
Re: Web site look and feel....
I know it's only been 13 hours or so, but I've hit the confluence bug with code blocks again so I'm going to go ahead and move to this. I'll save the old template so we can revert if we want or if people complain or something. Just like any code change, it's reversable. :-) At this point, I just want to make sure the documentation and such is consistently usable. Dan On Tue August 11 2009 9:22:20 pm Daniel Kulp wrote: I'm sure a couple of you have noticed that the upgrade that infrastructure did to confluence a few weeks ago has caused some trouble with the html export, particularly with code samples. Every time someone edits a page that contains code samples, I seem to have to re-export the entire space to fix it again. Quite annoying. One fix is to properly define our own styles and templates and such. This also has the advantage of making it look better. Basically, make it not look like a confluence space. I've copied the CXF space over to a new space (not the docs space) and have been playing with adapting the ServiceMix style sheets and layouts and such to CXF. (I like the SMX blue colors. I also played with the camel/activemq design, but I like the earth tones less) (then again, I'm VERY color blind, what the hell do I know about color?) Anyway, would everyone take a quick look at: http://cwiki.apache.org/CXFTEST/ And let me know what you think? If people are OK with it, I'll get everything switched to using it.Feel free to add/edit pages in that space to see how it would look, copy pages from the docs, etcWe can tweek it more later if need be, but I think we need to get something in place soon to work around the export issues. Thanks! -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: Web site look and feel....
On Wed August 12 2009 3:21:27 am Christian Schneider wrote: I like the new look. The only problem on my notebook (19/6 screen, 1280x800) is that the Apache CXF title uses a big part of the vertical size. I would suggest to make the title a little smaller. I THINK there is something in the css file that is setting the size of the banner. I shrunk the font size a bit, but it didn't seem to affect the banner size. I'll try and dig in a bit more. That said, longer term, I'd like to get that replaced with a real logo. That's a different topic. I started writing up a page to start a logo contest: http://cxf.apache.org/logo-contest.html but I need some time to finish that as well as figure out a good time to run it (august is not a good time due to vacations and such). Anyway, thanks for the feedback. Dan Greetings Christian Daniel Kulp schrieb: I'm sure a couple of you have noticed that the upgrade that infrastructure did to confluence a few weeks ago has caused some trouble with the html export, particularly with code samples. Every time someone edits a page that contains code samples, I seem to have to re-export the entire space to fix it again. Quite annoying. One fix is to properly define our own styles and templates and such. This also has the advantage of making it look better. Basically, make it not look like a confluence space. I've copied the CXF space over to a new space (not the docs space) and have been playing with adapting the ServiceMix style sheets and layouts and such to CXF. (I like the SMX blue colors. I also played with the camel/activemq design, but I like the earth tones less) (then again, I'm VERY color blind, what the hell do I know about color?) Anyway, would everyone take a quick look at: http://cwiki.apache.org/CXFTEST/ And let me know what you think? If people are OK with it, I'll get everything switched to using it.Feel free to add/edit pages in that space to see how it would look, copy pages from the docs, etcWe can tweek it more later if need be, but I think we need to get something in place soon to work around the export issues. Thanks! -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: WSDL2JS
On Tue August 11 2009 11:12:04 pm Demetris wrote: Hi Benson, that would a great opportunity to get to know CXF but I am sure I won't be given the time to work on it. I will certainly pass it on and see if we can get someone to work with you although I still have a feeling that the pressure to migrate to Axis2 is mounting. May I ask why Axis2? Axis2 is as similar to Axis1 as CXF is. :-) If you're going to migrate, I'd suggest migrating to a standards based API like JAX-WS and chose one of the really good JAX-WS implementations, like CXF. :-) Dan We (at least I) appreciate the offer Benson and I will make sure the word gets around here. I will let you know how it goes or at least if I have any more Qs on CXF in general. Thanks -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: WSDL2JS
On Tue August 11 2009 11:26:05 pm Demetris wrote: Do you know if Axis 1.x can generate document/literal or only rpc/encoded? I am wondering if setting the OPERATION_STYLE_PROPERTY to document would do the trick. I believe Axis1 can do doc/literal. JAX-RPC did require some level of support for that so I'm pretty sure Axis1 implemented it. Not sure how to go about configuring it to do so. I'm not an Axis1 user. :-) Dan Benson Margulies wrote: Demetris, If your place has a big investment in RPC/encoded, perhaps one of you would like to pick up the project that one of our committers started of adding RPC/encoded support to CXF. If you do it, you get to ensure that it works with your services :-). I'd be happy to mentor someone in figuring out where Dain left off. --benson On Tue, Aug 11, 2009 at 4:21 PM, Demetrisdemet...@ece.neu.edu wrote: Of course I do see infrastructures here in production still using Axis 1.x without any plans on migrating while other systems come into play with Axis 2 etc. and interoperability between the two sides is impossible - and of course the rest of us will need to sit in between and needing to do our own translations - not good. In any case, CFX is a pretty impressive project so I have a feeling I will be adapting it to my work. Cheers Daniel Kulp wrote: On Tue August 11 2009 12:15:40 pm Demetris wrote: That's what I figured ;) Thanks for the info Benson. Now regarding inteconnection of Web Services across implementations, if there is no bridge between the old RPC/encoded and CFX, at least I am assuming that newer versions would be able to handle SOAP calls across them or not? This is something I never tried/looked into while I worked exclusively with Axis so I was wondering. Pretty much none of the modern SOAP toolkits support RPC/encoded. Axis2 doesn't. CXF doesn't. Metro/JAX-WS RI doesn't. Etc Basically, rpc/encoded was such an interopability nightmare that it really fell into the bucket of You REALLY REALLY don't want to use it.If you want interopability, you really need to migrate to one of the literal forms. Dan Benson Margulies wrote: OK, that message is buried in the substrate somewhere. I'm not sure that I agree with it :-) In practical terms, we just don't have the code or RPC/encoded. I'm unaware of anything you can use to interconnect an old Axis RPC/encoded service with CXF. On Mon, Aug 10, 2009 at 11:00 PM, Demetrisdemet...@ece.neu.edu wrote: Hi Benson, the reason I mentioned JAX-WS is because a WSDL file that I passed to WSDL2JS returned RCP/encoded WSDLs are not supported in JAX-2.0. I had a feeling it is neither here nor there but I wanted to double-check - I think I know what the issue is now after reading the corresponding documentation but I will return and send more info if I cannot resolve it. A separate question - is there a bridge between Axis WS and its tools and CFX? Can an Axis WS client call a CFX-implemented WS and vice versa or not? Thanks Benson Margulies wrote: Demetris, CXF includes the ability to build Soap 1.1 Javascript clients for doc/lit and rpc/lit services. JAX-WS is relatively neither here nor there. The code can be run in two modes. You can run the tool as a standalone, and you get Javascript that (with the utility file supplied) will run anywhere that has a compatible request object. Or, you can ask any CXF-implemented web service to deliver a javascript client, and one will be returned. Have you read http://cwiki.apache.org/CXF20DOC/javascript-clients.html? --benson On Mon, Aug 10, 2009 at 5:40 PM, Demetrisdemet...@ece.neu.edu wrote: And one more observation - because wsdl2js utilizes JAX-WS 2.0, RPC/Encoded documents are not supported. Is that correct? Thanks again Demetris wrote: Ok now that I played a bit with wsdl2js I am beginning to understand what you said below. So one can use the wsdlurl in order to get the server to return the script - can you please clarify a few things since I am new to this - 1. what kind of server are we talking about in this case? 2. The only way to generate the Javascript is through a remote server + URL? If I have the WSDL in my possesion how can I use this tool to generate the script of me? Thanks again Benson Margulies wrote: The tool is part of CXF, so it requires Java 1.5. Since its output is Javascript, I don't understand why you need to run it under J2ME. In fact, you can just use the ?js URL form from the server to get the server to generate it on the fly. On Mon, Aug 10, 2009 at 2:32 PM, Demetrisdemet...@ece.neu.edu wrote: Hi all, I am interested in generating Javascript stubs from a WSDL file - I am assuming that the WSDL2js tool is the appropriate tool to use. Has anyone used this tool so that I can
Re: WSDL2JS
He he - didn't mean to put you on the spot Dan - but I think you are right so I will chase it in the Axis lists. Daniel Kulp wrote: On Tue August 11 2009 11:26:05 pm Demetris wrote: Do you know if Axis 1.x can generate document/literal or only rpc/encoded? I am wondering if setting the OPERATION_STYLE_PROPERTY to document would do the trick. I believe Axis1 can do doc/literal. JAX-RPC did require some level of support for that so I'm pretty sure Axis1 implemented it. Not sure how to go about configuring it to do so. I'm not an Axis1 user. :-) Dan Benson Margulies wrote: Demetris, If your place has a big investment in RPC/encoded, perhaps one of you would like to pick up the project that one of our committers started of adding RPC/encoded support to CXF. If you do it, you get to ensure that it works with your services :-). I'd be happy to mentor someone in figuring out where Dain left off. --benson On Tue, Aug 11, 2009 at 4:21 PM, Demetrisdemet...@ece.neu.edu wrote: Of course I do see infrastructures here in production still using Axis 1.x without any plans on migrating while other systems come into play with Axis 2 etc. and interoperability between the two sides is impossible - and of course the rest of us will need to sit in between and needing to do our own translations - not good. In any case, CFX is a pretty impressive project so I have a feeling I will be adapting it to my work. Cheers Daniel Kulp wrote: On Tue August 11 2009 12:15:40 pm Demetris wrote: That's what I figured ;) Thanks for the info Benson. Now regarding inteconnection of Web Services across implementations, if there is no bridge between the old RPC/encoded and CFX, at least I am assuming that newer versions would be able to handle SOAP calls across them or not? This is something I never tried/looked into while I worked exclusively with Axis so I was wondering. Pretty much none of the modern SOAP toolkits support RPC/encoded. Axis2 doesn't. CXF doesn't. Metro/JAX-WS RI doesn't. Etc Basically, rpc/encoded was such an interopability nightmare that it really fell into the bucket of You REALLY REALLY don't want to use it.If you want interopability, you really need to migrate to one of the literal forms. Dan Benson Margulies wrote: OK, that message is buried in the substrate somewhere. I'm not sure that I agree with it :-) In practical terms, we just don't have the code or RPC/encoded. I'm unaware of anything you can use to interconnect an old Axis RPC/encoded service with CXF. On Mon, Aug 10, 2009 at 11:00 PM, Demetrisdemet...@ece.neu.edu wrote: Hi Benson, the reason I mentioned JAX-WS is because a WSDL file that I passed to WSDL2JS returned RCP/encoded WSDLs are not supported in JAX-2.0. I had a feeling it is neither here nor there but I wanted to double-check - I think I know what the issue is now after reading the corresponding documentation but I will return and send more info if I cannot resolve it. A separate question - is there a bridge between Axis WS and its tools and CFX? Can an Axis WS client call a CFX-implemented WS and vice versa or not? Thanks Benson Margulies wrote: Demetris, CXF includes the ability to build Soap 1.1 Javascript clients for doc/lit and rpc/lit services. JAX-WS is relatively neither here nor there. The code can be run in two modes. You can run the tool as a standalone, and you get Javascript that (with the utility file supplied) will run anywhere that has a compatible request object. Or, you can ask any CXF-implemented web service to deliver a javascript client, and one will be returned. Have you read http://cwiki.apache.org/CXF20DOC/javascript-clients.html? --benson On Mon, Aug 10, 2009 at 5:40 PM, Demetrisdemet...@ece.neu.edu wrote: And one more observation - because wsdl2js utilizes JAX-WS 2.0, RPC/Encoded documents are not supported. Is that correct? Thanks again Demetris wrote: Ok now that I played a bit with wsdl2js I am beginning to understand what you said below. So one can use the wsdlurl in order to get the server to return the script - can you please clarify a few things since I am new to this - 1. what kind of server are we talking about in this case? 2. The only way to generate the Javascript is through a remote server + URL? If I have the WSDL in my possesion how can I use this tool to generate the script of me? Thanks again Benson Margulies wrote: The tool is part of CXF, so it requires Java 1.5. Since its output is Javascript, I don't understand why you need to run it under J2ME. In fact, you can just use the ?js URL form from the server to get the server to generate it on the fly. On Mon, Aug 10, 2009 at 2:32 PM, Demetrisdemet...@ece.neu.edu wrote: Hi all, I am interested in generating
Re: WSDL2JS
Nicely put - I wouldn't have been messing around with CXF if I didn't think it is worth it and the more I read about the more I am finding a number of fairly interesting directions I can take using it. So yes, I mentioned Axis2 cause I overhead some people talking about it but hey I have no problem advocating CXF here ;) Daniel Kulp wrote: On Tue August 11 2009 11:12:04 pm Demetris wrote: Hi Benson, that would a great opportunity to get to know CXF but I am sure I won't be given the time to work on it. I will certainly pass it on and see if we can get someone to work with you although I still have a feeling that the pressure to migrate to Axis2 is mounting. May I ask why Axis2? Axis2 is as similar to Axis1 as CXF is. :-) If you're going to migrate, I'd suggest migrating to a standards based API like JAX-WS and chose one of the really good JAX-WS implementations, like CXF. :-) Dan We (at least I) appreciate the offer Benson and I will make sure the word gets around here. I will let you know how it goes or at least if I have any more Qs on CXF in general. Thanks
Re: WSDL2JS
CXF has two things going on here. 1) you can ask the server to generate and deliver the javascript client. 2) you can create a 'dynamic client' that can talk to moderately complex services. However, option 2 requires the entire CXF stack on the client, and I have no idea if J2ME has the necessary goodies. On Wed, Aug 12, 2009 at 4:47 PM, Demetrisdemet...@ece.neu.edu wrote: Does CXF support client-side programming for Web Services? What we are after in one of our projects is to: (1) host web services (or at least a Soap engine) on mobile devices (primarily running J2ME CDC) (2) build web service clients on mobile devices, either by discovering and utilizing WSDLs (to generate javascript stubs) or some other mechanism to allow them to generate the client code. Not sure how realistic this is at this stage but I am not finding much on (1) and a bit on (2). Many people have said that generating WSDLs on mobile devices is a difficult task so we are considering the off-the- device mechanisms. Daniel Kulp wrote: On Tue August 11 2009 11:26:05 pm Demetris wrote: Do you know if Axis 1.x can generate document/literal or only rpc/encoded? I am wondering if setting the OPERATION_STYLE_PROPERTY to document would do the trick. I believe Axis1 can do doc/literal. JAX-RPC did require some level of support for that so I'm pretty sure Axis1 implemented it. Not sure how to go about configuring it to do so. I'm not an Axis1 user. :-) Dan Benson Margulies wrote: Demetris, If your place has a big investment in RPC/encoded, perhaps one of you would like to pick up the project that one of our committers started of adding RPC/encoded support to CXF. If you do it, you get to ensure that it works with your services :-). I'd be happy to mentor someone in figuring out where Dain left off. --benson On Tue, Aug 11, 2009 at 4:21 PM, Demetrisdemet...@ece.neu.edu wrote: Of course I do see infrastructures here in production still using Axis 1.x without any plans on migrating while other systems come into play with Axis 2 etc. and interoperability between the two sides is impossible - and of course the rest of us will need to sit in between and needing to do our own translations - not good. In any case, CFX is a pretty impressive project so I have a feeling I will be adapting it to my work. Cheers Daniel Kulp wrote: On Tue August 11 2009 12:15:40 pm Demetris wrote: That's what I figured ;) Thanks for the info Benson. Now regarding inteconnection of Web Services across implementations, if there is no bridge between the old RPC/encoded and CFX, at least I am assuming that newer versions would be able to handle SOAP calls across them or not? This is something I never tried/looked into while I worked exclusively with Axis so I was wondering. Pretty much none of the modern SOAP toolkits support RPC/encoded. Axis2 doesn't. CXF doesn't. Metro/JAX-WS RI doesn't. Etc Basically, rpc/encoded was such an interopability nightmare that it really fell into the bucket of You REALLY REALLY don't want to use it. If you want interopability, you really need to migrate to one of the literal forms. Dan Benson Margulies wrote: OK, that message is buried in the substrate somewhere. I'm not sure that I agree with it :-) In practical terms, we just don't have the code or RPC/encoded. I'm unaware of anything you can use to interconnect an old Axis RPC/encoded service with CXF. On Mon, Aug 10, 2009 at 11:00 PM, Demetrisdemet...@ece.neu.edu wrote: Hi Benson, the reason I mentioned JAX-WS is because a WSDL file that I passed to WSDL2JS returned RCP/encoded WSDLs are not supported in JAX-2.0. I had a feeling it is neither here nor there but I wanted to double-check - I think I know what the issue is now after reading the corresponding documentation but I will return and send more info if I cannot resolve it. A separate question - is there a bridge between Axis WS and its tools and CFX? Can an Axis WS client call a CFX-implemented WS and vice versa or not? Thanks Benson Margulies wrote: Demetris, CXF includes the ability to build Soap 1.1 Javascript clients for doc/lit and rpc/lit services. JAX-WS is relatively neither here nor there. The code can be run in two modes. You can run the tool as a standalone, and you get Javascript that (with the utility file supplied) will run anywhere that has a compatible request object. Or, you can ask any CXF-implemented web service to deliver a javascript client, and one will be returned. Have you read http://cwiki.apache.org/CXF20DOC/javascript-clients.html? --benson On Mon, Aug 10, 2009 at 5:40 PM, Demetrisdemet...@ece.neu.edu wrote: And one more observation - because wsdl2js utilizes JAX-WS 2.0, RPC/Encoded documents are not supported. Is that correct? Thanks again Demetris wrote: Ok now that I played a bit with wsdl2js I am beginning to understand
Re: WSDL2JS
Hmm - good point on (2). Ok thanks Benson, I will work with (1) first and see how it fairs. It should be straight-forward. Benson Margulies wrote: CXF has two things going on here. 1) you can ask the server to generate and deliver the javascript client. 2) you can create a 'dynamic client' that can talk to moderately complex services. However, option 2 requires the entire CXF stack on the client, and I have no idea if J2ME has the necessary goodies. On Wed, Aug 12, 2009 at 4:47 PM, Demetrisdemet...@ece.neu.edu wrote: Does CXF support client-side programming for Web Services? What we are after in one of our projects is to: (1) host web services (or at least a Soap engine) on mobile devices (primarily running J2ME CDC) (2) build web service clients on mobile devices, either by discovering and utilizing WSDLs (to generate javascript stubs) or some other mechanism to allow them to generate the client code. Not sure how realistic this is at this stage but I am not finding much on (1) and a bit on (2). Many people have said that generating WSDLs on mobile devices is a difficult task so we are considering the off-the- device mechanisms. Daniel Kulp wrote: On Tue August 11 2009 11:26:05 pm Demetris wrote: Do you know if Axis 1.x can generate document/literal or only rpc/encoded? I am wondering if setting the OPERATION_STYLE_PROPERTY to document would do the trick. I believe Axis1 can do doc/literal. JAX-RPC did require some level of support for that so I'm pretty sure Axis1 implemented it. Not sure how to go about configuring it to do so. I'm not an Axis1 user. :-) Dan Benson Margulies wrote: Demetris, If your place has a big investment in RPC/encoded, perhaps one of you would like to pick up the project that one of our committers started of adding RPC/encoded support to CXF. If you do it, you get to ensure that it works with your services :-). I'd be happy to mentor someone in figuring out where Dain left off. --benson On Tue, Aug 11, 2009 at 4:21 PM, Demetrisdemet...@ece.neu.edu wrote: Of course I do see infrastructures here in production still using Axis 1.x without any plans on migrating while other systems come into play with Axis 2 etc. and interoperability between the two sides is impossible - and of course the rest of us will need to sit in between and needing to do our own translations - not good. In any case, CFX is a pretty impressive project so I have a feeling I will be adapting it to my work. Cheers Daniel Kulp wrote: On Tue August 11 2009 12:15:40 pm Demetris wrote: That's what I figured ;) Thanks for the info Benson. Now regarding inteconnection of Web Services across implementations, if there is no bridge between the old RPC/encoded and CFX, at least I am assuming that newer versions would be able to handle SOAP calls across them or not? This is something I never tried/looked into while I worked exclusively with Axis so I was wondering. Pretty much none of the modern SOAP toolkits support RPC/encoded. Axis2 doesn't. CXF doesn't. Metro/JAX-WS RI doesn't. Etc Basically, rpc/encoded was such an interopability nightmare that it really fell into the bucket of You REALLY REALLY don't want to use it.If you want interopability, you really need to migrate to one of the literal forms. Dan Benson Margulies wrote: OK, that message is buried in the substrate somewhere. I'm not sure that I agree with it :-) In practical terms, we just don't have the code or RPC/encoded. I'm unaware of anything you can use to interconnect an old Axis RPC/encoded service with CXF. On Mon, Aug 10, 2009 at 11:00 PM, Demetrisdemet...@ece.neu.edu wrote: Hi Benson, the reason I mentioned JAX-WS is because a WSDL file that I passed to WSDL2JS returned RCP/encoded WSDLs are not supported in JAX-2.0. I had a feeling it is neither here nor there but I wanted to double-check - I think I know what the issue is now after reading the corresponding documentation but I will return and send more info if I cannot resolve it. A separate question - is there a bridge between Axis WS and its tools and CFX? Can an Axis WS client call a CFX-implemented WS and vice versa or not? Thanks Benson Margulies wrote: Demetris, CXF includes the ability to build Soap 1.1 Javascript clients for doc/lit and rpc/lit services. JAX-WS is relatively neither here nor there. The code can be run in two modes. You can run the tool as a standalone, and you get Javascript that (with the utility file supplied) will run anywhere that has a compatible request object. Or, you can ask any CXF-implemented web service to deliver a javascript client, and one will be returned. Have you read http://cwiki.apache.org/CXF20DOC/javascript-clients.html? --benson On Mon, Aug 10, 2009 at 5:40 PM, Demetrisdemet...@ece.neu.edu
