[jira] Commented: (AXIS2-653) Handler method "cleanup" is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=comments#action_12437469 ] Davanum Srinivas commented on AXIS2-653: Bill, Quick browse did not show me where .cleanup for handlers is invoked. can u please add that as well? thanks,

[jira] Assigned: (AXIS2-1221) ADB Code generation for XMIME (http://www.w3.org/TR/xml-media-types/) is incorrect

[ http://issues.apache.org/jira/browse/AXIS2-1221?page=all ] Davanum Srinivas reassigned AXIS2-1221: --- Assignee: Davanum Srinivas (was: Thilina Gunarathne) > ADB Code generation for XMIME (http://www.w3.org/TR/xml-media-types/) is > incorrect > --

[jira] Assigned: (AXIS2-969) Missing xsi:type in SOAP-Message

[ http://issues.apache.org/jira/browse/AXIS2-969?page=all ] Eran Chinthaka reassigned AXIS2-969: Assignee: Sanka Samaranayake > Missing xsi:type in SOAP-Message > > > Key: AXIS2-969 > U

[jira] Commented: (AXIS-2564) Unable to compile classes generated by java org.apache.axis.wsdl.WSDL2Java

[ http://issues.apache.org/jira/browse/AXIS-2564?page=comments#action_12437465 ] Venkatesh Audinarayanan commented on AXIS-2564: --- Since the interface name (BeanService) is same as the package name (BeanService), I am getting the e

[jira] Updated: (AXIS2-1222) WSDL2Java throws a StackOverflowError

[ http://issues.apache.org/jira/browse/AXIS2-1222?page=all ] Davanum Srinivas updated AXIS2-1222: Priority: Blocker (was: Critical) > WSDL2Java throws a StackOverflowError > - > > Key: AXIS2-1222 >

[jira] Assigned: (AXIS2-1219) Custom Fault Exception

[ http://issues.apache.org/jira/browse/AXIS2-1219?page=all ] Davanum Srinivas reassigned AXIS2-1219: --- Assignee: Eran Chinthaka > Custom Fault Exception > -- > > Key: AXIS2-1219 > URL: http://issue

[jira] Assigned: (AXIS2-1220) AxisServlet.initContextRoot assumes 1 level deep context

[ http://issues.apache.org/jira/browse/AXIS2-1220?page=all ] Davanum Srinivas reassigned AXIS2-1220: --- Assignee: Eran Chinthaka > AxisServlet.initContextRoot assumes 1 level deep context > > >

[jira] Assigned: (AXIS2-1224) setOperationContext() not thread-safe

[ http://issues.apache.org/jira/browse/AXIS2-1224?page=all ] Davanum Srinivas reassigned AXIS2-1224: --- Assignee: Deepal Jayasinghe > setOperationContext() not thread-safe > - > > Key: AXIS2-1224 >

[jira] Assigned: (AXIS2-1228) startUp() ignores exceptions

[ http://issues.apache.org/jira/browse/AXIS2-1228?page=all ] Davanum Srinivas reassigned AXIS2-1228: --- Assignee: Deepal Jayasinghe > startUp() ignores exceptions > > > Key: AXIS2-1228 > UR

A newbie question, Can't build Axis2 using Maven

hi, I follow the instruction on http://ws.apache.org/axis2/svn.html, try to build axis2 using maven, I check-out latest version of axis2 using svn, and run mvn, and it fails and complains that can't download one resource. I just paste the log following, could anybody tell me what happened and how

[jira] Updated: (AXIS2-1138) Generated client code does not handle attribute namespaces correclty.

[ http://issues.apache.org/jira/browse/AXIS2-1138?page=all ] Davanum Srinivas updated AXIS2-1138: Description: I am using the WSDL listed below. I generated a client. This client is pointing to a non-java service. The service fails because it can

[jira] Updated: (AXIS2-653) Handler method "cleanup" is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=all ] Bill Nagy updated AXIS2-653: Attachment: qoslifecyclepatch.txt Here's a patch that implements the QoS/handler lifecycle. (This still doesn't fix the module lifecycle issue [i.e. the cleanup() meth

Re: Axis2 is ignoring my WSDL (from axis-user)

Sanjiva Weerawarana wrote: On Sat, 2006-09-23 at 03:26 +1200, Dennis Sosnoski wrote: D.Kreft wrote: It seems *really* counter-intutive to have to supply a configuration setting to use a file that one intentionally puts in his .aar so that Axis can use it. It was my understanding after r

Re: Axis2 is ignoring my WSDL (from axis-user)

On Sat, 2006-09-23 at 03:26 +1200, Dennis Sosnoski wrote: > D.Kreft wrote: > > It seems *really* counter-intutive to have to supply a configuration > > setting to use a file that one intentionally puts in his .aar so that > > Axis can use it. It was my understanding after reading the > > documentat

Re: [Axis2] Status of JaxWS module (was:Re: Axis2 release progress (Axis2 1.1))

I agree with Jeff, JAX-WS is not ready yet for a release.  Even in an experimental state, it would be much to fragile and painful for people trying to use it. As he said, this could certainly be on the list for the next release though.   Regards, Nicholas Gallardo WebSphere  -  WebServices Deve

Re: [axis2] latest svn - NoClassDefFoundError: javax/jms/BytesMessage

I see a catch for NoClassDefFoundError in Line 400 of AxisConfigBuilder.java. Any idea why it is not getting caught? Or are you running with debug on for the logger? thanks, -- dims On 9/24/06, robert lazarski <[EMAIL PROTECTED]> wrote: Seeing this again on the latest svn: java.lang.NoClassDe

Re: [axis2] latest svn - NoClassDefFoundError: javax/jms/BytesMessage

Seeing this again on the latest svn: java.lang.NoClassDefFoundError: javax/jms/BytesMessage at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328) at java.lang.Class.getConstructor0(Class.java:2640)

[jira] Created: (AXIS2-1228) startUp() ignores exceptions

startUp() ignores exceptions Key: AXIS2-1228 URL: http://issues.apache.org/jira/browse/AXIS2-1228 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core Affects Versions: 1.1 Env

[jira] Closed: (AXIS2-1223) DOC-LIT BARE Marshal Excption when using primitive types in a Proxy Call.

[ http://issues.apache.org/jira/browse/AXIS2-1223?page=all ] Nick Gallardo closed AXIS2-1223. Resolution: Fixed > DOC-LIT BARE Marshal Excption when using primitive types in a Proxy Call. >

[jira] Closed: (AXIS2-1212) Dispatch invocations.

[ http://issues.apache.org/jira/browse/AXIS2-1212?page=all ] Nick Gallardo closed AXIS2-1212. Resolution: Fixed > Dispatch invocations. > - > > Key: AXIS2-1212 > URL: http://issues.apache.org/jira/brows

[jira] Commented: (AXIS2-663) WSDL2Java: allow user to specify separate destination folders for src and resources

[ http://issues.apache.org/jira/browse/AXIS2-663?page=comments#action_12437263 ] Ajith Harshana Ranabahu commented on AXIS2-663: --- Fixed in the latest revision - I'll mark it as resolved after adding a couple of test cases > WSDL2J

[jira] Commented: (AXIS2-1177) I am getting "OMException: Can't find datahandler" when I try to execute render operation on MSRS 2005. It seems that the axis2 generated stub client is not able to hand

[ http://issues.apache.org/jira/browse/AXIS2-1177?page=comments#action_12437252 ] Davanum Srinivas commented on AXIS2-1177: - Please point your browser to this issue: http://issues.apache.org/jira/browse/AXIS2-1177 One the left hand side,

[jira] Resolved: (AXIS2-1210) ADB databinding - Sending null byte array generates a wrong request message

[ http://issues.apache.org/jira/browse/AXIS2-1210?page=all ] Davanum Srinivas resolved AXIS2-1210. - Resolution: Fixed Applied a fix. please retest. thanks, dims > ADB databinding - Sending null byte array generates a wrong request message > ---

[jira] Resolved: (AXIS2-1211) Mapping a value of type xs:dateTime to null

[ http://issues.apache.org/jira/browse/AXIS2-1211?page=all ] Davanum Srinivas resolved AXIS2-1211. - Resolution: Fixed Matthias, Checked in the fix. Can you please review? and/or try nightly build to see if it indeed fixes your problem. thanks, dim

[jira] Resolved: (AXIS2-1208) ADB databinding - org.apache.axis2.databinding.utils.ConverterUtil$ObjectConversionException: java.lang.ArrayStoreException exception throw when convert the string repres

[ http://issues.apache.org/jira/browse/AXIS2-1208?page=all ] Davanum Srinivas resolved AXIS2-1208. - Resolution: Fixed Applied a fix. thanks, dims > ADB databinding - > org.apache.axis2.databinding.utils.ConverterUtil$ObjectConversionException: >

Re: [Axis2] Status of JaxWS module (was:Re: Axis2 release progress (Axis2 1.1))

Dims, thanks for the information. Although we have made a lot of progress on the code, I don't think it is quite ready for even an experimental release.  Our focus has been on getting functionality into the code, and there really are no samples and no documentation at this point.  In addition, th

[jira] Commented: (AXIS2-1222) WSDL2Java throws a StackOverflowError

[ http://issues.apache.org/jira/browse/AXIS2-1222?page=comments#action_12437237 ] Davanum Srinivas commented on AXIS2-1222: - Ajith, I don't see a check-in for the cyclic import problem...when did you do this? thanks, dims > WSDL2Java t

Re: [Axis2] Status of JaxWS module (was:Re: Axis2 release progress (Axis2 1.1))

- Add the jar to either the min dist or std dist- Make sure there are some samples that people can try out- Make sure that there is some documentation along with it.- Make a note in the Release notes that it is not really ready for production use, just as something that we are working on, but not y

[jira] Commented: (AXIS-2565) download links to older versions are broken

[ http://issues.apache.org/jira/browse/AXIS-2565?page=comments#action_12437236 ] Davanum Srinivas commented on AXIS-2565: http://archive.apache.org/ > download links to older versions are broken >

[jira] Commented: (AXIS2-969) Missing xsi:type in SOAP-Message

[ http://issues.apache.org/jira/browse/AXIS2-969?page=comments#action_12437235 ] Davanum Srinivas commented on AXIS2-969: increasing priority as this is a clear regression. -- dims > Missing xsi:type in SOAP-Message > --

[jira] Updated: (AXIS2-969) Missing xsi:type in SOAP-Message

[ http://issues.apache.org/jira/browse/AXIS2-969?page=all ] Davanum Srinivas updated AXIS2-969: --- Priority: Blocker (was: Major) > Missing xsi:type in SOAP-Message > > > Key: AXIS2-969 >

[jira] Commented: (AXIS2-1222) WSDL2Java throws a StackOverflowError

[ http://issues.apache.org/jira/browse/AXIS2-1222?page=comments#action_12437234 ] Ajith Harshana Ranabahu commented on AXIS2-1222: I have corrected the cyclic import problem for the wsdl imports but WSDL4J seems to be failing in

[jira] Created: (AXIS2-1227) Deserializing a array parameter is invalid

Deserializing a array parameter is invalid -- Key: AXIS2-1227 URL: http://issues.apache.org/jira/browse/AXIS2-1227 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Addressing

[jira] Commented: (AXIS2-969) Missing xsi:type in SOAP-Message

[ http://issues.apache.org/jira/browse/AXIS2-969?page=comments#action_12437214 ] Thomas, Berlinghoff commented on AXIS2-969: --- Hi all, just want to let you know that the current nightly snap (2006-09.24) got the mentioned problem again.

[jira] Created: (AXIS-2565) download links to older versions are broken

download links to older versions are broken --- Key: AXIS-2565 URL: http://issues.apache.org/jira/browse/AXIS-2565 Project: Apache Axis Issue Type: Bug Components: Documentation Affects V

[jira] Created: (AXIS2-1226) Can't deserialize a nil parameter to null

Can't deserialize a nil parameter to null - Key: AXIS2-1226 URL: http://issues.apache.org/jira/browse/AXIS2-1226 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: databinding A

[jira] Created: (AXIS2-1225) JAXWS is creating AxisService without regard to the WSDL port to use

JAXWS is creating AxisService without regard to the WSDL port to use Key: AXIS2-1225 URL: http://issues.apache.org/jira/browse/AXIS2-1225 Project: Apache Axis 2.0 (Axis2) I

Re: [Axis2] Status of JaxWS module (was:Re: Axis2 release progress (Axis2 1.1))

Hi Thilina, Could you, or someone, please elaborate on what releasing JAXWS as an "experimental feature" means? Thanks, Jeff IBM Software Group - WebSphere Web Services Development Phone: 512-838-4587 or Tie Line 678-4587 Internet e-mail and Sametime ID: [EMAIL PROTECTED] "Thilina Gunarath

Re: [axis2] Improvements to Service life cycle in handling - setOperationContext not thread-safe??!!

Entered as http://issues.apache.org/jira/browse/AXIS2-1224 . I set the priority to blocker as David suggested. IMHO it's probably best to drop the method. Many users will use it in an intuitive but wrong way. The only way to store the data it provides is an instance variable, and telling users to

[jira] Commented: (AXIS2-1224) setOperationContext() not thread-safe

[ http://issues.apache.org/jira/browse/AXIS2-1224?page=comments#action_12437201 ] Christopher Sahnwaldt commented on AXIS2-1224: -- The issue has also been raised here http://www.mail-archive.com/axis-dev@ws.apache.org/msg19379.html

[jira] Commented: (AXIS2-1224) setOperationContext() not thread-safe

[ http://issues.apache.org/jira/browse/AXIS2-1224?page=comments#action_12437200 ] Christopher Sahnwaldt commented on AXIS2-1224: -- It *IS* possible to implement setOperationContext() in a thread-safe way: store data not in a normal in

[jira] Commented: (AXIS2-1224) setOperationContext() not thread-safe

[ http://issues.apache.org/jira/browse/AXIS2-1224?page=comments#action_12437199 ] Christopher Sahnwaldt commented on AXIS2-1224: -- Here is an example of a user implementing setOperationContext in exactly this non-thread-safe way: ht

[jira] Created: (AXIS2-1224) setOperationContext() not thread-safe

setOperationContext() not thread-safe - Key: AXIS2-1224 URL: http://issues.apache.org/jira/browse/AXIS2-1224 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core, deployment Affe

Re: [axis2] Improvements to Service life cycle in handling - setOperationContext not thread-safe??!!

IMO this should be a blocker for 1.1 David On 24/09/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Chris, Can you please raise a new issue in JIRA? thanks, dims On 9/23/06, Christopher Sahnwaldt <[EMAIL PROTECTED]> wrote: > Something worries me: > > > setOperationContext(OperationContext) -