Hi
You have the following payload
getOrderPaymentMethodRequest
orderId23544619/orderId /getOrderPaymentMethodRequest
but it only works for SOAP as the JAXWS runtime ensures the Orderrequest bean
is populated out of thid request XML...
for plain HTTP invocations it has to be something
Hi
Thank you so much Sergey for prompt reply and the links.
I agree that JAX-RS might be more appropriate solution to my problem.
But I still has a query about Response object. As you see, I need to read
the phisical XML files that are stored on file system and based on user
query parameter,
Hi
In addition to what other have said, I'd also like to add that it is also possible to configure the client runtime to mantain a
current session (provided cookies are used), using an org.apache.cxf.message.Message.MAINTAIN_SESSION property, should work for both
JAXWS JAXRS...
cheers,
Is there any particular reason why a normal HTTP session cookie cannot be
used?Doing it that way allows a lot of powerful things like using the
Spring AOP stuff to provide a stateful object per session, etc...
By default, sessions are turned off on the client, but they are easy to turn
Hi!
I'm wondering, where wsdl2java gets the information what to put into
the @WebService-Annotation.
I'm throwing a WSDL with the following entries at wsdl2java:
wsdl:portType name=NameSoap
/wsdl:portType
wsdl:binding name=NameSoap type=tns:NameSoap
wsdl:service name=Name
Per spec, it's not supposed to (and if we did, it would fail the TCK). The
serviceName (and portName) attribute is for the service implementation only.
The interface represents the portType which can be used by several
services/ports/bindings and thus does not get those attributes set.
Hi !
I'm trying to figure out how to pickup all exceptions (including
IllegalArgument, NPE, etc)
that may be thrown from custom IN interceptors as well as Port Impls such
that I would be able to wrap it up in MyWebFault which has defined
ERROR_CODEs exposed through WSDL.
I see that there are
Hi, I'm using CXF 2.2.3 and am consuming a service where the address is
defined in the wsdl like so:
.
...
wsdl:service name=ServiceName
wsdl:port name=ServiceName_Port binding=tns1:ServiceName_Binder
soap:address location=http://[*A**ddressNotReachebleFromInternet*
Hi, I'm using CXF 2.2.3 and am consuming a service where the address is
defined in the wsdl like so:
.
...
wsdl:service name=ServiceName
wsdl:port name=ServiceName_Port binding=tns1:ServiceName_Binder
soap:address location=http://[*A**ddressNotReachebleFromInternet*
I tried that too. I am getting this exception.
09:05:44,793 ERROR [STDERR] Nov 18, 2009 9:05:44 AM
org.apache.cxf.interceptor.LoggingInInterceptor logging
INFO: Inbound Message
ID: 2
Address:
/paymentapi/stubHubPaymentJaxwsJaxrs_rest/payment/getorderpaymentmethod
Can someone give me a recipe to add cache control headers to ALL responses
from my JAX-RS service?
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Wednesday, November 18, 2009 9:10 AM
To: cxf-u...@incubator.apache.org
Subject: JAX-RS and cache-control
Can someone give me a recipe to add cache control headers to ALL
responses
from my JAX-RS
You have @XmlRootElement(name = OrderRequest)
I didn't pay any attention to it,
OrderRequest
orderId23544619/orderId
/OrderRequest
should do. It's really a JAXB issue
cheers, Sergey
- Original Message -
From: Pydipati, Karuna kpydip...@stubhub.com
To: users@cxf.apache.org
Sent:
Hello:
I am running into some name space issues in my jax-ws client using the
code below.
When I try to consume a service that was created with CXF, I get the
correct request. However, when I use the same code the consume a service
that was creating using a different tool kit, but the same
Sure, it should actually work for JAXWS services too...Or doing the same in the
CXF custom out interceptor (MARSHAL phase for ex)
That said, few more options are available at the (CXF) JAX-RS level :
- register a custom ResponseHandler filer and override the JAXRS Response by adding a
I tried all possible combinations. This one is failing with different
error. I never felt so difficulty with REST on CXF. This appears to be
very simple one. But, it is taking most of my energy.
Is it because I have annotated interface with both JAX-WS and JAX-RS?
09:23:31,125 ERROR [STDERR] Nov
This is part of the JAX-WS spec:
((BindingProvider)proxy).getRequestContext()
.put(BindingProvider.ENDPOINT_ADDRESS, http//ActualReachableAddress/)
Dan
On Wed November 18 2009 11:47:53 am Guðmundur Stefán Þorvaldsson wrote:
Hi, I'm using CXF 2.2.3 and am consuming a service where the
I'm sorry, but I have no idea what is going on. This time it's actually a different exception, it seems that the stream had already
been read by the time Unmarshaller tried to read...
Lets step back a bit and try to narrow the problem.
How about you temporarily removing JAXWS annotations
One way of achieving this is to stick an interceptor very early in the
FaultOut chain that would get the chain from the message and manipulate the
chain. Adding your own interceptors if needed, removing those you don't
want, etc... The chains are completely modifiable at run time during
Saw this thread:
http://osdir.com/ml/users-cxf-apache/2009-09/msg00014.html
but am wondering how this would be done in a config file. I saw an example
somewhere that says to use:
bean id=jaxbProvider
class=org.apache.cxf.jaxrs.provider.JAXBElementProvider
property
I really don't want to do this at the servlet level, I want it to work in
embedded jetty.
Can you point me at an example of registering a ResponseHandler for my
entire service?
On Wed, Nov 18, 2009 at 12:25 PM, Sergey Beryozkin sbery...@progress.comwrote:
Sure, it should actually work for
Sorry... I meant to say that the primary docs (for JAX-RS in CXF) is where I
got the same XML from. It doesn't work for me, though. So, I went looking
online, and found the osdir.com reference to doing it programmatically.
Regardless, just looking to get it to work via a configuration
Dan,
I was thinking of making a custom WebFaultOutInterceptor and inserting it
before the default one in the PRE_PROTOCOL phase.
Could you tell me how to remove the default WebFaultOutInterceptor from the
chain?
Thanks,
-Vitaly
dkulp wrote:
One way of achieving this is to stick an
On Wed November 18 2009 2:11:55 pm vickatvuuch wrote:
Dan,
I was thinking of making a custom WebFaultOutInterceptor and inserting it
before the default one in the PRE_PROTOCOL phase.
Could you tell me how to remove the default WebFaultOutInterceptor from the
chain?
Probably call
Thanks Sergey,
I have given a try with JAX-RS and I am able to return my XML file. I have
created a resource class where I defined a method. This method get
HttpResponse object from MessageContext, read XML file from file system and
then feeding it to HttpResponse outputstream. Please let me
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Wednesday, November 18, 2009 10:42 AM
To: users@cxf.apache.org
Cc: cxf-u...@incubator.apache.org
Subject: Re: JAX-RS and cache-control
I really don't want to do this at the servlet level, I want it to
David,
I have a JAX-RS service implemented in CXF. I can launch it from jetty:run.
I can launch it with the embedded CXF Jetty transport. I do not want to have
to be editing a web.xml to configure a filter. I want to tweak the headers
of all of the functions in it.
So this the response filter
The Apache CXF team is proud to announce the availability of the latest
patches for the fixes branches: 2.2.5 and 2.1.8
Apache CXF is an open source services framework. CXF helps you build and
develop services using front end programming APIs, like JAX-WS and JAX-RS.
These services can speak
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Wednesday, November 18, 2009 11:51 AM
To: users@cxf.apache.org
Subject: Re: JAX-RS and cache-control
David,
I have a JAX-RS service implemented in CXF. I can launch it from
jetty:run.
I can launch
After lots of trial and error, here is what I found. Still, I could not
solve this issue.
When I have the interface function like this, it WORKS. Please note that
it has only one argument.
@Path(/getorderpaymentmethod2)
@POST
public GetOrderPaymentMethodResponse
Hi
Thanks for confirming it. In fact, it occurred to me on the way back
home that you posted AuthHeader being a JAXB bean.
You see, as I noted in the earlier post, when you were asking how to
handle AuthHeader in a RESTful call, in SOAP you have an envelope which
wraps two XML fragments, like
Hi,
I have developed JAX-RS webservice in my spring application. my further
requirement is to communicate this service through Https. I am novice user.
Please let me know any good documents or other resource from where I get
more information about it and can try out implementation of https with
Hi
This is one possible option, another one is to return a Response :
return Response.status(200).entity(theInputStream).build()
cheers, Sergey
-Original Message-
From: Parimal Dhinoja [mailto:pdhin...@gmail.com]
Sent: 18 November 2009 19:46
To: users@cxf.apache.org
Subject: Re:
Hi
I'm sorry, that property has to be of type java.lang.Boolean according
to the Marshaller docs. I'm not sure right now how to specify from
Spring that a given map value should be of Boolean type, does anyone
know how to do it ?
I'll give it a try tomorrow
Thanks, Sergey
-Original
Hi
Please see http://cxf.apache.org/docs/http-transport.html
There's plenty of info there on how to configure HTTPS for server/client
Please see
http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/o
rg/apache/cxf/systest/jaxrs/security/jaxrs-https.xml
and
Thank you Sergey,
another option also worked perfectly. only difference between the 2 options
are :
with my approach(using HttpResponse), browser shows complete XML file (with
nodes also). where as by using Response object as you mentioned below, it
only shows content(values) of XML file I am
Makes sense.
Is there any documentation or example as to how to create a
ParameterHandlerAuthHeader and register as jaxrs provider? My
application is heavily dependent on Spring. I am fine to add spring
configuration OR annotation based.
I created a the following Provider
public class
Please Set application/xml on the Response.type(...), might help
-Original Message-
From: Parimal Dhinoja [mailto:pdhin...@gmail.com]
Sent: 18 November 2009 21:21
To: users@cxf.apache.org
Subject: Re: Exception : getWriter() has already been called for this
response
Thank you Sergey,
Sorry, I'm misleading you. It is @HeaderParam.
Also you can avoid creating ParameterHandler if AuthHeader class can
have a static valueOf(String) or a string based constructor.
Please review the CXF JAXRS docs
Thanks, Sergey
From: Sergey Beryozkin
Sent: 18 November 2009 22:35
To:
If you don't mind, could you tell which jar has this annotation? I
looked into my downloaded jars and I could not find it. My eclipse
always try to import org.codehaus.jra.HttpHeader annotation interface.
Regards
Karuna Pydipati
StubHub/eBay - Platform Services
Phone: (415)222-8752
Email:
The latest snapshot has fixed the problem with the header - thanks very much
:)
One question regarding the generated code for the following element
(declared in a schema referenced by my wsdl):
- xsd:element default=COLD name=temperature
- xsd:annotation
xsd:documentation
Hi !
Trying to find how to enable schema validation on the server side under the
code first scenario.
At some point I saw annotations that allow to limit bean field length etc.
can't find those for some reason,
anybody done that?
Thanks,
-Vitaly
--
View this message in context:
That's got to be a bug. I'll look into it.
On Wed, Nov 18, 2009 at 6:53 PM, noosy
vanessa.tow...@dsto.defence.gov.auwrote:
The latest snapshot has fixed the problem with the header - thanks very
much
:)
One question regarding the generated code for the following element
(declared in a
Hi Sergey,
I found some other sample XML on the web, and it appears to amount to this:
bean id=jaxbProvider
class=org.apache.cxf.jaxrs.provider.JAXBElementProvider
property name=marshallerProperties
map
entry key=jaxb.formatted.output
value
Thanks Dan.
I ended up adding it at the end of the PRE_PROTOCOL phase, which is where I
check what object is in the cause and following Amazon model update the
Fault error code with one of the pre-defined error codes.
If IllegalArgument etc. leak out I can deal with it there. or if I need to
I tried 3 options 1) Creating provider 2) static valudOf method 3)
Constructor of AuthHeader with String argument. At least..previous
error(s) gone away, but, my values are not being set. Even I added some
logging statements. Those were not printed. I am nullpointer exception
whenever I tried to
I am trying to use my WSDL2JS generated client code in an existing project
that uses the Ext JS library. I'm finding that it is no longer calling WS
operations successfully.
When I compare my WSDL2JS generated client code integrated with Ext, and
without Ext, I notice the following differences:
Problem we've faced with the catalog solution is the case where the
XSDs your WSDL is referencing also references other XSDs in a relative
way. It seems (to me) that you can't make a catalog entry which
overrides ../ to point to a specific place on the classpath.
For instance:
WSDL has
48 matches
Mail list logo
