In DataReaderImpl.java there is this hack in the
WSUIDValidationHandler.handleEvent that parses the event's message (see
below). It doesn't check for a null message. I have an envelope where I'm
sent a syntactically incorrect number that results in a
NumberFormatException with a null message.
It'
I'll try and take a closer look in the upcoming days, but a quick look in
the log you sent showed:
Creating Service ... from class ...
Basically, it's not using a WSDL for anything. Thus, none of the mime
extensors from the WSDL would be available. I haven't looked at the code or
a
I believe I correctly pointed my client at using the 2.5.3-SNAPSHOT (using the
snapshot maven repository) with no change to the outcome.
Would there be a reason to rerun wsdl2java from the 2.5.3-SNAPSHOT to rebuild
all of my classes? I kept the classes built from 2.5.2 wsdl2java.
-Kyle
-O
Christian put the sample client + servers I made up on GitHub:
https://github.com/ctoestreich/soapClient
He's the author of the Grails plugin (cxf-client) that I'm using.
The demo provides 4 very simple SOAP servers (1 MIME attachments, 1 non-MIME
attachments, 1 Holders but no attachments, 1 no
Hi Ben,
Sorry, I didn't look at the last response message from the server. I
also see the server not sending back the terminate sequence to the
client to close its sequence. Strangely, I was not seeing any
exception and assumed it was all okay. But there is something that
goes wrong during the ack
Can you create a sample that demonstrates this? Can you also test with the
latest 2.5.3-SNAPSHOT? Also, is there anything "interesting" in the logs?
The symptom is very similar to
https://issues.apache.org/jira/browse/CXF-4106 where attachments were
getting "lost" due to the SoapBodyInfo
This topic was previously: "CXF as Client - Response Attachment -
HolderInInterceptor IndexOutOfBoundsException"
But this subject better represents the true issue
SwAInInterceptor is failing to handle the attachment because SoapBodyInfo is
null.
The relevant code from SwAInInterceptor.java i
Hi Daniel,
I have upgraded to 2.3.4 and the issue seems to be fixed there since 2.3.3
has the same behavior than 2.2.12.
Thanks.
ivan.
On Wed, Mar 21, 2012 at 4:30 PM, ivan wrote:
> Hi Daniel,
>
> Thanks for your soon replay. We downgraded our cxf version to 2.2.16 to
> 2.2.2 and it worked pe
Hi
On 21/03/12 16:31, Jose Noheda wrote:
Hi,
I have a jaxws:client that proxies a web service. Unfortunately, I have two
environments to test against and each of them expects a different
targetNamespace. If I hardcode the namespace in the interface some tests
fail (with reason). Is there a way t
Hi Daniel,
Thanks for your soon replay. We downgraded our cxf version to 2.2.16 to
2.2.2 and it worked perfectly. I will continue investigating since we
cannot have this version installed. I will let you know if I have any news.
Thanks!
ivan
On Wed, Mar 21, 2012 at 12:20 PM, Daniel Kulp wrot
This is clearly a bug, it shouldn't be using the thread default
locale. I'm not sure where the bug will turn out to be; it could be
JAXB.
On Wed, Mar 21, 2012 at 10:42 AM, s t wrote:
>
>
>
>
>
>
>
>
>
> Hi,
> while generating a service from a wsdl, we are facing to problem of having
> turkish lo
Thx a lot!! You're my hero :D
On Wed, Mar 21, 2012 at 3:54 PM, Daniel Kulp wrote:
> On Wednesday, March 21, 2012 03:22:11 PM Jose Noheda wrote:
> > Hi,
> >
> > Thx, that was it. Unfortunately I can't use your preferred solution
> > because I'm porting a legacy JAX-RPC handler and I need to reuse
Greetings, I am fairly new to CXF but have run into an issue that I believe
requires some fairly advanced customization of interceptors.
I have a CXF consumer setup that I have schema validation turned on in.
When a client sends messages to the consumer if the message is not formatted
properly it
On Tuesday, March 20, 2012 09:20:34 AM merve wrote:
> Hi, I am using jdk1.6.0_24. Now I tried with jdk1.7.0_02 but gives the
> same error.
Any chance you can create a small testcase with step-by-step instructions
that reproduces this? This is just in the setup so hitting a local wsdl
file shou
On Tuesday, March 20, 2012 02:27:50 PM ivans wrote:
> Hi,
>
> We are facing a possible issue in our system with
> SoapOutEndingInterceptor. The log entry shows a delay of 20 seconds after
> SoapOutInterceptor$SoapOutEndingInterceptor entry.
>
> Our system is running in a Websphere 7 and and the c
On Tuesday, March 20, 2012 07:49:25 AM nitintiwari wrote:
> I'm using CXF to publish a Web Service, but our Security Team wants us to
> protect the WSDL over https access.
> So what are my options, so that Web Service remains functional but WSDL is
> hidden?
> This should also hide the CXFServlet d
On Wednesday, March 21, 2012 03:22:11 PM Jose Noheda wrote:
> Hi,
>
> Thx, that was it. Unfortunately I can't use your preferred solution
> because I'm porting a legacy JAX-RPC handler and I need to reuse an
> abstract class. The class in question generates a SOAPElement and then in
> JAX-RPC, it
Hi,
while generating a service from a wsdl, we are facing to problem of having
turkish locale.
The generator capitalizes the variable
class org.apache.ws.commons.schema.XmlSchemaForm.qualified
as
class org.apache.ws.commons.schema.XmlSchemaForm.QUALİFİED.
I am not sure how i can solve th
Hi Again.
Well, after two days of testing various versions (including 2.5.3-SNAPSHOT)
the results stay the same.
The client sends a final SequenceAck (for the offerSeq) to the server
after the initial conversation
has ended. The Server in turn sends a terminateSequence to w3c.org
It would be ver
On Tuesday, March 20, 2012 10:46:28 AM Hervé BARRAULT wrote:
> Hi,
> I would use a load balancer in front of my CXF deployment.
> As i am using cxf-transport-http-jetty, I know that this jetty module does
> not support all the features of Jetty.
> Does it support the Apache JServ Protocol ?
The sp
Hi,
Thx, that was it. Unfortunately I can't use your preferred solution because
I'm porting a legacy JAX-RPC handler and I need to reuse an abstract class.
The class in question generates a SOAPElement and then in JAX-RPC, it was
appended using
*header.addChildElement(soapElement);*
I'm replicat
On Tuesday, March 20, 2012 07:56:29 AM arknapik wrote:
> When I try to ask for wsdl of a service the invocation is captured by user
> defined interceptor chain.
>
> I use cxf-api-2.4.6. Is this not a bug?
No. A feature. In 2.4, the ?wsdl stuff was moved onto the interceptor
chain specifically
Is the client using Exception types generated from the wsdl or the original
Exception types from the server?If not from the wsdl, I would suggest
grabbing the wsdl, generating the faults in a kind of "one off", and
updating the server side exception to look like it. The constructors and
On Wednesday, March 21, 2012 02:21:59 AM chimaira wrote:
> Hi there,
>
> Actually when I apply an ascii encoding on message context with :
>
> Message msg = PhaseInterceptorChain.getCurrentMessage();
> message.put(Message.ENCODING, "ASCII");
>
>
> I got an encoding with lowercases : ex : [ 'e0
On Wednesday, March 21, 2012 02:09:56 PM Jose Noheda wrote:
> Hi,
>
> Looking at
> http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors it
> should be very simple to add a new header to a SOAP message.
> Unfortunately, my CXF message always return null when I ask for the
> SOAPMess
On Wednesday, March 21, 2012 02:58:21 PM Jason Pell wrote:
> Not quite, I was talking about the ?wsdl that is generated by cxf
There currently isn't a way to do it. All the code is there (the -
createxsdimports flag on the tools uses it) but no way to specify a property
or anything to trigger i
Hi Sergey,
Many thanks for your answer. I think I will use REST client to consume my
DOSGi exported on server side.
I find it's shame endpoint-descriptions xmlns="
http://www.osgi.org/xmlns/rsa/v1.0.0"; cannot be configured by a properties
file or another mean.
URL server depends on where OSGI bu
Hi Sergey,
Yes it works! I have declared like this :
---
---
H
Hi Sergey,
My big problem is the same than you : the time-(
My goal is to manage remoting in our Eclipse RCP/RAP application and I have
several solution like ECF, HttpInvoker, DOSGi...
I have already expermiented Spring HttpInvoker (serialize Java object with
binary mode), which works great but I
Hi Juerg
That's a good improvement as it reduces the amount of container specific code.
This would also allow to move the creation of the redirect URL to the
FederationProcessorImpl.
I do have on my todo list to support publishing the WS-Federation Metadata
document. This could be moved to fed
Hi there,
Actually when I apply an ascii encoding on message context with :
Message msg = PhaseInterceptorChain.getCurrentMessage();
message.put(Message.ENCODING, "ASCII");
I got an encoding with lowercases : ex : [ 'e0', 'e6' ]. I wish to get that
encoding in uppercase -> 'E0', 'E6' .
Is
Solution to the problem is to add something like this to authorizing
interceptor in PRE_STREAM phase:
WSDLGetInterceptor wsdlGetInterceptor = new WSDLGetInterceptor();
wsdlGetInterceptor.handleMessage(message);
if(message.getInterceptorChain().getState().equals(State.ABORTED)) {
return;
}
32 matches
Mail list logo
