Re: How to customize the wsdl attributes for methdos with annotations?

2011-09-30 Thread Daniel Kulp
On Friday, September 30, 2011 4:45:22 PM César Correia wrote: > Hello All! > How to customize the wsdl attributes for methdos with annotations? > > With @XmlElement(rquired=true) I managed to change minOccurs in wsdl for > class properties (mapped to complex type). I'd like to do the same with > m

Re: Sharing JAXB annotated classes and context between server and client.

2011-09-30 Thread Johan Edstrom
Doing it on the client will require a bit more work… The jaxb client is pretty smart in caching what it needs, not re-creating stuff and so on. On Sep 30, 2011, at 8:19 AM, paragmehta wrote: > Thanks, trying it on server. > > Hope it makes sense to allow such a thing on the client side too.

Re: Sharing JAXB annotated classes and context between server and client.

2011-09-30 Thread paragmehta
Thanks, trying it on server. Hope it makes sense to allow such a thing on the client side too. I.e. one may a client to it's own server and having separate set of classes for client with their own JAXB customizations does not make sense. I suppose I should create an enhancement request. Thanks,

Antwort: Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread smixdev
This is what worked with 2.2: Jens

Re: CoordinatorThread[] slow alarm

2011-09-30 Thread Mark juszczec
Benson Thank you. As soon as I sent the email, I figured it out. Mark On Fri, Sep 30, 2011 at 3:58 PM, Benson Margulies wrote: > These aren't CXF messages at all. CXF does not embed caucho. > > On Fri, Sep 30, 2011 at 2:29 PM, Mark juszczec > wrote: > > Hello all > > > > We were in the middl

Re: CoordinatorThread[] slow alarm

2011-09-30 Thread Benson Margulies
These aren't CXF messages at all. CXF does not embed caucho. On Fri, Sep 30, 2011 at 2:29 PM, Mark juszczec wrote: > Hello all > > We were in the middle of a demo when the web app using my CXF based service > slowed to a crawl. > > resin.stdout contained: > > [2011-09-30 13:44:02.543] Coordinator

How to customize the wsdl attributes for methdos with annotations?

2011-09-30 Thread César Correia
Hello All! How to customize the wsdl attributes for methdos with annotations? With @XmlElement(rquired=true) I managed to change minOccurs in wsdl for class properties (mapped to complex type). I'd like to do the same with method parameters using annotations. Is it possible? Thanks in advance! C

CoordinatorThread[] slow alarm

2011-09-30 Thread Mark juszczec
Hello all We were in the middle of a demo when the web app using my CXF based service slowed to a crawl. resin.stdout contained: [2011-09-30 13:44:02.543] CoordinatorThread[] slow alarm Alarm[alarm[com.caucho.server.admin.JniNetStat@1c04298e]] 28822ms [2011-09-30 13:44:02.543] CoordinatorThread[

Re: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Sergey Beryozkin
Hmm... Sorry, can you please double-check that ExtendedJSONProvider does not feature anyware in a stack trace ? I'll add a test on my own a bit later on, I have few tests where customized JAXB and JSON providers are used (these are effectively overriding default ones), Will get back to you asa

RE: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Muller, Anthony
Yep, classes are bundlized and deployed in an osgi environment. And yes, I imported "javax.ws.rs.ext". As I said, my provider is well instantiated but JSONProvider seems to have an higher priority. Regards, Anthony -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com

Re: Marshalling REST Query Parameter directly into Integer Array

2011-09-30 Thread Kiren Pillay
Hi Sergery, List works well, thanks for your help:) Moved to 2.4.2 also. Regards Kiren On Thu, Sep 29, 2011 at 2:33 PM, Sergey Beryozkin wrote: > Hi > > There was a minor issue to do with handling arrays such as Integer[], but I > can see no problems with List. I committed a test involving > L

Re: How to customize the wsdl attributes for methdos with annotations?

2011-09-30 Thread César Correia
How to customize the wsdl attributes for methdos with annotations? With @XmlElement(rquired=true) I managed to change minOccurs in wsdl for class properties (mapped to complex type). I'd like to do the same with method parameters using annotations. Is it possible? Thanks in advance! Cesar.

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Christian Schneider
Hi Jens, why do you set replyDestination and replyToDestination to different names? I don´t think that this can work. The JMSConduit will always specify the replyDestination in the message it sends out. So the server should always send the reply there. When receiving the JMSConduit will use t

Re: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Sergey Beryozkin
Hi I've checked that the code in CXF 2.3.3, CXF 2.4.2 and 2.5.0 that deals with getting providers from Applications is identical and I have a test where exception mappers are registered from CXFNonSpringJaxrsServlet and Application. I'm wondering if it is an OSGI issue ? Do you have javax.ws

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Jens
Hi Christian, that won't work, primarily because I'm not allowed to use temporary queues (company policy) and the server is listening on a remote queue manager, so if I leave out replyToDestination it won't know where to send the reply. Jens Christian Schneider wrote: > > Hi Jens, > > why don

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Christian Schneider
Hi Jens, why don´t you simply leave out replyDestination, replyToDestination, useConduitIdSelector, conduitIdSelectPrefix. Then cxf will use a temp queue for replies and the correlation should still work. Can you try this with the newest CXF? Christian Am 30.09.2011 15:25, schrieb Jens: T

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Jens
This is what worked with 2.2 (angle brackets replaced to get through Nabble): [bean id="jmsConfig" class="org.apache.cxf.transport.jms.JMSConfiguration"] [property name="connectionFactory" ref="jmsConnectionFactory"/] [property name="targetDestination" value="queue:///out.queue?targetCli

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Christian Schneider
Can you post your config? Christian Am 30.09.2011 14:00, schrieb Jens: Hi Christian, thanks for your reply. I had a look at the code, too. I guess my problem is that I need to a conduitSelectorPrefix with WebSphere MQ ("ID:"), otherwise CXF cannot correlate anything at all. My attempts to h

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Jens
Hi Christian, thanks for your reply. I had a look at the code, too. I guess my problem is that I need to a conduitSelectorPrefix with WebSphere MQ ("ID:"), otherwise CXF cannot correlate anything at all. My attempts to hack the conduit to support this have unfortunately not been successful so fa

RE: Question about web services

2011-09-30 Thread David Sills
All: I didn't get an answer to my original question, but still need one - just asking. The documentation for how to make a web service that is only accessible using HTTPS is, in any case, pretty thin. I'm happy to add to it if someone can point me in the right direction. One thing I'm also confus

Re: JMS Message Correlation in CXF 2.3+

2011-09-30 Thread Christian Schneider
Hi jens, sorry for the delay. I just created a testcase for this as I found none that was testing this case. See below for the algorithm to determine the correlation id to send out. So if you do not set a conduitSelectorPrefix and use a sync call and do not set useConduitIdSelector then it sh

RE: Non CFX clients for CFX web services

2011-09-30 Thread David Sills
Tim: I would strongly suggest you try doing the code generation using wsdl2java; your code should work then. If that's true, then you can try narrowing the issues. You don't necessarily have to continue to use the generated code (though I do so) but it should help you center in on the problems. D

RE: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Muller, Anthony
Thanks for your help Sergey. Sorry, it's configured through an Application instance! Anthony -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: vendredi 30 septembre 2011 12:14 To: users@cxf.apache.org Subject: Re: CXF 2.3.3 - JSON output - java.lang.IllegalSt

Re: Interceptor implementation - how to find current location

2011-09-30 Thread Willem Jiang
You can use below code to tell if the messsage is from client. Boolean.TRUE.equals(message.get(Message.REQUESTOR_ROLE)) On Fri Sep 30 17:40:10 2011, Gerald Preissler wrote: I'm implementing an interceptor for CXF and am looking for a way to programmatically determine where the interceptor is ac

Interceptor implementation - how to find current location

2011-09-30 Thread Gerald Preissler
I'm implementing an interceptor for CXF and am looking for a way to programmatically determine where the interceptor is actually being called during processing, i.e. I want to know whether the interceptor is being run on the client or the service side and in the outgoing or incoming interceptor

Re: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Sergey Beryozkin
That looks OK. How do you register it ? From Application instance or via servlet init params ? Give me more info please Cheers, Sergey On 30/09/11 11:10, Muller, Anthony wrote: Yes, it's what I did. Do you see something wrong? import javax.ws.rs.Consumes; import javax.ws.rs.Produces; import

RE: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Muller, Anthony
Yes, it's what I did. Do you see something wrong? import javax.ws.rs.Consumes; import javax.ws.rs.Produces; import javax.ws.rs.ext.Provider; import org.apache.cxf.jaxrs.provider.JSONProvider; @Produces({"application/json"}) @Consumes({"application/json"}) @Provider public class ExtendedJSONProv

Re: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Sergey Beryozkin
Hi, yea it does, but as I said CXF (CXFNonSpringJaxrsServlet) does not check superclasses for @Provider which will need to be fixed, so for now please add another @Provider to your custom provider and that will do - Cheers, Sergey On 30/09/11 10:47, Muller, Anthony wrote: Hi Sergey, Are you

RE: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Muller, Anthony
Hi Sergey, Are you sure that "org.apache.cxf.jaxrs.provider.JSONProvider" doesn't have the @Provider annotation? I found it in "cxf-2.3.3.jar" yet :-/ Anthony -Original Message- From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] Sent: vendredi 30 septembre 2011 11:20 To: users@cxf

Re: Non CFX clients for CFX web services

2011-09-30 Thread Glen Mazza
I have a Java-first example here: http://www.jroller.com/gmazza/entry/java_first_web_service On 09/30/2011 01:12 AM, Tim wrote: Thanks, Glen Mazza. I'll learn you tutorial. But my problem is is slightly different. I don't create a WSDL-first web service. I don't use wsdl at all and create web

Re: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Sergey Beryozkin
Hi Anthony How do you register it, using jaxrs.providers parameter ? A custom provider should be preferred to a default one. That warning suggests that you probably use a jaxrs.serviceClasses parameter ? Or do use register it from the Application implementation ? In that case this custom prov

Re: The signature or decryption was invalid

2011-09-30 Thread Colm O hEigeartaigh
For the record, the problem was in the use of openjdk 1.6.0. Colm. On Thu, Sep 29, 2011 at 9:02 AM, yannick wrote: > I found some posts that this problem would be solved in cxf 2.4.1 - snapshot > ... So I tried to change to 2.4.1 to see if it gives a difference but still > same problem. > > The

RE: CXF 2.3.3 - JSON output - java.lang.IllegalStateException: Invalid JSON namespace

2011-09-30 Thread Muller, Anthony
Hey Sergey, I'm trying to follow your advice and I inherited from JSONProvider class and just set "ignoreNamespace" to true. At the beginning, I didn't inherit from JSONProvider, but only instantiated this class, set the "ignoreNamespace" property and add it as a provider: however I get an exc

Re: Non CFX clients for CFX web services

2011-09-30 Thread Tim
Willem.Jiang wrote: > > You can access the WSDL with is generated from the CXF service from this > url http://localhost:8080/trainCFX/HelloWorld?WSDL. > I knew about it. I got wsdl description (see first post) this way. Willem.Jiang wrote: > > I just have a quick look at the AxisClient, it

Re: Non CFX clients for CFX web services

2011-09-30 Thread Tim
Willem.Jiang wrote: > > You can access the WSDL with is generated from the CXF service from this > url http://localhost:8080/trainCFX/HelloWorld?WSDL. > I knew about it. I got wsdl description (see first post) this way. Willem.Jiang wrote: > > I just have a quick look at the AxisClient, it

Re: Non CFX clients for CFX web services

2011-09-30 Thread Willem Jiang
You can access the WSDL with is generated from the CXF service from this url http://localhost:8080/trainCFX/HelloWorld?WSDL. I just have a quick look at the AxisClient, it looks it still use the JAXRPC API which is replaced by JAXWS. That could explain why you AxisClient can get the right resp