u, ok, but could you elaborate on what the problem was that this
nightly build might fix?
On Tue, 2007-01-23 at 18:56 +0530, Amila Suriarachchi wrote:
sorry for the late reply. I had to wait until axis2 1.1 brach changes
were merged to axis2 trunk.
I fixed your problems in axis2_truck
Well, I see that when I used the Snapshot from the Jan 23, that yes, the
ADB binding completes, places the ExtensionMapper in the proper class
and all the source did finally compile.
The XmlBeans binding still throws an Exception though.
On Tue, 2007-01-23 at 11:39 -0500, R Bruce Hoffman wrote:
On 1/23/07, R Bruce Hoffman [EMAIL PROTECTED] wrote:
u, ok, but could you elaborate on what the problem was that this
nightly build might fix?
there were three things
1. there was a problem in URLProcessor. it did not correctly convert the
namespaces like urn:/fih/1_0 correctly.
2. there
On 1/23/07, R Bruce Hoffman [EMAIL PROTECTED] wrote:
Well, I see that when I used the Snapshot from the Jan 23, that yes, the
ADB binding completes, places the ExtensionMapper in the proper class
and all the source did finally compile.
The XmlBeans binding still throws an Exception though.
The XmlBeans binding still throws an Exception though.
ohh thanks for remining this. I will work on it.
It seems to be an xml beans problem. can you take an xmlbeans 2.2.0release and
try to compile your wsdl using the scomp command comes with the
xmlbeans release.
--
Amila Suriarachchi,
Anne,
Thank you very much for taking the time to produce such a detailed answer.
The details are a little depressing for someone with software that
relies on being able to dynamically consume web services. For various
reasons, we don't support all possible wsdl-described services at
present,
Sure... sorry.
Also, when using xmlbeans binding, I get the following error:
Using AXIS2_HOME: /usr/local/axis2
Using JAVA_HOME: /usr/lib/jvm/java-1.5.0-sun
Retrieving schema at '../../../../fih/1.0/fih-header.xsd', relative to
Bruce,
Giving the WSDL a quick look, I noticed that it is not valid. I don't
know if this is what's causing your problem, but it's a good place to
start.
In your WSDL types section, you attempt to import the same namespace
twice. This is not allowed. If the namespace is defined in multiple
First, let me sincerely thank you for your rapid response.
I had originally questioned the other developers on that repeated import
of the namespace and been told it was ok. I probably have to be more
forceful when my gut says it's wrong... but, as you can probably tell, I
am new to this WSDL
Bruce,
I took the WSDL file, commented out the imports, pasted the schemas
inline, and validated the WSDL. I found one error:
There is no schema component of the name [ds:Signature] defined
in the WSDL either via imported or embedded schema.
I don't understand why
Again, thank you so much for the effort and information.
What tool is it that you are using to validate this stuff? And, is it a
commercial product or open source tool?
On Wed, 2007-01-17 at 13:20 -0500, Anne Thomas Manes wrote:
Bruce,
I took the WSDL file, commented out the imports, pasted
Anne,
So if you want to dynamically consume web services based on the wsdl
alone, the WS-Policy constructs have to be embedded there and the
client machinery has to know how to process them to determine what
headers are required, if any? Is this the way it's supposed to work?
Is the
I use the Cape Clear SOA Editor tool. It's free, but not open source.
No support. I have permission to distribute it, so I can send it to
you if you like. It's a big file, though. (10MB)
Anne
On 1/17/07, R Bruce Hoffman [EMAIL PROTECTED] wrote:
Again, thank you so much for the effort and
The way it supposed to work is thus:
- A web service has various metadata files associated with it:
- WSDL defines the supported interfaces, MEPs, and bindings
- XSD defines the message formats
- WS-Policy defines its constraints and capabilities
(policies can be embedded in the
you call 10MB big? HA! I download System i software and Redhat
distributions... that's big. Send away... my email should be able to
handle anything less than a couple of GB...
On Wed, 2007-01-17 at 19:56 -0500, Anne Thomas Manes wrote:
I use the Cape Clear SOA Editor tool. It's free, but not
I just can't seem to get Axis2 1.1.1 wsdl2java.sh to properly create
skeleton code and Axiom or XmlBeans artifacts correctly for, what seems
to be, relatively simple wsdl and xsd's.
Below is the xsd and wsdl information. I have used FC4, FC5, Ubuntu and Debian
Sarge. I have tried 1.1, a snapshot
Can you attach your fih-header.xsd file?
On 1/16/07, R Bruce Hoffman [EMAIL PROTECTED] wrote:
I just can't seem to get Axis2 1.1.1 wsdl2java.sh to properly create
skeleton code and Axiom or XmlBeans artifacts correctly for, what seems
to be, relatively simple wsdl and xsd's.
Below is the xsd
17 matches
Mail list logo
