Hi Everyone!
I write tow Endpoints in Server side. I want to bind this tow Endpoints to a
service URL.
But it prompt me " java.lang.RuntimeException: Soap 1.1 endpoint already
registered on address".
So I have found some post in this mail list. I find only post in 2008.
The post is
"http://cxf.5
Maybe it is becuase before chain.wait() return, the sync of chain will be
re-locked, so it will block untill chain.resume() finished;
- Original Message -
From: "xuhb"
To:
Sent: Friday, August 19, 2011 1:39 PM
Subject: Re: A mysteriously deadlock of CXF OnewayProcessorInterceptor
>
Sorry, I foget post the issue link:
https://issues.apache.org/jira/browse/CXF-3750
- Original Message -
From: "xuhb"
To:
Sent: Friday, August 19, 2011 1:34 PM
Subject: A mysteriously deadlock of CXF OnewayProcessorInterceptor
> Hi:
>Recently when I am checking/testing CXF , there
Hi:
Recently when I am checking/testing CXF , there is a mysteriously deadlock
of CXF Oneway Process; Normally CXF engine will invoke the one way bussiness
logical asynchronized ,, so the servlet handle will finished and return back to
servlet engine immediately;
But sometime, I notic
Thanks again.
This fixed it. I removed all references to the bouncycastle jar and after
deploying to WLS, the service worked. So you were right, I no longer needed
that jar.
Jay
--
View this message in context:
http://cxf.547215.n5.nabble.com/java-lang-NoClassDefFoundError-org-bouncycastle-as
This SHOULD be working.
Line 610 of ServiceImpl.java calls off to the configureObject with the right
name, so it should be configuring in the features and then copying them over
at line 621. Any chance you can debug through that code to see if anything
looks strange?
Dan
On Thursday, A
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:
However using both SOAP 1.1 and 1.2 Dispatch API clients, I found that it sets
the wrong Ac
I would check you meven dependencies for any old versions of Xerces or xml-
api's. It kind of looks like it's pulling in some older stuff someplace that
is conflicting.
Dan
On Thursday, August 18, 2011 4:07:25 PM David Karlsen wrote:
> With 2.4.2 and the maven plugin doing wsdl2java I get:
>
The best option is likely to set the publishedEndpointUrl property on the
endpoint to whatever URL you want. That is what will be published in the
WSDL.
Dan
On Thursday, August 18, 2011 5:19:38 PM Blue Diamond wrote:
> Any help on this is greatly appreciated. Thanks. :)
>
> On Wed, Aug 17,
On Thursday, August 18, 2011 2:05:45 PM jaybytez wrote:
> We are using CXF 2.2.12 (upgrading to 2.4.1) on WLS 11.
>
> The interesting thing is that we don't specifically gen the wsdl when a
> ?wsdl request comes in, CXF is fulfilling that.
>
> If we hit the WLS instance directly over http, then t
On Thursday, August 18, 2011 5:57:02 AM Evangelina wrote:
> Hi! Thanks for answering.
> I'm pretty new to CXF so please correct me if I'm wrong, but doesn't the
> 'mustUnderstand' attribute specifies if a header entry is mandatory or not?
> From what I saw in the code it just checks if the QName is
We are using CXF 2.2.12 (upgrading to 2.4.1) on WLS 11.
The interesting thing is that we don't specifically gen the wsdl when a
?wsdl request comes in, CXF is fulfilling that.
If we hit the WLS instance directly over http, then the WSDL soap:address is
set to the WLS instance with a protocol of h
This definitely sounds like a bug. Can you log an issue (and maybe attach a
patch?)
Thanks!
Dan
On Thursday, August 18, 2011 2:42:42 PM Timothy Paul Hanna wrote:
> I have a service that returns a list of objects using application/xml. The
> WADL doesn't display these object in the grammar n
I attempted to replace the WadlGenerator with one of my own by adding it as a
provider to my JAXRS server in spring. The server didn't see the new
WadlGenerator unless it extending the WadlGenerator that comes with CXF.
However extending the WadlGenerator in CXF is difficult because it declar
I have a service that returns a list of objects using application/xml. The
WADL doesn't display these object in the grammar nor connects them to the
operations response.
While debugging in CXF it seems the problem is in
ResourceUtils.getAllRequestResponseTypes The problem is the this method do
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
URL("file:/home/jpangburn/Desktop/IHE/XDSb.
I had webservices-api.jar in there, which was required for another probject.
It has jaxb2.2 inside it. Bummer, I wondered about that and discounted it.
Anyway, that fixed the build, so I verified with a clean cxf-2.4.1.jar that
both of these patches are working, at least with my test cases.
T
Dan thanks for the reply.
Adding that annotation seems to have done the trick.
I had this all working with MTOM and that is what i wanted to use but the
clients service bus doesn't support it currently.
Thanks,
James
--
View this message in context:
http://cxf.547215.n5.nabble.com/SwA-and-CX
Yes. You can disable this by setting the SecurityConstants tag
"ws-security.is-bsp-compliant" to "false".
Colm.
On Thu, Aug 18, 2011 at 4:06 PM, Penmatsa, Vinay wrote:
> It seems the BSPEnforcer rejects the signature security token reference
> without this token type attribute:
>
>
> if
It seems the BSPEnforcer rejects the signature security token reference without
this token type attribute:
if (assertion.getSaml2() != null &&
!WSConstants.WSS_SAML2_TOKEN_TYPE.equals(tokenType)) {
throw new WSSecurityException(
WSSecurityException.INVALID_SE
Hi,
Thank you very much. That seems to fix the issue with generating the signature.
But within the signature, the is missing the
"TokenType" attribute. How can I get this?
I think the expected attribute is
wsse11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0
With 2.4.2 and the maven plugin doing wsdl2java I get:
*15:57:55* message : Failed to execute goal
org.apache.cxf:cxf-codegen-plugin:2.4.2:wsdl2java (generate-sources)
on project pays-web-ws-pays: org/w3c/dom/ElementTraversal*15:57:55*
cause : org/w3c/dom/ElementTraversal*15:57:55* Stack trace :
On Thursday, August 18, 2011 1:43:09 PM Colm O hEigeartaigh wrote:
> Could you try it with CXF 2.4.1? I may have fixed a bug related to this.
>
Actually, try 2.4.2 if you can.If you are going to attempt an upgrade,
jump to the latest. :-)
Dan
> Colm.
>
> On Thu, Aug 18, 2011 at 1:31 PM
Do you have jaxb2.2 api jar endorsed in your JRE?Glen mentioned to me the
other day that he gets this error if the jaxb2.2 jar is endorsed. Haven't
had a chance to look at it at all.
Dan
On Wednesday, August 17, 2011 10:44:30 PM Jesse Pangburn wrote:
> Bugs are submitted. Patches are c
On Wednesday, August 17, 2011 10:00:18 PM jaybytez wrote:
> This got even more weird. My service war includes bcprov-jdk16-1.43.jar
> which has this class.
Now that's interesting. Hmm
You could TRY removing the bcprov jar entirely and it may work. MOST of the
Algorithms and such neede
Hi! Thanks for answering.
I'm pretty new to CXF so please correct me if I'm wrong, but doesn't the
'mustUnderstand' attribute specifies if a header entry is mandatory or not?
>From what I saw in the code it just checks if the QName is understood or
not, but I haven't seen that it checks the seman
Could you try it with CXF 2.4.1? I may have fixed a bug related to this.
Colm.
On Thu, Aug 18, 2011 at 1:31 PM, Penmatsa, Vinay wrote:
> CXF 2.4.0
>
>
> -Vinay
>
>
> -Original Message-
> From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
> Sent: Thursday, August 18, 2011 8:29 AM
> To
CXF 2.4.0
-Vinay
-Original Message-
From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
Sent: Thursday, August 18, 2011 8:29 AM
To: users@cxf.apache.org
Subject: Re: InitiatorSignatureToken
What version of CXF are you using?
Colm.
On Thu, Aug 18, 2011 at 12:53 PM, Penmatsa, Vinay
What version of CXF are you using?
Colm.
On Thu, Aug 18, 2011 at 12:53 PM, Penmatsa, Vinay
wrote:
> Hi Colm,
> Below is my cxf config client & policy def in the wsdl. The result is that
> STS token is included in the message is not signed by the client. Am I
> missing some policy assertion?
>
Hi Colm,
Below is my cxf config client & policy def in the wsdl. The result is that STS
token is included in the message is not signed by the client. Am I missing some
policy assertion?
I'm getting the error: " Caused by: org.apache.cxf.binding.soap.SoapFault: An
error was discovered processing
You can do the exact same things with either approach because, at the
end of the day, RAX-RS is built on top of the servlet API so it stands
to reason that you can do the same things in either. I can think of a
couple big distinctions between them off the top of my head.
1) JAX-RS is a stan
Any help on this is greatly appreciated. Thanks. :)
On Wed, Aug 17, 2011 at 8:30 PM, Blue Diamond wrote:
> Hi,
>
> I have a service binding provider based on my WSDL. Now, after I start the
> endpoint, I want to use the Endpoint and reset the service URLs in the WSDL.
> Is this possible in CXF 2
What does the full policy look like? That fragment looks ok to me.
What error are you getting? Also, what version of CXF are you using?
Colm.
On Wed, Aug 17, 2011 at 10:36 PM, Penmatsa, Vinay
wrote:
> Hi,
> I'm unable to define the correct policy for SAML_TOKEN_SIGNED. The following
> gets the
Hi,
You can add system property to the script which start Websphere like
-Djavax.xml.ws.spi.Provider=org.apache.cxf.jaxws22.spi.ProviderImpl
This can ensure pick up cxf as jaxws implementation.
Freeman
On 2011-8-18, at 下午6:37, Peter4Work wrote:
If so, how can to enforce Websphere to use CXF? I
If so, how can to enforce Websphere to use CXF? I have already tried to
disable IBMWSEngine by adding JVM argument mentioned in CXF deployment
section.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Aegis-binding-that-property-value-becomes-null-tp4695764p4711656.html
Sent from
Hi - that is not properly supported right now - will get it fixed
Cheers, Sergey
On Wed, Aug 17, 2011 at 1:02 AM, javanewbie wrote:
> Hi Guys,
>
> I am trying to use Enum as one of the query params. it is working fine but
> its not getting displayed in wadl?Is there anything special, i should do
Hi
On Wed, Aug 17, 2011 at 2:21 AM, Jason Chaffee wrote:
> I have a POJO/Java Bean QueryParam object that has a getter/setter for a
> field that is an Enum. While the Enum is working fine and the Enum is
> created correctly when we pass the value in the URI, the WADL does not show
> that part
Hi
On Thu, Aug 18, 2011 at 7:18 AM, Raj Floyd wrote:
> Hi
>
> REST style architecture, being based on HTTP specification, has common
> conventions like GET, POST typically also used by Servlets. Any idea why one
> would prefer RESTful Web service and not plain Servlet based framework. Its
> Web a
38 matches
Mail list logo
