Re: WSS4J - Protection Order
I see, interesting. In order to do this in a way that does not require a change to CXF, perhaps what you could do is split your encryption and signature actions into 2 separate interceptors, and add a third in between, which peeks at the result of the encryption action (the results object will be on the message), and then programatically configures the WS4JOutInterceptor, which will do the signature action for you. -Fred On Jan 23, 2008, at 12:41 AM, Mayank Mishra wrote: Hi Fred, Yes, you are right. I am talking about the scenario when we have multiple EncryptedData elements and I want to sign only one of them. Yes, I agree XPath would have been much better to handle such scenario. But AFAIK, we can specify parts (WSEncryptionPart) during SignatureAction by initializing part structure with element Id (I guess it is wsu:id, which we can get from map populated during encryptionAction). I am yet to test it. I will let you know about it. With Regards, Mayank Fred Dushin wrote: Hi Mayank, When you say one way to achieve this is to specify the URI of the EncryptedData, do you mean QName, instead of URI? I get the sense from what you are saying that your message may have multiple EncryptedData elements in it, and you want to sign one, but not others. Is that right? If you have only one EncryptedData, then you should be able to direct the WSS4J toolkit to sign it, by specifying the EncryptedData QName, in configuration of the interceptor. Unfortunately, WSS4J does not provide XPath support for protecting (signing/encrypting) message parts, so using QNames is inherently ambiguous. -Fred On Jan 18, 2008, at 2:24 AM, Mayank Mishra wrote: Any reply to this thread will be highly appreciated. Thanking in advance, With Regards, Mayank Mayank Mishra wrote: Hi, Usually we use, Sign and then Encrypt action for any particular xml element. If I want to use Encrypt and then Sign for a particular xml element, then SignatureAction fails to find the xml element. The reason is it has been encrypted and hence corresponding EncryptedData element will be there. One way to achieve this, is to specify, URI of EncryptedData itself in the signature parts. (It should work, though I haven't tested it). But this is not a full proof solution if I want only specific element only to be encrypted and eventually signed. *Is there any mechanism to achieve this?* The only way I can think of achieving this is to maintain a list of wsu:id's of corresponding EncryptedData elements and add URI of them to Signature Parts during .SignatureAction. This may be performed in adding another interceptor which handles the message after encryption has been done. Please let me know your views/suggestions about this. Thanking in advance. :) With Regards, Mayank
RE: jms client
Hi, Got it! Extracted the proxy object from the client proxy, the client from the proxy object, the jmstransport conduit from the client, and finally the AddressType from the conduit. Then added all the address info to the AddressType. :) Regards Mayank -Original Message- From: Mayank Thakore [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 12:45 To: cxf-user@incubator.apache.org; [EMAIL PROTECTED] Subject: RE: jms client Hi, After getting the service I could add the port to it and then get the service proxy. service.addPort(portName, http://schemas.xmlsoap.org/soap/;, endPointURL); NotificationConsumer consumer = service.getPort(portName, NotificationConsumer.class); But, problem is that this port does not have JMS information which we provide per port in the wsdl. jms:address jndiConnectionFactoryName=ConnectionFactory jndiDestinationName=NotificationConsumerQueue jndiReplyDestinationName=NotificationConsumerReplyQueue jms:JMSNamingProperty name=java.naming.factory.initial value=org.apache.activemq.jndi.ActiveMQInitialContextFactory / jms:JMSNamingProperty name=java.naming.provider.url value=tcp://localhost:61616 / /jms:address Hence, when trying to use the proxy, it fails with exception similar to when wsdl is not provided in the service annotation. So, now that I can add the port, how to provide the jms destination specific information? Thanks! Regards Mayank -Original Message- From: Mayank Thakore [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 11:53 To: cxf-user@incubator.apache.org Subject: jms client Hi, I need to write client to contact several JMS service instances. I will know their queue names only at runtime. If I provide wsdl to the client code, then it only contacts the port listed in the wsdl. (In http I could provide the server's wsdl by appending ?wsdl to the url, but this can't be done for jms urls) How to contact server? The service definition is same. The jndi is also same. Only the queue names will differ. Thanks! Regards Mayank This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
JAX-RS maturity
Hi, I'm currently deciding on a REST framework to use for an upcoming project and have been looking at a number of possibilities including CXF. Just a few quick questions. How mature is the JAX-RS implementation? Will there be a lot of changes in the near future? Have any of you had experience with the Jersey implementation of the JSR311 standard, and if so how does it compare to the CXF implementation? At the moment I'm siding towards using JAX-RS via the CXF implementation provided it is pretty stable. Cheers. -- View this message in context: http://www.nabble.com/JAX-RS-maturity-tp15039120p15039120.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: JSON and JAX-RS
Hi String is supported already, not sure if more work is needed to support primitive types, it would be trivial to do Cheers, Sergey - Original Message - From: Vespa, Anthony J [EMAIL PROTECTED] To: Daniel Kulp [EMAIL PROTECTED]; cxf-user@incubator.apache.org Sent: Wednesday, January 23, 2008 2:12 AM Subject: RE: JSON and JAX-RS Interesting. Would that mean I would have to use seekAlso and list all of the objects that could possibly be returned - I have currently about six types of custom objects. What if I was returning a type like a boolean or just a string? From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tue 1/22/2008 5:31 PM To: cxf-user@incubator.apache.org Cc: Vespa, Anthony J Subject: Re: JSON and JAX-RS Well, looking at the code, it seems to create a new JAXBContext for each top level type, which really sucks. IMO, it should use our JAXBDatabinding in some way which would allow it/you to configure things via spring or something so one one JAXBContext is created/used that would have all the required types in it. Actually, checking if there is an ObjectFactory in the package and creating the context based on that would also go a long way to helping. That said, with JAXB 2.1, you can probably add an @XmlSeeAlso annation on the wsResponse that points to the wsMessage to make the JAXBContext for the wsResponse be able to marshal the wsMessage as well. Dan On Tuesday 22 January 2008, Vespa, Anthony J wrote: So I spent some time playing with JAX-RS and I seem to have encountered an issue. I can return single objects from my service as JSON (standard Java types as well as my custom objects) but if I try to return my wrapper object which contains an anytype generic list, I get an exception. Effectively I have an object called wsResponse that, in this case, is returning an array of messages (wsMessage) - I have decorated both objects with the XMLType. I am looking into this exception and see references to JAXB; is it possible to get around this? Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Available content types for response is: application/json, Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Response EntityProvider is: org.apache.cxf.jaxrs.provider.JSONProvider Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Response content type is: application/json javax.xml.bind.MarshalException - with linked exception: [javax.xml.bind.JAXBException: class com.cbs.bos.data.ws.wsMessage nor any of its super class is known to this context.] at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:2 95 ) at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java :1 48) at org.apache.cxf.jaxrs.provider.JSONProvider.writeTo(JSONProvider.java:9 0) at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(JAX RS OutInterceptor.java:99) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercepto rC hain.java:208) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(Outg oi ngChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercepto rC hain.java:208) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitia ti onObserver.java:78) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletD es tination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(S er vletController.java:264) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletContr ol ler.java:123) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXF Se rvlet.java:170) at org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet(AbstractCXFS er vlet.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli ca tionFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lt erChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa lv e.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa lv e.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja va :128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja va :102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv e. java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :2 63) at
Re: JAX-RS maturity
Hi At the moment I'm siding towards using JAX-RS via the CXF implementation provided it is pretty stable. If you look at the JAX-RS code you can see it's a pretty simple code and there's a space for a number of enhancements there. Jervis has already done a lot there, and the ability to integrate JAX-RS services through Spring configuration with the core CXF runtime is probably the most critical enhancement. You can expect a better support for multiple formats coming in, perhaps we can see some other features added for it to keep up with Jersey and indeed outperform it in some areas. In the end of the day it's quite a simple specification (JSR 311) so hopefully if you find that some features you'd expect from the CXF implementation missing then it would be simple to add a patch... Cheers, Sergey Hi, I'm currently deciding on a REST framework to use for an upcoming project and have been looking at a number of possibilities including CXF. Just a few quick questions. How mature is the JAX-RS implementation? Will there be a lot of changes in the near future? Have any of you had experience with the Jersey implementation of the JSR311 standard, and if so how does it compare to the CXF implementation? At the moment I'm siding towards using JAX-RS via the CXF implementation provided it is pretty stable. Cheers. -- View this message in context: http://www.nabble.com/JAX-RS-maturity-tp15039120p15039120.html Sent from the cxf-user mailing list archive at Nabble.com. IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: WSS4J - Protection Order
Hi Fred, Yes, sounds interesting. But consider a scenario when I have Sign-Encrypt-Sign or Encrypt-Sign-Encrypt to be done, then the same interceptor need to added twice (before and after the other one). A solution to this will be to see all Actions beforehand and then repeat adding interceptors for repeated Actions accordingly. Also since, we are seeking a generic solution, IMO this will be a bit overhead. Also, each designated WSS4JInterceptors will have their own data structures (cryptos, etc) leading to high memory overhead. The trade-off in the other solution (tweaking SecurityAction, EncryptionAction) is that we have to change WSS4J code. But, a solution to this issue will provide support for ProtectionOrder (SignBeforeEncrypting and EncryptBeforeSigning in WS-Security Policy spec), though not a concern right now. What are you thoughts? With Regards, Mayank Fred Dushin wrote: I see, interesting. In order to do this in a way that does not require a change to CXF, perhaps what you could do is split your encryption and signature actions into 2 separate interceptors, and add a third in between, which peeks at the result of the encryption action (the results object will be on the message), and then programatically configures the WS4JOutInterceptor, which will do the signature action for you. -Fred On Jan 23, 2008, at 12:41 AM, Mayank Mishra wrote: Hi Fred, Yes, you are right. I am talking about the scenario when we have multiple EncryptedData elements and I want to sign only one of them. Yes, I agree XPath would have been much better to handle such scenario. But AFAIK, we can specify parts (WSEncryptionPart) during SignatureAction by initializing part structure with element Id (I guess it is wsu:id, which we can get from map populated during encryptionAction). I am yet to test it. I will let you know about it. With Regards, Mayank Fred Dushin wrote: Hi Mayank, When you say one way to achieve this is to specify the URI of the EncryptedData, do you mean QName, instead of URI? I get the sense from what you are saying that your message may have multiple EncryptedData elements in it, and you want to sign one, but not others. Is that right? If you have only one EncryptedData, then you should be able to direct the WSS4J toolkit to sign it, by specifying the EncryptedData QName, in configuration of the interceptor. Unfortunately, WSS4J does not provide XPath support for protecting (signing/encrypting) message parts, so using QNames is inherently ambiguous. -Fred On Jan 18, 2008, at 2:24 AM, Mayank Mishra wrote: Any reply to this thread will be highly appreciated. Thanking in advance, With Regards, Mayank Mayank Mishra wrote: Hi, Usually we use, Sign and then Encrypt action for any particular xml element. If I want to use Encrypt and then Sign for a particular xml element, then SignatureAction fails to find the xml element. The reason is it has been encrypted and hence corresponding EncryptedData element will be there. One way to achieve this, is to specify, URI of EncryptedData itself in the signature parts. (It should work, though I haven't tested it). But this is not a full proof solution if I want only specific element only to be encrypted and eventually signed. *Is there any mechanism to achieve this?* The only way I can think of achieving this is to maintain a list of wsu:id's of corresponding EncryptedData elements and add URI of them to Signature Parts during .SignatureAction. This may be performed in adding another interceptor which handles the message after encryption has been done. Please let me know your views/suggestions about this. Thanking in advance. :) With Regards, Mayank
RE: Any book written on xfire
+1 SOA Using Java Web Services by Hansen Mike Barlotta Associate Booz | Allen | Hamilton -Original Message- From: Mayank Thakore [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 12:41 AM To: cxf-user@incubator.apache.org Subject: RE: Any book written on xfire I would definitely buy a book if it goes into the details of using cxf. Not just jasws or wsdl or stuff but also about cxf interceptors, arch etc. Regards Mayank This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! -Original Message- From: Adrian Trenaman [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 22, 2008 20:15 To: cxf-user@incubator.apache.org Subject: Re: Any book written on xfire Hi Anshul , I've written a 2-day training course on JAX-WS development using CXF; am delivering a cut down version of this at OOP in Munich later this week. I've been toying with the idea of producing a developer's handbook for CXF; would be interested to know if you think there's a market for it! For the minute, I concur with Glen that the online documentation for CXF is a pretty good start. You might also want to take a look at the Fuse Service Framework documentation, available on open.iona.com http://open.iona.com/documentation/fuse-service-framework-documentation Warm regards, Ade. Glen Mazza-2 wrote: I like Hansen's book[1], although it is about JAX-WS in general (either CXF or GlassFish Metro). Presently our online user's guide[2] is the best source for CXF-specific information. HTH, Glen [1] http://www.jroller.com/gmazza/date/20070809 [2] http://cwiki.apache.org/CXF20DOC/index.html Am Dienstag, den 22.01.2008, 09:09 + schrieb Anshul Dutta: Does any one knows about a good book on xfire or cxf? Or any SOA book that includes these topics? Thanks, ad This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. -- View this message in context: http://www.nabble.com/Any-book-written-on-xfire-tp15015038p15019897.html Sent from the cxf-user mailing list archive at Nabble.com.
Flex and CXF
Just curious if anyone has experiences (good/bad/other) working with Flex and web services in CXF? Any input on pitfalls or approaches is appreciated. Thx, Tony
Leaving CXF for Glasshfish Metro
Hi, After spending about 2 weeks trying to get a very simple service to return JSON in CXF, I found the Glassfish Metro project and it's jaxws-json plugin. I gave it a shot and after 2 hours had my service up and running. Not only that, but the plugin generates pretty api docs at the endpoint for me as well as generates a javascript client on the fly. It was just too easy to make me stick with CXF. I think CXF is probably a good framework, but the docs and examples are in pieces and without real life end-to-end tutorials, it's really hard to get things working. - Jonathan
Re: Leaving CXF for Glasshfish Metro
After spending about 2 weeks trying to get a very simple service to return JSON in CXF, I found the Glassfish Metro project and it's jaxws-json plugin. What's the point of this post ? Say to the world that you're not happpy with CXF ? Or tell everyone that you could've commited a patch after spending 2 days on it but just didn't get enough time :-) ? Cheers, Sergey - Original Message - From: jonathan doklovic [EMAIL PROTECTED] To: cxfuser cxf-user@incubator.apache.org Sent: Wednesday, January 23, 2008 2:37 PM Subject: Leaving CXF for Glasshfish Metro Hi, After spending about 2 weeks trying to get a very simple service to return JSON in CXF, I found the Glassfish Metro project and it's jaxws-json plugin. I gave it a shot and after 2 hours had my service up and running. Not only that, but the plugin generates pretty api docs at the endpoint for me as well as generates a javascript client on the fly. It was just too easy to make me stick with CXF. I think CXF is probably a good framework, but the docs and examples are in pieces and without real life end-to-end tutorials, it's really hard to get things working. - Jonathan IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: Flex and CXF
My understanding is that for Flex (or indeed Silverlight and similar technologies) to work with a given service all that needs to be done is, in case of Flex, to have some MXML[1] created (tools would do it typically) which would link to a service, but for the purpose of the demo it can be done manually. And Flex server side libs should be added to a runtime classpath of a given application. Have you done some Flex before ? It would be interesting to know what need to be dome to FLEX-ify, say, a basic JAX-RS demo. Cheers, Sergey [1] http://en.wikipedia.org/wiki/MXML - Original Message - From: Vespa, Anthony J [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Wednesday, January 23, 2008 2:09 PM Subject: Flex and CXF Just curious if anyone has experiences (good/bad/other) working with Flex and web services in CXF? Any input on pitfalls or approaches is appreciated. Thx, Tony IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: Leaving CXF for Glasshfish Metro
well, i have spent a lot of time getting cxf to work. but migrating from xfire, our code reduced from about 1200 lines to 200 lines. and i find cxf to be very extensible but it's not just coincidence that someone was talking about a book on cxf just today... Regards Mayank On Jan 23, 2008 8:36 PM, jonathan doklovic [EMAIL PROTECTED] wrote: The point being that since this is a users list (not a dev list) I thought I'd share my user experience in hopes that it could help the future of the project. If all anyone hears about a project is how great it is and never hears why people choose not to use it, then it never progresses. I was never able to get CXF working properly simply because of the lack of simple docs and end-to-end examples. Maybe it's just that I don't get it or something, but I feel there are probably a lot of me's out there that struggle with getting things up and running. - Jonathan On Wed, 2008-01-23 at 14:47 +, Sergey Beryozkin wrote: After spending about 2 weeks trying to get a very simple service to return JSON in CXF, I found the Glassfish Metro project and it's jaxws-json plugin. What's the point of this post ? Say to the world that you're not happpy with CXF ? Or tell everyone that you could've commited a patch after spending 2 days on it but just didn't get enough time :-) ? Cheers, Sergey - Original Message - From: jonathan doklovic [EMAIL PROTECTED] To: cxfuser cxf-user@incubator.apache.org Sent: Wednesday, January 23, 2008 2:37 PM Subject: Leaving CXF for Glasshfish Metro Hi, After spending about 2 weeks trying to get a very simple service to return JSON in CXF, I found the Glassfish Metro project and it's jaxws-json plugin. I gave it a shot and after 2 hours had my service up and running. Not only that, but the plugin generates pretty api docs at the endpoint for me as well as generates a javascript client on the fly. It was just too easy to make me stick with CXF. I think CXF is probably a good framework, but the docs and examples are in pieces and without real life end-to-end tutorials, it's really hard to get things working. - Jonathan IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
@ProduceMime support
Hi,
Does CXF support the JSR311 @ProduceMime annotation fully? Here's the code:
import com.sun.ws.rest.api.ConsumeMime;
import com.sun.ws.rest.api.HttpMethod;
import com.sun.ws.rest.api.ProduceMime;
import com.sun.ws.rest.api.UriTemplate;
@UriTemplate(/sampleservlet)
public class SampleServlet {
@HttpMethod(PUT)
@ConsumeMime(text/plain)
@ProduceMime(application/xml)
public void getXML() {
System.out.println(### Handle PUT for sampleservlet: XML ###);
}
@HttpMethod(PUT)
@ConsumeMime(text/plain)
@ProduceMime(application/json)
public void getJSON() {
System.out.println(### Handle PUT for sampleservlet: JSON
###);
}
}
When the client specifies the Accept parameter in the http header as
application/json or application/xml I would expect the corresponding method
to be called according to the @ProduceMime specified before the method. Is
this supported? It doesn't seem to be working as expected for me.
Thanks in advance.
--
View this message in context:
http://www.nabble.com/%40ProduceMime-support-tp15043754p15043754.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Leaving CXF for Glasshfish Metro
If all anyone hears about a project is how great it is and never hears why people choose not to use it, then it never progresses. fair enough, it's a good point Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: JAX-RS maturity
Okay. Thanks for the replies. -- View this message in context: http://www.nabble.com/JAX-RS-maturity-tp15039120p15043875.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: JSON and JAX-RS
On Tuesday 22 January 2008, Vespa, Anthony J wrote: Interesting. Would that mean I would have to use seekAlso and list all of the objects that could possibly be returned - I have currently about six types of custom objects. What if I was returning a type like a boolean or just a string? You should be fine. (although, you probably need to wrapper them with a JAXBElement to get the element name) I think all the stuff that maps to straight xsd schema types are always part of the created JAXBContext. The stuff you need to be careful of are the things that would be generated from the xjc. Dan From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tue 1/22/2008 5:31 PM To: cxf-user@incubator.apache.org Cc: Vespa, Anthony J Subject: Re: JSON and JAX-RS Well, looking at the code, it seems to create a new JAXBContext for each top level type, which really sucks. IMO, it should use our JAXBDatabinding in some way which would allow it/you to configure things via spring or something so one one JAXBContext is created/used that would have all the required types in it. Actually, checking if there is an ObjectFactory in the package and creating the context based on that would also go a long way to helping. That said, with JAXB 2.1, you can probably add an @XmlSeeAlso annation on the wsResponse that points to the wsMessage to make the JAXBContext for the wsResponse be able to marshal the wsMessage as well. Dan On Tuesday 22 January 2008, Vespa, Anthony J wrote: So I spent some time playing with JAX-RS and I seem to have encountered an issue. I can return single objects from my service as JSON (standard Java types as well as my custom objects) but if I try to return my wrapper object which contains an anytype generic list, I get an exception. Effectively I have an object called wsResponse that, in this case, is returning an array of messages (wsMessage) - I have decorated both objects with the XMLType. I am looking into this exception and see references to JAXB; is it possible to get around this? Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Available content types for response is: application/json, Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Response EntityProvider is: org.apache.cxf.jaxrs.provider.JSONProvider Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Response content type is: application/json javax.xml.bind.MarshalException - with linked exception: [javax.xml.bind.JAXBException: class com.cbs.bos.data.ws.wsMessage nor any of its super class is known to this context.] at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java :2 95 ) at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.ja va :1 48) at org.apache.cxf.jaxrs.provider.JSONProvider.writeTo(JSONProvider.java :9 0) at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(J AX RS OutInterceptor.java:99) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercep to rC hain.java:208) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(Ou tg oi ngChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercep to rC hain.java:208) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInit ia ti onObserver.java:78) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(Servle tD es tination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination (S er vletController.java:264) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletCon tr ol ler.java:123) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractC XF Se rvlet.java:170) at org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet(AbstractCX FS er vlet.java:152) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(App li ca tionFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(Application Fi lt erChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapper Va lv e.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContext Va lv e.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve. ja va :128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve. ja va :102) at
Jaxb char mapping
I'm using CXF with jaxws and jaxb. My problem is that the char java types are mapped to xs:unsignedShort (instead of xs:string with size 1 as i expected). I read the jaxb 2.0 specs, but the char primitive type mapping seems not to be defined. There is a quick way to configure/customize jaxb to map char to xs:string? Bye, Marco.
RE: JSON and JAX-RS
Well it turned out that I had too many jaxb jars in my classpath so now the xmlseealso works, but I get this odd exception as an invalid namespace - I'm not quite sure why I'm getting it though, do I need to specify another namespace somewhere? At this point, I'm not specifying it anywhere - my bean.xml looks like... (for this service jaxrs:server id=boardservice address=/ jaxrs:serviceBeans bean class=com.cbs.bos.ws.BoardService / /jaxrs:serviceBeans /jaxrs:server And the exception INFO: Interceptor has thrown exception, unwinding now java.lang.IllegalStateException: Invalid JSON namespace: http://www.w3.org/2001/XMLSchema-instance at org.codehaus.jettison.mapped.MappedNamespaceConvention.getJSONNamespace( MappedNamespaceConvention.java:148) at org.codehaus.jettison.mapped.MappedNamespaceConvention.createAttributeKe y(MappedNamespaceConvention.java:136) at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeAttribute(Mapped XMLStreamWriter.java:89) at com.sun.xml.bind.v2.runtime.output.XMLStreamWriterOutput.attribute(XMLSt reamWriterOutput.java:133) at com.sun.xml.bind.v2.runtime.XMLSerializer.attribute(XMLSerializer.java:4 31) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.j ava:676) at com.sun.xml.bind.v2.runtime.property.ArrayElementNodeProperty.serializeI tem(ArrayElementNodeProperty.java:65) at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeListB ody(ArrayElementProperty.java:168) at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(Array ERProperty.java:152) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInf oImpl.java:322) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializ er.java:589) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInf oImpl.java:312) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java :490) at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:328 ) at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:1 75) at org.apache.cxf.jaxrs.provider.JSONProvider.writeTo(JSONProvider.java:90) at org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.handleMessage(JAXRS OutInterceptor. -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 10:28 AM To: cxf-user@incubator.apache.org Cc: Vespa, Anthony J Subject: Re: JSON and JAX-RS On Tuesday 22 January 2008, Vespa, Anthony J wrote: Interesting. Would that mean I would have to use seekAlso and list all of the objects that could possibly be returned - I have currently about six types of custom objects. What if I was returning a type like a boolean or just a string? You should be fine. (although, you probably need to wrapper them with a JAXBElement to get the element name) I think all the stuff that maps to straight xsd schema types are always part of the created JAXBContext. The stuff you need to be careful of are the things that would be generated from the xjc. Dan From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tue 1/22/2008 5:31 PM To: cxf-user@incubator.apache.org Cc: Vespa, Anthony J Subject: Re: JSON and JAX-RS Well, looking at the code, it seems to create a new JAXBContext for each top level type, which really sucks. IMO, it should use our JAXBDatabinding in some way which would allow it/you to configure things via spring or something so one one JAXBContext is created/used that would have all the required types in it. Actually, checking if there is an ObjectFactory in the package and creating the context based on that would also go a long way to helping. That said, with JAXB 2.1, you can probably add an @XmlSeeAlso annation on the wsResponse that points to the wsMessage to make the JAXBContext for the wsResponse be able to marshal the wsMessage as well. Dan On Tuesday 22 January 2008, Vespa, Anthony J wrote: So I spent some time playing with JAX-RS and I seem to have encountered an issue. I can return single objects from my service as JSON (standard Java types as well as my custom objects) but if I try to return my wrapper object which contains an anytype generic list, I get an exception. Effectively I have an object called wsResponse that, in this case, is returning an array of messages (wsMessage) - I have decorated both objects with the XMLType. I am looking into this exception and see references to JAXB; is it possible to get around this? Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage INFO: Available content types for response is: application/json, Jan 22, 2008 4:45:26 PM org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor handleMessage
Re: JCA demo raises java.lang.UnsupportedOperation when deployed in JBOSS
I tested using JBoss4.0.5 and CXF 2.0.2 as Jeff suggested to the sample, it works. But I still found error messages from JBoss 4.0.5 console. I don't know why there are so many ERRORs? although the sample seems function correctly. Is this bug in CXF? Please see the error messages: == ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl init ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl init ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl setResourceAdapter ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl createConnectionFactory ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory initialiseServants ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory startPropertiesMonitorThread ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.ConnectionFactoryImpl init ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory $EJBServicePropertiesMonitorRunnable run ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory loadProperties ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.ConnectionFactoryImpl getConnection Jeff Zhang-2 wrote: Hi Ade, CXF has tested on Jboss 4.0.x in release. We can do work on Jboss 4.2.x if you need. Could you raise a JIRA? Thanks Jeff - Original Message - From: Adrian Trenaman [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Friday, August 17, 2007 6:03 PM Subject: JCA demo raises java.lang.UnsupportedOperation when deployed in JBOSS Hi, Has anyone experienced any problems deploying the JCA adaptor into JBoss? I was experiencing problems and have reproduced with the demo in samples/integration/jca/hello_world. When the servlet invokes on the proxy, we get: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAP Message I'm using JDK 1.5.0_09, CXF 2.0.1 and JBoss 4.2.1. Have also gotten the same problem with JBoss 5.0.0 Beta 2. Google shows that others have also experienced this problem; some workarounds are suggested around putting libraries (jboss-jaxrpc.jar, jboss-saaj.jar, jaxb-api.jar and jaxws-api.jar) into the JBoss lib/endorsed directory. I note that the demo already places files in lib/endorsed - do we need to add more? Finally (I'm not sure whether this is related or not) - I'm noting that the stack trace uses CXF classes right down to sun.reflect.NativeMethodAccessorImpl, and then JBossWS classes are used to create the SOAP message. is this right? I would have thought that the entire interaction should be handled by CXF classes? Curious, Ade. -- View this message in context: http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tf4284807.html#a12197014 Sent from the cxf-user mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tp12197014p15045592.html Sent from the cxf-user mailing list archive at Nabble.com.
cxf-eclipse-plugin
Hi, Anybody's has used CXF-Plugin, want to share your experience ? Does anybody know if this plugin will make it to production ? And if this will be available as a standard Eclipse plugin with Features and Site.xml Thanx -yogen -Original Message- From: Yadav, Yogendra (IT) Sent: Friday, January 18, 2008 10:40 AM To: [EMAIL PROTECTED] Subject: cxf-eclipse-plugin Hi, What is the plan on including Features in the CXF Eclipse Plugin zip file, like standard eclipse plugins do ? And what is the plan on providing site.xml for this plugin so that I can update plugin from Eclipse directly ? Thanx -yogen NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
RE: Flex and CXF
I have only done some basic Flex work in the past myself, which is why I am soliciting experiences. -Original Message- From: Sergey Beryozkin [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 10:04 AM To: cxf-user@incubator.apache.org Subject: Re: Flex and CXF My understanding is that for Flex (or indeed Silverlight and similar technologies) to work with a given service all that needs to be done is, in case of Flex, to have some MXML[1] created (tools would do it typically) which would link to a service, but for the purpose of the demo it can be done manually. And Flex server side libs should be added to a runtime classpath of a given application. Have you done some Flex before ? It would be interesting to know what need to be dome to FLEX-ify, say, a basic JAX-RS demo. Cheers, Sergey [1] http://en.wikipedia.org/wiki/MXML - Original Message - From: Vespa, Anthony J [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Wednesday, January 23, 2008 2:09 PM Subject: Flex and CXF Just curious if anyone has experiences (good/bad/other) working with Flex and web services in CXF? Any input on pitfalls or approaches is appreciated. Thx, Tony IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: JCA demo raises java.lang.UnsupportedOperation when deployed in JBOSS
This ERROR is not a problem, because cxf uses the java.util.logger as default, but jboss uses the log4j, so the log level is a bit of different. you can config the log by using log4j one's in the cxf, and then the ERROR would go away. On Jan 24, 2008 12:42 AM, YI (William) ZHU [EMAIL PROTECTED] wrote: I tested using JBoss4.0.5 and CXF 2.0.2 as Jeff suggested to the sample, it works. But I still found error messages from JBoss 4.0.5 console. I don't know why there are so many ERRORs? although the sample seems function correctly. Is this bug in CXF? Please see the error messages: == ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl init ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl init ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.AssociatedManagedConnectionFactoryImpl setResourceAdapter ... ERROR [STDERR] ... org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl createConnectionFactory ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory initialiseServants ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory startPropertiesMonitorThread ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.ConnectionFactoryImpl init ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory $EJBServicePropertiesMonitorRunnable run ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.JCABusFactory loadProperties ... ERROR [STDERR] ..org.apache.cxf.jca.cxf.ConnectionFactoryImpl getConnection Jeff Zhang-2 wrote: Hi Ade, CXF has tested on Jboss 4.0.x in release. We can do work on Jboss 4.2.xif you need. Could you raise a JIRA? Thanks Jeff - Original Message - From: Adrian Trenaman [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Friday, August 17, 2007 6:03 PM Subject: JCA demo raises java.lang.UnsupportedOperation when deployed in JBOSS Hi, Has anyone experienced any problems deploying the JCA adaptor into JBoss? I was experiencing problems and have reproduced with the demo in samples/integration/jca/hello_world. When the servlet invokes on the proxy, we get: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAP Message I'm using JDK 1.5.0_09, CXF 2.0.1 and JBoss 4.2.1. Have also gotten the same problem with JBoss 5.0.0 Beta 2. Google shows that others have also experienced this problem; some workarounds are suggested around putting libraries (jboss-jaxrpc.jar, jboss-saaj.jar, jaxb-api.jar and jaxws-api.jar) into the JBoss lib/endorsed directory. I note that the demo already places files in lib/endorsed - do we need to add more? Finally (I'm not sure whether this is related or not) - I'm noting that the stack trace uses CXF classes right down to sun.reflect.NativeMethodAccessorImpl, and then JBossWS classes are used to create the SOAP message. is this right? I would have thought that the entire interaction should be handled by CXF classes? Curious, Ade. -- View this message in context: http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tf4284807.html#a12197014 Sent from the cxf-user mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/JCA-demo-raises-java.lang.UnsupportedOperation-when-deployed-in-JBOSS-tp12197014p15045592.html Sent from the cxf-user mailing list archive at Nabble.com. -- Thanks Jeff
Re: Flex and CXF
We are developing a project that utilizes both CXF and Flex. In Flex, there are 3 ways to make a remote call: Http service, Web Service and remote object based on AMF protocol. It is very convenient to have a CXF service layer on top of JPA entity classes. Here I guess you have few options: You can either manually call web services from Flex and lastResult method in webservice object gives you the call result or you can use enunciate framework. Currently, I am doing the first way and not familiar with the second way but it might be valueable to investigate. Hope it helps. Mustafa On Jan 23, 2008 4:09 PM, Vespa, Anthony J [EMAIL PROTECTED] wrote: Just curious if anyone has experiences (good/bad/other) working with Flex and web services in CXF? Any input on pitfalls or approaches is appreciated. Thx, Tony -- Mustafa Egilmezbilek
Re: @ProduceMime support
I'm seeing the same thing here, no matter what I do the runtime seems to
want to dispatch the call to the method annotated application/json. I
also noted that it isn't possible to annotate a single method with
multiple mime types. i.e. per the dec4th jsr311 draft it should be
possible t0 annotate a method with the following:
@ProduceMime(application/xml, application/json)
alas, this doesn't appear to be supported in cxf yet. I guess we should
log JIRA's for these.
--Frank
On Wed, 2008-01-23 at 07:12 -0800, brmaguir wrote:
Hi,
Does CXF support the JSR311 @ProduceMime annotation fully? Here's the code:
import com.sun.ws.rest.api.ConsumeMime;
import com.sun.ws.rest.api.HttpMethod;
import com.sun.ws.rest.api.ProduceMime;
import com.sun.ws.rest.api.UriTemplate;
@UriTemplate(/sampleservlet)
public class SampleServlet {
@HttpMethod(PUT)
@ConsumeMime(text/plain)
@ProduceMime(application/xml)
public void getXML() {
System.out.println(### Handle PUT for sampleservlet: XML ###);
}
@HttpMethod(PUT)
@ConsumeMime(text/plain)
@ProduceMime(application/json)
public void getJSON() {
System.out.println(### Handle PUT for sampleservlet: JSON
###);
}
}
When the client specifies the Accept parameter in the http header as
application/json or application/xml I would expect the corresponding method
to be called according to the @ProduceMime specified before the method. Is
this supported? It doesn't seem to be working as expected for me.
Thanks in advance.
Client throws No NamespaceURI exception from server SOAP fault
I am writing a client to a VMWare management web service. In working
with the API, I made a mistake and a SOAP fault was thrown. That is not
the problem. Instead of an WSDL generated exception class being thrown,
I got what appears to be a validation error during parsing of the SOAP
fault. I found someone who had a similar issue, but am not sure whether
the problem is my code, the VMWare web service, or CXF. It would seem
to me that if a web service operation would automatically utilize the
schemas associated with the Service created from the WSDL. The previous
mailing list poster said he solved the problem by using the Java.Net
RI. However, the CXF web site listing the dependencies say the saaj
being used is the Sun 1.3 RI. I am using Maven2 to pull in all the
necessary libraries as well as building the client code from the WSDL.
If anyone can shed some light on what the problem might be, I would be
very grateful.
I did write some code to try and verify the schema associated with the
web service:
ListServiceInfo serviceInfos =
client.getEndpoint().getService().getServiceInfos();
for (ServiceInfo serviceInfo : serviceInfos) {
Schema schema = EndpointReferenceUtils.getSchema( serviceInfo );
LOG.info( Schema = + serviceInfo.getName().toString() +
\n + schema.toString() );
}
Its output was:
INFO: Creating Service {urn:vim2Service}VimService from WSDL:
http://127.0.0.1:8080/sdk/vimService?wsdl
2008-01-23 16:56:08,780 INFO main SampleClient.afterPropertiesSet:158]
Schema = [EMAIL PROTECTED]
The vimService.wsdl imports another WSDL, vim.wsdl, which contains most
of the schema information. I was trying to verify that the imported
schema was being properly associated with the service. You can see from
above that the service/namespace is urn:vim2Service. However, only
one service/namespace is listed. The imported WSDL's schema's
namespace, urn:vim2, is not shown and I do not know whether this is a
problem.
The previous posting can be found at the following URL:
http://mail-archives.apache.org/mod_mbox/incubator-cxf-user/200709.mbox/[EMAIL
PROTECTED]
Below is the SOAP fault message that caused the exception and below that
is the stack trace. Some relevant fragments from the imported WSDL are:
element name=InvalidRequestFault type=vim2:InvalidRequest/
message name=InvalidRequestFaultMsg
part name=fault element=vim2:InvalidRequestFault /
/message
The target namespace for these schema elements were
xmlns:vim2=urn:vim2. SOAP fault message:
?xml version=1.0 encoding=UTF-8?
soapenv:Envelope xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:Body
soapenv:Fault
faultcodeServerFaultCode/faultcode
faultstringspecSet/faultstring
detail
InvalidRequestFault xmlns=urn:vim2
xsi:type=InvalidRequest/
/detail
/soapenv:Fault
/soapenv:Body
/soapenv:Envelope
I believe that this line is causing the problem, but should the contents
of the detail element even be validated?
InvalidRequestFault xmlns=urn:vim2 xsi:type=InvalidRequest/
Here is the stack trace:
Jan 23, 2008 4:56:09 PM com.sun.xml.messaging.saaj.soap.impl.FaultImpl
setFaultCode
SEVERE: SAAJ0140: No NamespaceURI, SOAP requires faultcode content to be
a QName
java.lang.reflect.UndeclaredThrowableException
at $Proxy32.retrieveProperties(Unknown Source)
at
com.reflexsecurity.vmware.SampleClient.retrieveProperties(SampleClient.java:216)
at com.reflexsecurity.vmware.SampleClient.main(SampleClient.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: No
NamespaceURI, SOAP requires faultcode content to be a QName
at
com.sun.xml.messaging.saaj.soap.impl.FaultImpl.setFaultCode(FaultImpl.java:101)
at
com.sun.xml.messaging.saaj.soap.impl.FaultImpl.setFaultCode(FaultImpl.java:138)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:155)
... 8 more
Failed to retrieve properties.
2008-01-23 16:56:09,872 ERROR main SampleClient.main:96] Failed to
retrieve properties
java.lang.reflect.UndeclaredThrowableException
at $Proxy32.retrieveProperties(Unknown Source)
at
com.reflexsecurity.vmware.SampleClient.retrieveProperties(SampleClient.java:216)
at com.reflexsecurity.vmware.SampleClient.main(SampleClient.java:82)
at
Re: Creating and publishing services from wsdl
Basically I'm aiming at deploying many strongly typed services defined in the wsdl, but servicing each of them using a generic (existing) mechanism. If I declare each wsdl defined service in a jaxws:endpoint / then they load and publish successfully. I've subclassed the service factory to do things like rename the loaded endpoints to get rid of the generic implementor names.. The config -- jaxws:endpoint id=barthenticator implementor=ews.service.Implementor wsdlLocation=BarthenticatorService.wsdl address=/Barthenticator serviceName=tns:BarthenticatorService xmlns:tns=http://connectivity.ews/; jaxws:serviceFactory bean class=service.factory.EWSServiceFactoryBean / /jaxws:serviceFactory /jaxws:endpoint jaxws:endpoint id=bazthenticator implementor=ews.service.Implementor wsdlLocation=BazthenticatorService.wsdl address=/Bazthenticator serviceName=tns:BazthenticatorService xmlns:tns=http://connectivity.ews/; jaxws:serviceFactory bean class=com.mincom.ews.service.factory.EWSServiceFactoryBean / /jaxws:serviceFactory /jaxws:endpoint jaxws:endpoint id=Foothenticator implementor=ews.service.Implementor wsdlLocation=FoothenticatorService.wsdl address=/Foothenticator serviceName=tns:FoothenticatorService xmlns:tns=http://connectivity.ews/; jaxws:serviceFactory bean class=com.mincom.ews.service.factory.EWSServiceFactoryBean / /jaxws:serviceFactory /jaxws:endpoint Ideally I'd like to achieve all of this programatically - i.e. without having to knock together a big config file. Has anyone done something like this before? Rob
Re: Creating and publishing services from wsdl
Ideally I'd like to achieve all of this programatically - i.e. without having to knock together a big config file. All that spring config corresponds to plain old Java objects. Some of them are even specified by the JAX-WS specification :-) Beyond the stock JAXWS API, all of CXF can be configured programmatically, so you can, indeed, stamp these things out like cookies. See the user guide section on non-spring configuration.
Re: Creating and publishing services from wsdl
that's what i'm looking for - got a url? On Jan 24, 2008 12:46 PM, Benson Margulies [EMAIL PROTECTED] wrote: Ideally I'd like to achieve all of this programatically - i.e. without having to knock together a big config file. All that spring config corresponds to plain old Java objects. Some of them are even specified by the JAX-WS specification :-) Beyond the stock JAXWS API, all of CXF can be configured programmatically, so you can, indeed, stamp these things out like cookies. See the user guide section on non-spring configuration.
Re: Creating and publishing services from wsdl
On Thu, 2008-01-24 at 12:54 +1000, Rob Barrett wrote: that's what i'm looking for - got a url? See what the following page does for you. I'm not 100% sure that I'm following your thread, but if you could express it in Spring, you can do it here. http://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html#AsimpleJAX-WSservice-Publishingyourservice On Jan 24, 2008 12:46 PM, Benson Margulies [EMAIL PROTECTED] wrote: Ideally I'd like to achieve all of this programatically - i.e. without having to knock together a big config file. All that spring config corresponds to plain old Java objects. Some of them are even specified by the JAX-WS specification :-) Beyond the stock JAXWS API, all of CXF can be configured programmatically, so you can, indeed, stamp these things out like cookies. See the user guide section on non-spring configuration.
Re: Creating and publishing services from wsdl
thanks, will give that a go. On Jan 24, 2008 1:02 PM, Benson Margulies [EMAIL PROTECTED] wrote: On Thu, 2008-01-24 at 12:54 +1000, Rob Barrett wrote: that's what i'm looking for - got a url? See what the following page does for you. I'm not 100% sure that I'm following your thread, but if you could express it in Spring, you can do it here. http://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html#AsimpleJAX-WSservice-Publishingyourservice On Jan 24, 2008 12:46 PM, Benson Margulies [EMAIL PROTECTED] wrote: Ideally I'd like to achieve all of this programatically - i.e. without having to knock together a big config file. All that spring config corresponds to plain old Java objects. Some of them are even specified by the JAX-WS specification :-) Beyond the stock JAXWS API, all of CXF can be configured programmatically, so you can, indeed, stamp these things out like cookies. See the user guide section on non-spring configuration.
