dims,
Thanks for the bug fix - I downloaded, built the snapshot and tried
it against the remote WSDL in question.
The generation of the stub did not error out. Thanks for your help!
I hope to be able to return the favor soon. This list is a great
resource for everyone who uses it.
--
Hmm..actually this may be a bug. i'll check in a fix tonight. Please
try a nightly tomorrow.
-- dims
On 7/2/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Anne, Jeff,
The problem is the "https://"; the normal URL connection expects the
cert to be in the local jks store AFAICT.
thanks,
dims
Anne, Jeff,
The problem is the "https://"; the normal URL connection expects the
cert to be in the local jks store AFAICT.
thanks,
dims
On 7/2/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Jeff,
This URL:
https://uat-atc.regents.ohio.gov/ccx/OrgInfo/CoreMain_v1.0.0.xsd?wsdl
does indeed poi
Jeff,
This URL:
https://uat-atc.regents.ohio.gov/ccx/OrgInfo/CoreMain_v1.0.0.xsd?wsdl
does indeed point to the XSD in question. This problem looks to me to be
caused by WSDL2Java's inability to reference a remote XSD. Keith should do
as Haneef recommends and download the XSD and store it locally,
This line looks odd to me also:
Here is a definition of how import works in XML Schema:
http://www.w3.org/TR/xmlschema-0/ section 5.4. So, the ?wsdl at the end
of the schemaLocation string looks weird.
I did in fact download that wsdl file, and got the same error in Axis
1.3 as you did.
I do b
Thanks, Haneef, for the quick reply.
Unfortunately, I had to edit the wsdl and it failed under axis2 1.1.1
with a NullPointerException (even though it found the referenced schema)
I've switched to Axis2 1.2, but I haven't been able to get it to run
wsdl2java; just sends my poor little MacBo
You can download the wsdl from the schemalocation (
https://uat-atc.regents.ohio.gov/ccx/OrgInfo/CoreMain_v1.0.0.xsd?wsdl )
and put it in the same directory as that of original wsdl and run
wsdl2java.
Thanks,
Haneef
From: Keith Veleba [mailto:[EMAIL PROTECTED]
