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
After many test i find why sending a soap message with 2 attachments with an
Axis client only one is received. As you can see in this Wireshark log the
response is send before the message is completely received. With Wireshark
packet viewer is easy to notice that client send the message, but
Forgot to say:
service just display attachments id and echo the request back.
Thx for any help to solve this.
Bye!
--
View this message in context:
http://www.nabble.com/-CXF--Bug--SOAPwAttachment-bad-received.-tp15017531p15017690.html
Sent from the cxf-user mailing list archive at
Sorry fior bringing this one again, but I am having the same issues with
Cxf-2.0.3 with java2wsdl approach.
Is there any official workaround for this before XmlSchema team releases
binary?
Also I cant find the java2ws tool
(http://cwiki.apache.org/CXF20DOC/java-to-ws.html), is it only usable
This seems more blocking issue than we initally thought. We use Java first
approach, and Cxf-2.0.3.
For example when we use ListMyType etc we get that error, when we use
ListJavaPrimitiveType everything goes ok.
We would really appreciate any news/info regarding this: when it will be
fixed (put
On Tue, 2008-01-22 at 06:14 -0800, silithus wrote:
This seems more blocking issue than we initally thought. We use Java first
approach, and Cxf-2.0.3.
For example when we use ListMyType etc we get that error, when we use
ListJavaPrimitiveType everything goes ok.
We would really
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
Hi
Online documentation is ok but I think that many would buy
book if it has more details than documentation and explain
how to solve some real world problems...
Regards,
Amir
-Original Message-
From: Adrian Trenaman [mailto:[EMAIL PROTECTED]
Sent: 22. januar 2008 15:45
To:
Yep, Cxf has JIRA for this one, and its only one with blocker status.
https://issues.apache.org/jira/browse/CXF-1388.
as oposed to Axis2 16 'Blocker' issues.
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=10611priority=1resolution=-1.
Its shame to have this one and only
Hi Priya,
On your #1 - its unfortunate that we throw a NullPointerException, but
the actual issue is outlined in the log:
SEVERE: No operation found for path: /, contentType: */*, Accept contentType:
*/*
i.e. your sending a request to a path that doesn't have an operation
associated with it.
I hadn't heard any more on this..I know it seems like a minor thing,
just wondering if this will be fixed for the 2.0.4 release.
-Original Message-
From: Vespa, Anthony J
Sent: Tuesday, January 15, 2008 2:52 PM
To: cxf-user@incubator.apache.org
Subject: RE: Snapshot JAR file
Thanks for
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
This performance hit is likely due to the fact that the WSS4J
interceptors require DOM structures for processing through the WSS4J
interfaces. So you are paying for DOM-ifying your entire message.
If you are using WS-Security to simply propagate security tokens
(E.g., UsernameTokens),
It does seem to work now in my IDE. Thanks. =)
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2008 11:32 AM
To: cxf-user@incubator.apache.org
Cc: Vespa, Anthony J
Subject: Re: Snapshot JAR file
On Tuesday 22 January 2008, Vespa, Anthony J
On Tuesday 22 January 2008, Vespa, Anthony J wrote:
I hadn't heard any more on this..I know it seems like a minor thing,
just wondering if this will be fixed for the 2.0.4 release.
You tell me :-) The release candidates are at:
http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator/
Hmm... I was hoping for an easy answer to this and, unfortunately, I
don't have one. :-(
I don't know Groovy, but if you can do something like:
MapString, Object context = new HashMapString, Object();
MapString, Object reqContext = new HashMapString, Object();
Hi Dan,
I looked hard could not find out how to set ENDPOINT_ADDRESS on the
client. The generated service class has nothing to this effect. Do you
have an example for this ?
Thanx
-yogen
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, January 21, 2008 4:16
This is part of the JAX-WS spec:
Greeter port = service.getSoapPort();
BindingProvider provider = (BindingProvider)port;
provider.getRequestContext().put(
BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
address);
Dan
On Tuesday 22
Thanks for your reply!
Actually I'm using ServiceMix 3.2.1, and also using the CXF component with
ServiceMix (not the one with CXF2.0.2).
I just wondering that this maybe a bug in CXF component, if someone can
confirm that.
Regards,
gnodet wrote:
Could you please try with the servicemix
Hi,
I met some similar troubles with JBoss 4.2.2, CXF2.0.2 and JDK 1.5.0_14.
When I deploy the JCA J2ee connector on JBoss, I found the following error
messages on JBoss console:
ERROR [STDERR] Jan 22, 2008 3:27:29 PM
org.apache.cxf.jca.cxf.ManagedConnectionFactoryImpl init
ERROR [STDERR]
Christian,
As Fred mentioned, doing the SAAJ stuff is definitely expensive,
especially if the body of the message is large. With SAAJ, the entire
message pretty much gets sucked into memory consuming memory, causeing
extra garbage collections, etc... The Sun RI SAAJ impl isn't exactly
On Monday 21 January 2008, Frederick N. Brier wrote:
The WSDL2Java CXF generated web service is not sending a SOAP header.
Perhaps it is because it is an implicit header? I tried the -exsh,
but that did not cause the header to be generated. The doc seems to
indicate that it causes the header
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.
Hi
org.apache.cxf.jaxrs.provider.JSONProvider checks XMLRootElement
annotations.
Would it make a difference if you annotate both wsResponse and wsMessage
classes with this annotation ?
Cheers, Sergey
-Original Message-
From: Vespa, Anthony J [mailto:[EMAIL PROTECTED]
Sent: 22 January
I did try that, and I get the same error.
-Original Message-
From: Beryozkin, Sergey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2008 5:14 PM
To: cxf-user@incubator.apache.org
Subject: RE: JSON and JAX-RS
Hi
org.apache.cxf.jaxrs.provider.JSONProvider checks XMLRootElement
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
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
Hi,
Did you do any setting up the transportIds for the local transport in
CXF bus?
You need to override the CXF bus default loading transport factory to
local transport.
Here are an example of setting the bus with code in the jaxws front end
test module[1],
and a spring configuration file
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
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
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
Hi,
I have a large set of existing WSDL describing ~200 business
interfaces, and a set of classes that bind SOAP to the underlying
services and vice-versa.
I'm trying to publish these services through CXF, and so far have had
mixed results
My approach has been to subclass the CXFServlet, and on
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,
33 matches
Mail list logo
