Dims,
I owe you an apology. I jumped to the wrong conclusion when I read this
message the first time. Last night while mulling over the problem I realised
that the dates did not jive and when I checked this again this morning I
found out that you are absolutely right here. The changes to
no problem. No apologies needed :)
-- dims
On Fri, 28 Jan 2005 11:11:15 +, Joel Rosi-Schwartz
[EMAIL PROTECTED] wrote:
Dims,
I owe you an apology. I jumped to the wrong conclusion when I read this
message the first time. Last night while mulling over the problem I realised
that the
Anne,
In case it was a general problem I have reattached the WSDL file here.
I am not certain if your reply reflects an official response from the Axis
team or if you are simply a user being helpful. If this is a team response
then I am somewhat at a loss of where to go from here. One of the
Joel,
Please open a bug report in Axis...http://issues.apache.org/jira/
thanks,
dims
On Thu, 27 Jan 2005 14:40:43 +, Joel Rosi-Schwartz
[EMAIL PROTECTED] wrote:
Anne,
In case it was a general problem I have reattached the WSDL file here.
I am not certain if your reply reflects an
Dimms,
Done, the url is http://issues.apache.org/jira/browse/AXIS-1788
Thanks,
Joel
On Thursday 27 January 2005 14:46, Davanum Srinivas wrote:
Joel,
Please open a bug report in Axis...http://issues.apache.org/jira/
thanks,
dims
On Thu, 27 Jan 2005 14:40:43 +, Joel Rosi-Schwartz
See JBoss's CVS:
http://cvs.sourceforge.net/viewcvs.py/jboss/jaxrpc/src/main/org/apache/axis/utils/Mapping.java?r1=1.1r2=1.2
They created the problem in their forked version of Axis...So you need
to ask them to fix it. For comparison see Axis's version:
Dims,
I know. This change was done in response to my initial posting to the JBoss
JBossWS forum http://www.jboss.org/index.html?module=bbop=viewtopict=58149
If you read that thread you will understand my predicament. Thomas Diesler
the Web Service lead felt that the problem is being caused
Joel,
XML-wise the follow envelope
SOAP-ENV:Envelope
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
SOAP-ENV:Body
Joel,
Is it possible at at all for you to deploy Axis1.2RC2 inside JBoss and
use that aas your soap engine? Or have u ruled out that possibility?
We have no control over how JBoss chooses to change already existing
and working code :(
Let me know...and i am still looking at fixing Axis cvs for
On Thursday 27 January 2005 21:10, Davanum Srinivas wrote:
Joel,
XML-wise the follow envelope
SOAP-ENV:Envelope
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Dims,
I am not at all sure. It appears that JBoss has modified Axis to integrate it.
There is also a jboss-ws4ee.jar which seems to provide part of the web
services functionality. Does this depend on the modifications? I am not a all
certain how straightforward it would be to simply replace
- Original Message -
From: Joel Rosi-Schwartz [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 27, 2005 5:01p
Subject: Re: Problem using Axis RC2 against JBoss 4.0.1
Dims,
I am not at all sure. It appears that JBoss has modified Axis to integrate
- Original Message -
From: Joel Rosi-Schwartz [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 27, 2005 5:01p
Subject: Re: Problem using Axis RC2 against JBoss 4.0.1
Dims,
I am not at all sure. It appears that JBoss has modified Axis to
integrate
For some reason I can't open the attached WSDL file, but there's
nothing wrong with specifying xmlns= in an unqualified element. In
fact, assuming that the in0 is an unqualified element, it's
required.
So I don't think this is a bug in Axis. If JBoss is rejecting the
xmlns= attribute, then it's a
Thanks Dims. I just tried last nights cvs and I get the same results. I will
log a Jira issuse as you recommend.
Cheers,
Joel
On Monday 24 January 2005 21:17, Davanum Srinivas wrote:
Joel,
1) Try latest CVS version/nightly build of axis.
2) Log a bug in JIRA
thanks,
dims
On Mon, 24 Jan
Apologies for reposting this, but this is really show stopper for me and I
could truly use some advice on this. Even a response to the extent that this
must certainly be something that I have screwed up would be appreciated, as
right now I simply have no idea if this is my problem, an axis
Joel,
1) Try latest CVS version/nightly build of axis.
2) Log a bug in JIRA
thanks,
dims
On Mon, 24 Jan 2005 18:38:15 +, Joel Rosi-Schwartz
[EMAIL PROTECTED] wrote:
Apologies for reposting this, but this is really show stopper for me and I
could truly use some advice on this. Even a
Hi,
I have a set of web services that I have been developing using Apache Axis 1.2
RC2 on the Java client and JBoss 4 on the server. They have been functioning
fine under JBoss 4.0.0, but I am having trouble migrating them to Jboss
4.0.1. When I make a call to any of the web services I get a
18 matches
Mail list logo
