[jira] Commented: (AXIS2-2929) Java2WSDL does not correctly create enumerations from Enum

2009-06-19 Thread Dennis Sosnoski (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722098#action_12722098 ] Dennis Sosnoski commented on AXIS2-2929: You might want to give Jibx2Wsdl a try as

RE: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Tom Jordahl
Eventually Axsi2 will be almost as good as Axis is. :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) Tom Jordahl Axis 1 implementer -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: Friday, June 19, 2009 7:42 AM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Make RPCUti

[jira] Commented: (AXIS2-2929) Java2WSDL does not correctly create enumerations from Enum

2009-06-19 Thread John Peregrine (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721907#action_12721907 ] John Peregrine commented on AXIS2-2929: --- Has there seriously been no progress on this

Axis2/Axiom/Woden OSGi bundle issues, was: Re: Treat axis2 bundles as plain jars

2009-06-19 Thread Raymond Feng
Hi, The following is a list of issues we ran into. Some of the issues might have been resolved by Axis2 1.5. I have tried to bring some of them to the attentions of Axis2 community but it doesn't seem to be very responsive in the OSGi area :-(. With Axis2 1.4.1, we have experienced quite a f

RE: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Pétur Runólfsson
Actually, mapping handlers for individual types/QName doesn't catch all possible use cases. For example, custom handling of xsi:type would have to be applied before the QName/type can be determined. The same goes for custom error handling or logging that should be applied across all nodes in the

[jira] Issue Comment Edited: (AXIS2 -3837) Exception extracting jars in to temporary directory : java.io.Fi leNotFoundException: C:\Program File s\jboss-4.2.2.GA\server\serveraxis\ .\tmp\deploy\tmp181

2009-06-19 Thread Giovanni Sarbia (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721793#action_12721793 ] Giovanni Sarbia edited comment on AXIS2-3837 at 6/19/09 7:15 AM:

[jira] Commented: (AXIS2-3837) Ex ception extracting jars into tempo rary directory : java.io.FileNotFo undException: C:\Program Files\jbo ss-4.2.2.GA\server\serveraxis\.\tm p\deploy\tmp18123axis2-exp

2009-06-19 Thread Giovanni Sarbia (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721793#action_12721793 ] Giovanni Sarbia commented on AXIS2-3837: The same error is still also in Axis2 1.5

Re: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Deepal Jayasinghe
No no, I understand what you mean. And I think that is something we can easily do. So in services,xml he can map QName to Serialization/DeSerialization classes then we can easily call them. I like the idea, let's go for it. Deepal On Fri, Jun 19, 2009 at 9:22 AM, Davanum Srinivas wrote: > MR you

Re: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Davanum Srinivas
MR you take over everything. With Axis1's TypeMappingRegistry you have a default registry for QName/Java classes and a user can override only the things they want to. Basically the users want to keep most of the functionality in RPCMessageReceiver as-is but would like to modify just bits and

Re: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Deepal Jayasinghe
What the difference of writing a MR and a serializer/deserializer ?, I do not see a big difference. Deepal On Fri, Jun 19, 2009 at 7:41 AM, Davanum Srinivas wrote: > Guess it's time to port the pluggable serializer/deserializer mechanism from > Axis1 :) > > -- dims > > On 06/19/2009 06:33 AM, And

Re: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Davanum Srinivas
Guess it's time to port the pluggable serializer/deserializer mechanism from Axis1 :) -- dims On 06/19/2009 06:33 AM, Andreas Veithen wrote: So, to summarize: You are happy with most of the JavaBeans<-> XML mapping rules, but you want to customize some of them (e.g. java.util.Date/java.util.C

RE: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Pétur Runólfsson
Hi Andreas, Yes, that is correct. Regards, Pétur Runólfsson Betware From: Andreas Veithen [andreas.veit...@gmail.com] Sent: Friday, June 19, 2009 10:33 To: axis-dev@ws.apache.org Subject: Re: [Axis2] Make RPCUtil more flexible So, to summarize: You are h

Re: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Andreas Veithen
So, to summarize: You are happy with most of the JavaBeans <-> XML mapping rules, but you want to customize some of them (e.g. java.util.Date/java.util.Calendar <-> xsd:date/xsd:dateTime mapping or the way arrays are mapped), without modifying Axis2 code (or creating a fork of it). Is that correct?

RE: [Axis2] Make RPCUtil more flexible

2009-06-19 Thread Pétur Runólfsson
Hi Sanjiva, > I guess your point is that RPCMessageReceiver does everything you want except > do the JavaBeans <-> XML mapping the way you want? Exactly. > In that case, can you not subclass the message receiver and redirect some > code? That's what I would like to do, but it's currently not

[jira] Updated: (AXIS2-4373) If a service becomes faulty due to a Module, faulty list is not updated correctly.

2009-06-19 Thread Sameera Jayasoma (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sameera Jayasoma updated AXIS2-4373: Attachment: patch-axis2-trunk-19-06-2009-01.txt Yeah, there was a problem. I have re-create