I fixed my problem, they were two fold:
1. I hadn't yet imported the server's key into the client keystore
2. I didn't see the WS-Security headers in SOAPMonitor because the output
phase was at the begining instead of the end
Thanks
Marc
-- Forwarded message --
From: Marc
Could using jibx data binding option help in this scenario (Skipping some
class generations) ?
On Thu, Feb 26, 2009 at 4:39 PM, amit shah amits...@gmail.com wrote:
Re-replying to the mail in case I was not clear in explaining the problem.
I want to generate java classes from a published wsdl
Hi Amit,
Why do you want to skip generating the element? You could do this using
JiBX, but any XML documents you generated without this element would be
invalid (since the schema says it's a required element).
- Dennis
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
The reason I want to skip it is because, as the class gets generated each
web service call (method) takes an instance of this class as a parameter,
which I don't want.
Can this be done by using JiBX ? (i.e. skip the generation which I think
will automatically make the service calls not take an
The latest version of JiBX (1.2, currently in beta test and soon to be
production released) supports code generation from schema, and you'd
easily be able to eliminate this element in that code generation. But
WSDL2Java is separate, and to eliminate the parameter from the generated
web
The wsdl is a published one (by Microsoft SQL Reporting Services 2008) and
hence I cannot edit it.
On Sun, Mar 1, 2009 at 10:45 AM, Dennis Sosnoski d...@sosnoski.com wrote:
The latest version of JiBX (1.2, currently in beta test and soon to be
production released) supports code generation from
In my last mail I forgot to provide the full details of the s:element
which I want to skip
s:element name=*TrustedUserHeader* type=*tns:TrustedUserHeader*
/ *-*http://ind-sd-01/reportserver/ReportExecution2005.asmx#
s:complexType name=*TrustedUserHeader*
*-*
