Hi All,
I'm new to cxf and I manged to run the java_first_jaxws and
java_first_pojo in samples folder bundled in cxf distribution. When I
go through code I find that cxf-servlet.xml file is there. I would
like to know the purpose of this file and I have noted, for these
examples(java_first_jaxws
Hi Arambage,
cxf-servlet.xml is a spring config to start the cxf endpoint as a
servlet in a container. I just checked the java_first_jaxws demo.
I could simply remove the cxf-servlet.xml and the demo still works. So I
guess it is a leftover from when the example also had a mode to run it
in
Anyone have any ideas?
--
View this message in context:
http://cxf.547215.n5.nabble.com/The-signature-or-decryption-was-invalid-tp4845894p4848221.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
I got a question regarding the WSDL generated by CXF:
Using a Java-first approach I want to use the generated WSDL (availabe under
.../services/...?wsdl) to give third-party systems an description of my web
service methods. But the WSDL looks very poor, because the Method/Operation
It's impossible to tell from so little information. Could you supply a
test-case?
Colm.
On Wed, Sep 28, 2011 at 8:32 AM, yannick yannick.land...@gmail.com wrote:
Anyone have any ideas?
--
View this message in context:
You can set the following jax-ws property
ws-security.username-token.always.encrypted to false. See the
ALWAYS_ENCRYPT_UT variable here:
http://svn.apache.org/viewvc/cxf/trunk/rt/ws/security/src/main/java/org/apache/cxf/ws/security/SecurityConstants.java?view=markup
Why would you want to send an
Hi,
I can't see the operations parameters are missing, what you pasted
here is only the binding part.
I believe you can find all your parameters from http://x.x.x.x/xyz/
services/RepurchaseResellNoReturnRequester?
wsdl=RepurchaseResellNoReturnRequester.wsdl where should have schema
and
Just one comment for the maxIdleTime. Jetty use this parameter to check
the underlayer stream's states,
the timeout timer will be reset when there is any read or write
operation on the stream.
On Wed Sep 28 13:39:03 2011, Freeman Fang wrote:
Hi,
I've encounter similar exception lately(with
cxf-servlet.xml will be loaded by CXFServlet for publishing the endpoints.
On Wed Sep 28 15:30:46 2011, Christian Schneider wrote:
Hi Arambage,
cxf-servlet.xml is a spring config to start the cxf endpoint as a
servlet in a container. I just checked the java_first_jaxws demo.
I could simply
Hello Freeman,
here´s the complete WSDL:
?xml version='1.0' encoding='UTF-8'?wsdl:definitions
name=RepurchaseResellNoReturnRequester
targetNamespace=http://www.springframework.org/schema/beans;
xmlns:ns1=http://repurchaseresellnoreturn.xyz.de/;
Yes, but the java_first_jaxws example does not seem to use a servlet or
am I wrong there?
Christian
Am 28.09.2011 11:40, schrieb Willem Jiang:
cxf-servlet.xml will be loaded by CXFServlet for publishing the
endpoints.
On Wed Sep 28 15:30:46 2011, Christian Schneider wrote:
Hi Arambage,
No, it's not the complete wsdl, there must be wsdl:types and
wsdl:messages and wsdl:portType in
wsdl:import location=http://x.x.x.x/xyz/services/
RepurchaseResellNoReturnRequester?
wsdl=RepurchaseResellNoReturnRequester.wsdl namespace=http://repurchaseresellnoreturn.xyz.de/
You can find
explained here (and in other guides on the CXF Resources page):
http://www.jroller.com/gmazza/entry/web_service_tutorial
On 09/28/2011 03:10 AM, Nuwan Arambage wrote:
Hi All,
I'm new to cxf and I manged to run the java_first_jaxws and
java_first_pojo in samples folder bundled in cxf
Dear Srinivas,
Did you find an answer to this problem? I faced a similar bean
initialization issue. The problem is that I am not able to figure out the
source of the problem as my bean depends on initialization of reference
beans. Or, is it a problem with Websphere 6.1? Our app works with
Hi Freeman,
thank you very much!!!
After using http://x.x.x.x/xyz/services/RepurchaseResellNoReturnRequester?
wsdl=RepurchaseResellNoReturnRequester.wsdl instead of
http://x.x.x.x/xyz/services/
RepurchaseResellNoReturnRequester?wsdl I got the complete WSDL.
I thought the ?wsdl after the
I updated CXFNonSpringJaxrsServlet to support the injection of simple
properties for service and Application classes, providers and
interceptors, few people have asked about it, Carl-Eric, others, so it
makes sense to add some simple support, ex:
init
param-namejaxrs.interceptors/param-name
Maye also interresting the stacktrace:
org.apache.ws.security.WSSecurityException: The signature or decryption was
invalid
at
org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:373)
at
Hi Indranil,
Yes it is problem with Websphere 6, you may need to install featurepack for
your websphere to support JAX-WS webservices.
Thanks
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Service-deployment-on-Websphere-6-1-0-29-tp4462184p4849035.html
Sent from the
No :
You can use CXF 2.4 with websphere 6 without feature pack. But you need to
set the classload to Parent_Last and add some dependencies with cxf 2.4.2
dependency
groupIdjavax.xml.ws/groupId
artifactIdjaxws-api/artifactId
version2.2.5/version
We noticed that cxf has problems with the referencing in the request in
linux... We took out ts-16 reference and then it complained on the next
one...
Any ideas?
--
View this message in context:
http://cxf.547215.n5.nabble.com/The-signature-or-decryption-was-invalid-tp4845894p4849193.html
Sent
On Wednesday, September 28, 2011 12:08:23 PM Christian Schneider wrote:
Yes, but the java_first_jaxws example does not seem to use a servlet or
am I wrong there?
I think most of the are remnants from the now-removed Ant build.xml files.
Several of those did have war targets along with the
I just put in CXF-3831 for that, at least for the intro level java-first
and wsdl-first examples. I found it redundant to repeat it for every
CXF example, because it clutters the pom.xmls with new profiles and
library (jetty) exemptions, which distracts the reader from the specific
Could you paste the SOAP request?
Colm.
On Wed, Sep 28, 2011 at 2:44 PM, yannick yannick.land...@gmail.com wrote:
We noticed that cxf has problems with the referencing in the request in
linux... We took out ts-16 reference and then it complained on the next
one...
Any ideas?
--
View this
soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
soap:Header
Action xmlns=http://www.w3.org/2005/08/addressing;
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
It has to do with the namespaces.
The @WebService annotation on the impl class likely either doesn't have a
targetNamespace attribute (in which case it will derive from the package name
for the impl) or it's different than the targetNamespace for the SEI
interface.Thus, the WSDL
Hi Colm,
Thanks for the info. Yes, it wouldn't make sense to send it unencrypted, but I
was wondering why when I use SignedSupportingTokens, the message is
automatically encrypted too instead of only signed.
Regards,
Vinay
-Original Message-
From: Colm O hEigeartaigh
Hi
This is an old problem, but I can't seem to find a solution posted
anywhere. I want to marshall a comma-separated list of integers
directly into an Integer [].
1. Service:
public Response getCounters(
@QueryParam(msisdn) Long msisdn,
@QueryParam(counters) Integer
On Wednesday, September 28, 2011 10:41:10 AM Penmatsa, Vinay wrote:
Hi Colm,
Thanks for the info. Yes, it wouldn't make sense to send it unencrypted, but
I was wondering why when I use SignedSupportingTokens, the message is
automatically encrypted too instead of only signed.
Compatibility
Hi
ListInteger must be supported, I'll add a test for Integer[], have you
tried int[] ?
Cheers, Sergey
On 28/09/11 15:42, Kiren Pillay wrote:
Hi
This is an old problem, but I can't seem to find a solution posted
anywhere. I want to marshall a comma-separated list of integers
directly into
All:
I have a question I can't seem to get a ready answer to. I see some
potentially useful attributes on the jaxws:endpoint element, but I'm not
sure how to use them.
I have a report-writing service implemented on a Tomcat server in
Windows using the CXF Spring configuration. While doing this,
Hi,
I have both code first and wsdl first scenarios in which I have to support
WS-Security with various security tokens. To make it easier for CXF clients, I
need to provide policy definitions in wsdl in all scenarios.
I find from CXF documentation - Note: at this point, WS-SecurityPolicy
Hi,
Maybe the approach to my problem is driving me to a wrong path. We are in
the process of changing all integration components from EJB2 to Rest. In the
server side when a component exception is thrown I look at the accept header
that was sent by the client to see if the client is a regular
Hi Sergey!
Tried int[], got the same error.
detail[I cannot be cast to [Ljava.lang.Object;
org.apache.cxf.jaxrs.utils.InjectionUtils.addToCollectionValues(InjectionUtils.java:752)
org.apache.cxf.jaxrs.utils.InjectionUtils.injectIntoCollectionOrArray(InjectionUtils.java:740)
I also tried
Another typo! It should be pc.setPassword(password); not
pc.getPassword(password);
--
View this message in context:
http://cxf.547215.n5.nabble.com/UsernameTokenHandler-required-or-Help-with-WSS4J-CallbackHandler-tp4831197p4849910.html
Sent from the cxf-user mailing list archive at Nabble.com.
On Wednesday, September 28, 2011 12:24:18 PM Penmatsa, Vinay wrote:
Hi,
I have both code first and wsdl first scenarios in which I have to
support WS-Security with various security tokens. To make it easier for CXF
clients, I need to provide policy definitions in wsdl in all scenarios. I
find
Hello Sergey,
I think I have found the problem, considering the following code:
http://svn.apache.org/repos/asf/cxf/dosgi/trunk/dsw/cxf-dsw/src/main/java/org/apache/cxf/dosgi/dsw/handlers/ServiceInvocationHandler.java
Around line 56-57, where it checks whether the arrived exception is
assignable
Thanks for the tip, it brought some hope, but it just didnt worked.
The sad thing is that polimorphism doesnt work this way via CXF-DOSGI (as it
does in simple CXF).
2011/9/27 Daniel Kulp dk...@apache.org
On Tuesday, September 27, 2011 2:45:08 PM András Liter wrote:
Hey,
I bumped into the
Hello, Not sure if this is directly related to CXF but maybe someone can
provide some direction.
I am trying to do an update to an object based on the XML file being passed
as the payload. I am able to retrieve the object from the database but when
I goto save the object I get the following
Can you provide more info please, where do abstract classes come into
the picture ?
Sergey
On 28/09/11 19:12, András Liter wrote:
Thanks for the tip, it brought some hope, but it just didnt worked.
The sad thing is that polimorphism doesnt work this way via CXF-DOSGI (as it
does in simple
Hello Sergey,
Here is the situation simplified:
Let's say I have the following Java types as entities/business objects:
- abstract Shape
- Triangle extends Shape
- Rectangle extends Shape
And let's say I have the following interface implementation to expose via
DOSGI-CXF
public
Please share your ideas. Thanks.
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Client-issue-with-upgrade-from-CXF-2-2-7-to-2-4-2-tp4845738p4851812.html
Sent from the cxf-user mailing list archive at Nabble.com.
41 matches
Mail list logo
