thank you for your help.
I did this in my development environment and it worked. (I was able to
connect to web service)
I also put the certificate in my production server and it is said that
certificate added successfully to key store.
When I run the code I am still getting the error:
You may enable SSL tracing on your deployment container by setting
'-Djavax.net.debug=SSL,handshake,trustmanager' jvm option ... see
http://docs.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html
This should enable you to find out
which truststore is used and why the
You may enable SSL tracing on your deployment container by setting
'-Djavax.net.debug=SSL,handshake,trustmanager' jvm option ... see
http://docs.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html
This should enable you to find out
which truststore is used and why the
Hi Oliver,
Thanks for your feedback.
I do agree that the 1st approach would mean less effort and more
maintainability because the effort is done only over one implementation.
For better understanding of the answer, please let me write mine in
between you lines:
Hi
I have been trying to create a XML file from a Java Web service and create a
SOAP message with Attachment using SAAJ to send it to another Web service.
My Web service code is given below.
DocumentBuilderFactory documentBuilderFactory =
DocumentBuilderFactory.newInstance();
To reproduce I just created a class with a main that uses the
JaxWsProxyFactoryBean in it for the client. Then in Eclipse (3.7 at least)
right click on the project - Export - Runnable Jar - Select your Launch
Config (your Main class) - Select the Package required libraries into
generated JAR
Hi Fran
Regarding this, Do you mean that the IDP1 should also be able to process the
token coming from the external IDP (not only redirecting the client to the
external IDP) so this token can be transformed according to what the
application expects to have as claims information? That should
Does anyone have any clue about this.
why on some computers this would be a problem and on some not.
--
View this message in context:
http://cxf.547215.n5.nabble.com/consuming-web-service-runtime-modeler-error-Wrapper-class-not-found-tp5154080p5154983.html
Sent from the cxf-user mailing list
http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.2/samples/greeter/
By the way, I'm redirecting to the users list
Sergey
On 18/01/12 14:53, Jesus wrote:
Sorry Sergey,
what demo do you said?
Actual version of D-OSGi is 1.2
On Wed, Jan 18, 2012 at 3:23 PM, Sergey Beryozkin-5
The issue is this:
I receive a signed soap message with the X509 certificate in the header (in
the BinarySecurityToken element). I have added this certificate to my
keystore and try to validate the signature. However the message won't be
validated, I keep receiving:
Good day,
I've run into a situation where we are using CXF, but the client at this
point wants to have a multiple STS setup as follows:
STS A: Takes a username and login, returns a SAML 1.1 token (TOKEN_A) with
a basic set of claims (username, role, given name)
STS B: Takes TOKEN_A, and
On Wednesday, January 18, 2012 6:31:45 AM uib wrote:
Does anyone have any clue about this.
why on some computers this would be a problem and on some not.
Yea. It's not picking up CXF. It's using the JAX-WS implementation found in
the JDK which requires all the wrapper classes to be
I am trying to consume a SOAP webservice with CXF served by .NET WCF. I used
wsimport to create the Java client objects.
We have a custom http tunnel that routes based on info in an extra http header
field. When trying to use the tunnel I was getting errors from WCF (so I know
the header is
Hi Dan
I do have a very similar scenario. Just to double check,
- there are two security domains/realms in this use case
- does a person has got an identity in both security domains which means that
when the STS issues TOKEN_B it must first map the identity (see STS
IdentityMapper) and the
I'm testing a fix for this now. Basically, when jaxb generates the schemas,
it more or less creates 'temporary' schemaLocations in the schemas. (like
schema1.xsd, schema2.xsd, etc...)Since we inline everything in the wsdl,
we strip them out. However, we're stripping out all the
Here's an update:
* Using a separate client app I confirmed that Op2 on its own will work
with the custom header. Problems come up when it's after another call on the
same proxy object.
* Creating a new proxy object between calls fixes the problem. CXF
seems to be caching
I have a web service which supports both SOAP and RESTful calls which works
great except for one small issue with JSON serialization on List results.
I have two methods, one that returns a single entity and one that returns a
List of entities.
@GET
@Path(/parcel/{id})
Hi Oli,
Thanks for your response. The item you specified with your JIRA issue
CXF-3520 is pretty much the exact scenario we will require for future
service implementations.
Is there a way to do the work described in CXF-3520 manually and
(relatively) easily using the STSClient class, or is it
Hi Dan
If you do it manually, you will loose the token caching functionality. Maybe as
a starting point have a look to the following class:
Hi Oliver,
Sorry I thought I'd answered.
We are talking initially about the identity mapping, and in a later
application the claims transformation scenario. In terms of the time frame,
if I can get a workaround in place, then somewhere in the vicinity of 1 - 2
months I believe. Otherwise
Mike, can you submit a JIRA with a very simple test client WSP that
quickly reproduces the problem? One way of doing this is to download my
minimal DoubleIt Web Service Client
(http://www.jroller.com/gmazza/entry/web_service_tutorial) which quickly
runs OOTB on Tomcat and make whatever
Hi
On 18/01/12 19:07, Chris Geer wrote:
I have a web service which supports both SOAP and RESTful calls which works
great except for one small issue with JSON serialization on List results.
I have two methods, one that returns a single entity and one that returns a
List of entities.
@GET
Thanks Sergey.
On Wed, Jan 18, 2012 at 4:31 PM, Sergey Beryozkin sberyoz...@gmail.comwrote:
Hi
On 18/01/12 19:07, Chris Geer wrote:
I have a web service which supports both SOAP and RESTful calls which
works
great except for one small issue with JSON serialization on List results.
I
I am having a similar problem with minOccurs=0 being generated in my WSDL no
matter what I put in the @XmlElement annotation.
I am using java2ws maven plugin v 2.5.1 to generate the WSDL and regardless
of if I put @XmlElement(required=true) or @XmlElement(required=true,
nillable=false) or just
OK...just discovered that the minOccurs=0 vs 1 does get generated correctly,
but only for classes in the same maven project as my java2ws plugin.
Annotated classes that are dependencies do not seem to be correctly
detected. Is there a limitation to multi-project maven builds when using the
java2ws
Hello,
We have a jaxws:endpoint defined like this:
jaxws:endpoint xmlns:tns=http://my.org/examples/;
id=greeter_Https
implementor=demo.service.Greeter_HttpsImpl
serviceName=tns:Greeter_HttpsService
26 matches
Mail list logo
