Hi,
I have a SOAP Provider service and am using XML Schema validation to
successfully filter all junk messages that don't match my WSDL except for one:
HTTP GET requests. If someone uses their Browser to test if my service is up,
I get a blank request into my service where I am expecting only
Hi,
I use the jax-ws Provider mechanism to implement a service provider:
@WebServiceProvider
@ServiceMode(value = Service.Mode.MESSAGE)
public class SOAPProvider implements ProviderStreamSource
If WS-Addressing is enabled and I receive a message with a ReplyTo address,
then the server will
Web Services Consulting http://www.sosnoski.com/consult.html
CXF and Web Services Security Training
http://www.sosnoski.com/training.html
Web Services Jump-Start http://www.sosnoski.com/jumpstart.html
On 11/21/2013 07:34 AM, Jesse Pangburn wrote:
Hi,
I use the jax-ws Provider mechanism
, but am definitely not well-versed enough in its usage
to understand all the pros and cons.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Wednesday, November 20, 2013 1:51 PM
To: users@cxf.apache.org; Jesse Pangburn
Subject: Re: long running
AM
To: users@cxf.apache.org
Subject: RE: CXF-4382 says that faultTo WSA header should work, but it doesn't
Hi,
Sounds as defect.
Could you create jira issue and attach test case to reproduce that?
Regards,
Andrei.
-Original Message-
From: Jesse Pangburn [mailto:jesse.pangb
Hi,
XML schema validation is failing in 2.7.7, which used to work in 2.7.6 and back
to 2.5.3 (at least). On my jaxws:endpoint I have schema validation enabled and
I see this in the log:
Oct 15, 2013 11:22:45 AM
org.apache.cxf.wstx_msv_validation.ResolvingGrammarReaderController error
SEVERE:
(same channel for
synchronous), instead of the faultTo address (despite it showing up in the
reply's To address).
Any ideas about this?
Thanks,
Jesse
-Original Message-
From: Jesse Pangburn [mailto:jesse.pangb...@infor.com]
Sent: Tuesday, July 23, 2013 4:42 PM
To: users@cxf.apache.org
(find.dispatch.operation, Boolean.TRUE);
thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, September 10, 2013 2:14 PM
To: users@cxf.apache.org; Jesse Pangburn
Subject: Re: how to determine/debug effective ws policy used?
On Sep 9, 2013, at 6:57 PM
Hi Dan,
I can submit a patch to make this change if necessary? Just hoping for some
feedback if this is a bad idea for some reason?
Thanks,
Jesse
-Original Message-
From: Jesse Pangburn
Sent: Friday, June 28, 2013 3:05 PM
To: users@cxf.apache.org; Daniel Kulp
Subject: RE: how
Hi Dan,
Just wonder if you've had a chance to see if this code should be changed as I
suggested, or if it is incorrect and will cause some other problem?
Thanks,
Jesse
-Original Message-
From: Jesse Pangburn [mailto:jesse.pangb...@infor.com]
Sent: Wednesday, June 05, 2013 3:36 PM
I use Dispatch and got attachments to work inbound/outbound for it. For
outbound, it's basically these steps (carving the relevant lines from my code,
leaving out the rest):
CollectionAttachment attachments = new LinkedListAttachment();
// do a loop here to create your attachments
is to turn on logging for the PolicyOutInterceptor
class at FINEST level.
Thanks,
Jesse
-Original Message-
From: Jesse Pangburn [mailto:jesse.pangb...@infor.com]
Sent: Tuesday, June 04, 2013 4:22 PM
To: users@cxf.apache.org
Subject: how to determine/debug effective ws policy used?
Hi,
I'm
Hi,
I'm trying to learn how to correctly use WS-Policy with CXF (using version
2.7.2) and would like to know if there's a way to log the effective policy
calculated for both consumer and provider?
The problem is that I have a wsdl with 3 policies attached to different points.
The first policy
Hi,
I'm trying to learn how to correctly use WS-Policy with CXF (using version
2.7.2) and would like to know if there's a way to log the effective policy
calculated for both consumer and provider?
The problem is that I have a wsdl with 3 policies attached to different points.
The first policy
Hi Dan,
Great, thanks for fixing this and for the comment about the default. I think
my own usage will not exceed 254.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, January 03, 2012 6:56 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
, January 03, 2012 2:21 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: CXF 2.5.1 problem with httpj:threadingParameters
On Thursday, December 29, 2011 1:47:16 PM Jesse Pangburn wrote:
Hi,
I have the following portion of a Spring configuration file that I was using
with CXF 2.4.2
Hi,
I have the following portion of a Spring configuration file that I was using
with CXF 2.4.2:
httpj:engine-factory
httpj:engine port=9003
httpj:threadingParameters minThreads=6
maxThreads=16 /
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, November 15, 2011 1:10 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: partial response problem with SOAP 1.1 use of WS-Addressing and
SOAPAction
On Thursday, November 10, 2011 4:39:22 PM Jesse Pangburn
Hi,
I invoked a SOAP 1.1 web service using CXF 2.4.2 DispatchImpl and that service
immediately returned the following soap header:
soap:Header
wsa:MessageIDuuid:A12B3727-0B3D-11E1-983D-DFB5348FF699/wsa:MessageID
wsa:Actionresponse/wsa:Action
.
Do you want me to create an issue in Jira or you already are taking care of
that?
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Friday, September 09, 2011 2:13 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: jaxws Provider doesn't allow
This is now tracked as issue: https://issues.apache.org/jira/browse/CXF-3802
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Monday, September 12, 2011 12:11 PM
To: Jesse Pangburn
Cc: users@cxf.apache.org
Subject: Re: jaxws Provider doesn't allow
Similar to the recent problem with jaxws Provider, the jaxws Dispatch doesn't
allow override of outbound ws addressing headers either. I tried setting with
the following code:
AddressingProperties wsaClient = new AddressingPropertiesImpl();
// snipped out properties setting
// attach these
Hi,
I have a jaxws Provider configured to do WS-Addressing and the defaults seem to
work fine. However, if I try to override some of the WS-Addressing headers in
the MessageContext, it gets ignored. I've tried the following :
AddressingProperties wsaServer = new AddressingPropertiesImpl();
if it's a bug to have to jump through all
these hoops to set that on the outbound message. Shouldn't it inherit from the
MessageContext or something? The outbound message seems to get the inbound
addressing properties assigned just fine.
Thanks,
Jesse
-Original Message-
From: Jesse
in the dispatcher's request context.
Regards, aki
2011/8/22 Jesse Pangburn jesse.pangb...@us.lawson.com:
I don't think that will work because the WSAddressingFeature doesn't have
that method signature, it has:
protected void initializeProvider(InterceptorProvider provider, Bus bus) {
Client
too. So I think it's good
but just think it could use another pair of eyes.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, August 23, 2011 10:59 AM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: Can Dispatch API be used
, August 23, 2011 11:05 AM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: setting wsa:addressing feature in cxf:bus causes wrong action
header to be sent when using Dispatch API
On Monday, August 22, 2011 3:59:39 PM Jesse Pangburn wrote:
I don't think that will work because
2:24 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: Can Dispatch API be used with jaxws:client Spring configuration?
On Friday, August 19, 2011 3:34:53 PM Jesse Pangburn wrote:
It seems that the ServiceImpl code is copying over stuff from the following
items (all this stuff is near
is enabled.
I will create the patch this way unless anyone objects?
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Friday, August 19, 2011 2:29 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: setting wsa:addressing feature in cxf:bus causes wrong
.
At least it's closer.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Thursday, August 18, 2011 7:51 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: Can Dispatch API be used with jaxws:client Spring configuration?
This SHOULD be working
2011/8/19 Jesse Pangburn jesse.pangb...@us.lawson.com:
Hi,
Another Dispatch API / wsAddressing question. I configured ws addressing on
the cxf bus like this, instead of adding the feature directly to the dispatch
client:
cxf:bus
cxf:features
wsa:addressing
it. I'll
also patch the DispatchImpl to respect the ws-addressing feature if set in the
jaxws:client bean.
Thanks,
Jesse
-Original Message-
From: Jesse Pangburn [mailto:jesse.pangb...@us.lawson.com]
Sent: Friday, August 19, 2011 12:54 PM
To: Daniel Kulp; users@cxf.apache.org
Subject
.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Thursday, August 18, 2011 6:15 AM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: dispatch api with ws-addressing
Do you have jaxb2.2 api jar endorsed in your JRE?Glen mentioned to me the
other
I'm trying to use the Spring jaxws:client configuration to put as much of the
setup for my Dispatch API client into Spring as possible, but it seems to be
ignoring it.
The following is the code I'm using to setup the dispatch client:
URL wsdlURL = new
Hi,
Another Dispatch API / wsAddressing question. I configured ws addressing on
the cxf bus like this, instead of adding the feature directly to the dispatch
client:
cxf:bus
cxf:features
wsa:addressing/
/cxf:features
/cxf:bus
However using both SOAP 1.1 and 1.2
(BindingProvider.SOAPACTION_URI_PROPERTY,
urn:ihe:iti:2007:RegistryStoredQuery) ;
Regards, aki
2011/8/17 Jesse Pangburn jesse.pangb...@us.lawson.com:
Hi,
I'm trying to use the dispatch API and while I can make the service call ok,
the ws-address action header is wrong. Here's my code:
URL wsdlURL = new
URL
to, but assume I
misunderstood or am doing something else wrong. Or maybe this only works in
soap 1.1 wsdls or something?
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Wednesday, August 17, 2011 10:29 AM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject
-Original Message-
From: Jesse Pangburn
Sent: Wednesday, August 17, 2011 11:17 AM
To: 'Daniel Kulp'; users@cxf.apache.org
Subject: RE: dispatch api with ws-addressing
Hi Dan,
Thanks for the suggestion, I'm trying to figure out one of those cases. I
changed the code to this to try a DOMSource
, otherwise I think it's fine the
way it is- if somewhat inconvenient.
Thanks,
Jesse
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Wednesday, August 17, 2011 2:28 PM
To: users@cxf.apache.org
Cc: Jesse Pangburn
Subject: Re: dispatch api with ws-addressing
They both look
Hi,
I'm trying to use the dispatch API and while I can make the service call ok,
the ws-address action header is wrong. Here's my code:
URL wsdlURL = new
URL(file:/home/jpangburn/Desktop/IHE/XDSb.Support.Materials.v9/wsdl/XDS.b_DocumentRegistry.wsdl);
Service service =
is that your
configuration does not wrap httpj:engine with httpj:engine-factory,
although I'm unsure if that's required.
Glen
On 07/26/2011 06:02 PM, Jesse Pangburn wrote:
Hi,
Any advice on the httj:engine using SSL problem below?
Thank you,
Jesse
-Original Message-
From: Jesse
is that your configuration
does not wrap httpj:engine with httpj:engine-factory, although I'm unsure if
that's required.
Glen
On 07/26/2011 06:02 PM, Jesse Pangburn wrote:
Hi,
Any advice on the httj:engine using SSL problem below?
Thank you,
Jesse
-Original Message-
From: Jesse
Hi,
Any advice on the httj:engine using SSL problem below?
Thank you,
Jesse
-Original Message-
From: Jesse Pangburn [mailto:jesse.pangb...@us.lawson.com]
Sent: Wednesday, July 20, 2011 5:55 PM
To: users@cxf.apache.org
Subject: SSL engine starting problem
Hi,
I'm new to CXF so please
Hi,
I'm new to CXF so please forgive these noob questions. I'm running CXF
embedded in a Spring app and have a couple problems. The following is the
content of my spring config xml:
beans xmlns=http://www.springframework.org/schema/beans;
44 matches
Mail list logo
