this is fixed already.
thanks,
Amila.
[1]
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/adb/src/org/apache/axis2/databinding/typemapping/SimpleTypeMapper.java?r1=783787r2=835823
2009/12/14 Dinçer Karaduman dincer.karadu...@hititcs.com
Hi All,
I think there is a bug in
. I am kinda hate to mess up the
templates. :-)
I have attached a simple service that can be used to re-create this bug.
Thank you!
Saminda
==
org.apache.axis2.AxisFault:
org.apache.axiom.om.util.OMXMLStreamReaderValidator cannot be cast
));
to generated code to work. Is this bug already fixed in truck ?. If not
I'll open a JIRA and attahced a patch. I am kinda hate to mess up the
templates. :-)
I have attached a simple service that can be used to re-create this bug.
Thank you!
Saminda
to mess up the
templates. :-)
I have attached a simple service that can be used to re-create this bug.
Thank you!
Saminda
==
org.apache.axis2.AxisFault:
org.apache.axiom.om.util.OMXMLStreamReaderValidator cannot be cast to
org.apache.axiom.om.impl.llom.OMStAXWrapper
The address of the bug tracker is:
http://issues.apache.org/jira
Regards,
Andreas
On Tue, Jul 21, 2009 at 16:37, Meindert
Oldenburgermeindert.oldenbur...@pallas-athena.com wrote:
Hello,
It is possible that i found a serious bug, it cost me days to find out that
it is not our application,
Hi Dimuthu Gamage,
I have filed a JIRA AXIS2C-1343 for this issue. Please do
needful to fix this issue as this is a blocking to use axis2/c 1.5.0.
Thanksyou're your support.
Thanks
-Srini
-Original Message-
From: Frank Zhou [mailto:fcho...@yahoo.com]
Sent: Friday, February 06,
This seems to be an issue that is related to how XML messages are processed
in Axis2. I have simplified my example and have noticed that XPath
expressions function differently depending on how the XML fragment was
constructed. I cannot get an XPath expression to work in an Axis2 service,
but I
Can we have a volunteer to be the RM for 1.3.1 please?
Thanks,
Samisa...
Dinesh Premalal wrote:
On Wed, Apr 2, 2008 at 2:09 PM, Samisa Abeysinghe [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Samisa Abeysinghe wrote:
I happen to find that the libs created with 1.3.0 has
Samisa Abeysinghe wrote:
I happen to find that the libs created with 1.3.0 has the extension
so.0.2.0.
This should be 0.3.0 I suppose.
This calls for a patch release?
Samisa...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Wed, Apr 2, 2008 at 2:09 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Samisa Abeysinghe wrote:
I happen to find that the libs created with 1.3.0 has the extension
so.0.2.0.
This should be 0.3.0 I suppose.
This calls for a patch release?
+1
thanks,
Dinesh
--
you.
Thanks,
-jaliya
- Original Message -
From: [EMAIL PROTECTED]
To: Jaliya Ekanayake [EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 9:11 AM
Subject: Re:[Axis2] Axis2-Plugin-Bug?
Hi Jaliya,
for a better understanding of what I did I send you some screenshots of
these steps
PROTECTED]
Hope someone in the dev list will help you.
Thanks,
-jaliya
- Original Message -
From: [EMAIL PROTECTED]
To: Jaliya Ekanayake [EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 9:11 AM
Subject: Re:[Axis2] Axis2-Plugin-Bug?
Hi Jaliya,
for a better understanding of what I did I
YG,
Please log a bug in JIRA. Someone will need to take a very close look
at the code again.
thanks,
dims
On 5/26/07, YG Park [EMAIL PROTECTED] wrote:
Hi,
I'm new to Axis2 and while I was using Axis2 1.2, I encountered a strange
behavior.
The module I was working on was working just
We don't use Bugzilla any more.
Please use JIRA: http://ws.apache.org/axis/bugs.html
--
Tom Jordahl
Adobe ColdFusion Team
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, April 20, 2007 1:51 PM
To: axis-dev@ws.apache.org
Subject: DO NOT REPLY [Bug
Please summarize the problem for us.
On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote:
Hello,
first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6.
We've found an issue wih the namespaces in the SOAP message returned by
Axis.
In order to follow this issue from the begining
marzo de 2007 15:29
Para: axis-dev@ws.apache.org
Asunto: Re: Possible Axis 1.4 Bug
Please summarize the problem for us.
On 3/7/07, Ibai Perez Arbulu [EMAIL PROTECTED] wrote:
Hello,
first of all, I'm using Axis 1.4 with Tomcat 5.5 and JDK 1.6.
We've found an issue wih
forom Kiran ( the one posted in 2007-03-02) read client
as partner!
Thank you!
--
*De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
*Enviado el:* miércoles, 07 de marzo de 2007 15:29
*Para:* axis-dev@ws.apache.org
*Asunto:* Re: Possible Axis 1.4 Bug
Please summarize
( the one posted in 2007-03-02) read client
as partner!
Thank you!
--
*De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
*Enviado el:* miércoles, 07 de marzo de 2007 15:29
*Para:* axis-dev@ws.apache.org
*Asunto:* Re: Possible Axis 1.4 Bug
Please summarize the problem
Object (Sumador) from which Axis generates the Web service.
Am I right?
De: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Enviado el: miércoles, 07 de marzo de 2007 15:49
Para: axis-dev@ws.apache.org
Asunto: Re: Possible Axis 1.4 Bug
btw -- after you did
PROTECTED]
*Enviado el:* miércoles, 07 de marzo de 2007 15:49
*Para:* axis-dev@ws.apache.org
*Asunto:* Re: Possible Axis 1.4 Bug
btw -- after you did this:
As you can see in the project I send some days before, I took this
WSDL and removed the Schema to paste it in the Operacion.xsd file
under
Hi DO;
Which Axis2 version are you using , as I remember correct we fixed this
issue before 1.0 release. If you have this problem in Axis2 1.0 please
create a JIRA.
DO wrote:
Hello,
I am trying to test a service with the header. I auto generated stubs
and every time I invoke the service it
oops, never mind...must be working too hard. I read the code wrong. No
bug.
Nadir K. Amra
Nadir Amra/Rochester/[EMAIL PROTECTED] wrote on 05/22/2006 08:18:34 PM:
I am looking at how fault handling is done, and I see that we generate
code like the following (using FaultMappingDoc test
You must use xsd:include to bring in a schema with the same
namespace and xsd:import to bring in a schema with a different
namespace. So you must change this:
xsd:schema targetNamespace=
http://www.opengis.net/ows
xsd:import namespace=http://www.opengis.net/ows
Sent: Wednesday, December 14, 2005 4:36
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You must use xsd:include to bring in a schema
with the same namespace and xsd:import to bring in a schema
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 4:36
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You must use xsd:include
Here is that files.
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 5:18
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type
PROTECTED] wrote:
Here is that files.
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 5:18
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create
Sent:
Wednesday, December 14, 2005 5:18 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:27
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You have a bunch of namespace errors in these files. Fix
them and try again.I
problem there. Or do you knew some source
where where is my problem solved?
Please help
Ales
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:54
PM
Subject: Re: Is it a bug? Multi-nested
includes
Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:54
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
Sorry, I'm not going to do your homework
ll
find a solution. Thank you again for your time, because you help me a
lot.
Ales
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 9:35
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.gene
, 2005 5:11 PMTo: axis-user@ws.apache.orgCc:
axis-dev@ws.apache.orgSubject: RE: Is this a
bug??
sounds like on your client you are instantiating a java
object but not populating the "required" attribute named "id", sending the
object to axis, and axis is rejecting the me
I've opened a new bug on this, and provided a way to test.
Could someone please verify the validity of this bug?
http://issues.apache.org/jira/browse/AXIS-2050
Dan
Tom Jordahl wrote:
Dan,
This is a document/literal service? Are you using wrapped mode?
I don't like the look of the
Dan,
This is a document/literal service? Are you using wrapped mode?
I don't like the look of the repeated element. What is the WSDL
description of getSupportedCodeSystemsResponse? Since there is no type
info in the response, I am not sure how .NET (or Axis for that matter,
but it probably
Hmm, I'm still puzzled myself.. I'm trying to compare the RC2 WSDL and
over the wire messages with what I'm seeing now... and I can't find a
difference immediately. Yet it worked then.. and now .NET only gets
arrays of size 1 for any of my custom object arrays.
I'll do some more
Ok, I'm completely baffeled.
The only difference in the SOAP messages generated by 1.2 RC2 compared
to todays daily build of 1.2.1 is that 1.2.1 has some extra spaces after
the closes on xml tags. I can't believe that would affect things.
I attached the messages.
Maybe it has to do with
Here is a capture by tcpmon of the .NET request and response of the
1.2.1 server:
POST /axis/services/VocabRuntimeService HTTP/1.1
VsDebuggerCausalityData:
Whoa. This looks like a status message from 2002! Something burped in the
bugzilla bug base.
:-)
Tom Jordahl
Macromedia Server Development
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 06, 2005 12:05 AM
To: axis-dev@ws.apache.org
On 7/14/03 05:32 PM Shellman, Joel [EMAIL PROTECTED] wrote:
Can't you create a timezone from the offset?
I see. You would have to arbitrarily choose the ID, right? You could keep
the offset but because there are multiple timezones with the same offset, is
that the problem?
To some extend I
To: '[EMAIL PROTECTED]'
Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n bug
Okay. I think for me then... Does Axis support a date instead of a datetime?
Thanks,
-joel
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 14, 2003 9:03
To: '[EMAIL PROTECTED]'
Subject: RE: DO NOT REPLY [Bug 21394] - Possible datetime deserializatio n
bug
You can certainly send an XML element for which you define your own
serializer for that would give you any behavior you neeed.
--
Tom Jordahl
Macromedia Server Development
-Original Message
Tom Jordahl wrote:
You can certainly send an XML element for which you define your own serializer for that would give you any behavior you neeed.
BTW, I send time_t in UTC as a long, as it is the only format that is
guaranteed to be understood by things other than axis; .net is a bit
patch
Glen,
Need help with this one...
-- dims
--- [EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED
You got it, dims. I'm planning to devote some Axis-time this weekend.
--Glen
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2003 10:40 AM
To: [EMAIL PROTECTED]
Subject: ATTN: Glen (Re: DO NOT REPLY [Bug 20654] - Java2WSDL
gen
OK folks - should I hold off re-kitting 1.1 until this is resolved?
--Glen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 9:04 AM
To: [EMAIL PROTECTED]
Subject: DO NOT REPLY [Bug 15133] - Problems serializing
german umlauts
No (IMHO). Please go ahead.
Thanks,
dims
--- Glen Daniels [EMAIL PROTECTED] wrote:
OK folks - should I hold off re-kitting 1.1 until this is resolved?
--Glen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 9:04 AM
To:
]'
Subject: RE: DO NOT REPLY [Bug 15133] - Problems serializing german
umlauts
OK folks - should I hold off re-kitting 1.1 until this is resolved?
--Glen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 9:04 AM
To: [EMAIL PROTECTED
13, 2003 9:15 AM
To: '[EMAIL PROTECTED]'
Subject: RE: DO NOT REPLY [Bug 15133] - Problems serializing german
umlauts
OK folks - should I hold off re-kitting 1.1 until this is resolved?
--Glen
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent
Please refer to
http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/SoapMonitor for more
info on the SOAPMonitorApplet.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 10:37 AM
To: [EMAIL PROTECTED]
Subject: DO NOT REPLY
Daniels
Cc: [EMAIL PROTECTED]
Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY
[Bug 19682] - non-AxisFault exceptions don't have details serialized))
Glen,
Uploaded a patch to bugzilla. Can you please try it out? the
zip file contains the use case on how this should work as well
it in.
--Glen
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 10:09 AM
To: Glen Daniels
Cc: [EMAIL PROTECTED]
Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY
[Bug 19682] - non-AxisFault exceptions don't have details
-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 10:09 AM
To: Glen Daniels
Cc: [EMAIL PROTECTED]
Subject: RE: ATTN: GLEN (Re: ATTN: TOMJ (Re: DO NOT REPLY
[Bug 19682] - non-AxisFault exceptions don't have details serialized))
Glen
, Michael E.
Subject: Re: DO NOT REPLY [Bug 18530] - org.xml.sax.SAXException: No
deserializer defined for array type AcnInfoRow
Try starting with
1. A brand new tomcat 4.1.8.
2. Run Java2WSDL on the wsdl to generate both server and client
3. Don't use any other code other than the generated
Try starting with
1. A brand new tomcat 4.1.8.
2. Run Java2WSDL on the wsdl to generate both server and client
3. Don't use any other code other than the generated server and client.
Let us know. THIS is definitely a problem with your environment.
Thanks,
dims
--- [EMAIL PROTECTED] wrote:
DO
James,
See http://marc.theaimsgroup.com/?l=axis-devm=104800578623575w=2
-- dims
--- James M Snell [EMAIL PROTECTED] wrote:
Working on a fix. Running all tests now.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(877) 511-5082 (voice/fax) ** NEW NUMBER **
Ok, I hadn't looked at the patch in detail. Given the tone of the
discussion, it sounded as if the patch was going to allow this type of
silliness to occur. Exceptions are good. Sorry for not paying closer
attention. I retract my -1
- James Snell
IBM Emerging Technologies
[EMAIL
OK, I'm glad you caught it!
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 6:52 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: DO NOT REPLY [Bug 16522] - Allow Axis HTTP 1.1 clients to u
se Keep-Alive
Eric,
Forcing
Eric,
I could *really* use this feature so if you need help getting it working let
me know and I'll be glad to help code and/or test.
alan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 1:59 PM
To: [EMAIL PROTECTED]
Subject: DO NOT
unsubscribe
- Original Message -
From: James M Snell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, February 18, 2003 18:18
Subject: Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only
HashMaps, throwing ClassCastException when assigning
I recommend that we do
-1.2 changes are needed in Seattle,
then release RC2, and final a week later.
Thoughts?
--Glen
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 12:29 PM
To: [EMAIL PROTECTED]
Subject: Re: DO NOT REPLY [Bug 16844] - MapDeserializer
- Original Message -
From: Glen Daniels [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 09:37
Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only
HashMaps, throwing ClassCastException when assigning
Yup, I agree with this too. I'm not going
+1 to getting soapbuilder's fixes in.
-- dims
--- Steve Loughran [EMAIL PROTECTED] wrote:
- Original Message -
From: Glen Daniels [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 09:37
Subject: RE: DO NOT REPLY [Bug 16844] - MapDeserializer creates only
I believe, and the spec concurs, that the isFoo pattern is optional:
http://java.sun.com/products/javabeans/docs/beans.101.pdf
8.3.2 Boolean properties
In addition, for boolean properties, we allow a getter method to match the
pattern:
public boolean is PropertyName();
This isPropertyName
Not yet. The folks responsible for the WSDL have not yet come up with the final
version.
Thanks,
dims
--- [EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
respond to axis-dev
To
[EMAIL PROTECTED]
cc
bcc
Subject
Re: DO NOT REPLY [Bug 16844] - MapDeserializer creates only HashMaps,
throwing ClassCastException when assigning
- Original Message -
From: Glen Daniels [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 17
Can you really say FIXED then? More like LATER, no?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 8:24 PM
To: [EMAIL PROTECTED]
Subject: DO NOT REPLY [Bug 11306] - Use of Runnable in Call object
violates J2EE rules in J2EE
James writes:
In the meantime, if others can start working through the bug
list also, it would be very helpful :-)
+1! Post-release donuts are on me if we can get a good percentage of these bugs
+resolved. :)
--Glen
69 matches
Mail list logo
