[jira] Resolved: (AXIS2-3769) Reinstate the MessageContextChangeTest

[ https://issues.apache.org/jira/browse/AXIS2-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3769. - Resolution: Fixed This test seems to be passing now without any issues. I tested with both JDK 1

[jira] Commented: (AXIS2-3197) configurable hot deployment

[ https://issues.apache.org/jira/browse/AXIS2-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978655#action_12978655 ] Sameera Jayasoma commented on AXIS2-3197: - I'll take this. Thanks Sameera > confi

[jira] Resolved: (AXIS2-4610) ServiceLifeCycle shutDown() doesn't fire upon hot update

[ https://issues.apache.org/jira/browse/AXIS2-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4610. - Resolution: Fixed Applied patch provided by Sameera Jayasoma. > ServiceLifeCycle shutDown() does

[jira] Updated: (AXIS2-4610) ServiceLifeCycle shutDown() doesn't fire upon hot update

[ https://issues.apache.org/jira/browse/AXIS2-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sameera Jayasoma updated AXIS2-4610: Attachment: patch-AXIS2-4610.txt This patch provide a fix for this issue. When the ServiceL

Hudson build is back to normal : axis2-1.5 #120

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build is back to normal : ax is2-1.5 » Apache Axis2 - Parent #120

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] Assigned: (AXIS2-4263) Stopping ListenerManager does not cleanup several Timer threads

[ https://issues.apache.org/jira/browse/AXIS2-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera reassigned AXIS2-4263: - Assignee: Srinath Perera (was: Hemapani Perera) > Stopping ListenerManager does not clea

[jira] Commented: (AXIS2-4902) Changes in Axiom OSGi support break Axis2 OSGi bundle

[ https://issues.apache.org/jira/browse/AXIS2-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978460#action_12978460 ] Andreas Veithen commented on AXIS2-4902: Short status update on this issue: I think

[jira] Commented: (AXIS2-3769) Reinstate the MessageContextChangeTest

[ https://issues.apache.org/jira/browse/AXIS2-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978412#action_12978412 ] Davanum Srinivas commented on AXIS2-3769: - Azeez, Thanks for picking this up from m

[jira] Assigned: (AXIS2-3769) Reinstate the MessageContextChangeTest

[ https://issues.apache.org/jira/browse/AXIS2-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3769: --- Assignee: Afkham Azeez (was: Davanum Srinivas) > Reinstate the MessageContextChangeTest > --

[jira] Assigned: (AXIS2-3452) wsdl2code maven2 plugin should not generate build.xml file.

[ https://issues.apache.org/jira/browse/AXIS2-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3452: --- Assignee: Afkham Azeez > wsdl2code maven2 plugin should not generate build.xml file. > --

[jira] Assigned: (AXIS2-4500) Using the SOAP Monitor with server listening adress & port number

[ https://issues.apache.org/jira/browse/AXIS2-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4500: --- Assignee: Afkham Azeez > Using the SOAP Monitor with server listening adress & port number >

[jira] Assigned: (AXIS2-3316) Control whether a WSDL is returned when ?wsdl comes in - both at service level and global level

[ https://issues.apache.org/jira/browse/AXIS2-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3316: --- Assignee: Afkham Azeez (was: Deepal Jayasinghe) > Control whether a WSDL is returned when ?

[jira] Assigned: (AXIS2-3292) OutInAxisOperation violates the Callback/AxisCallback contract with onComplete(), onMessage() and onError()

[ https://issues.apache.org/jira/browse/AXIS2-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3292: --- Assignee: Afkham Azeez (was: Deepal Jayasinghe) > OutInAxisOperation violates the Callback/A

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

[ https://issues.apache.org/jira/browse/AXIS2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-1220: --- Assignee: Afkham Azeez (was: Deepal Jayasinghe) > AxisServlet.initContextRoot assumes 1 leve

[jira] Assigned: (AXIS2-4731) Inefficient inputstream reading in JSONDataSource

[ https://issues.apache.org/jira/browse/AXIS2-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4731: --- Assignee: Isuru Eranga Suriarachchi > Inefficient inputstream reading in JSONDataSource > ---

[jira] Assigned: (AXIS2-4879) Enable setting ConfigContextTimeoutInterval OR LastTouchedTime to 0 programmatically

[ https://issues.apache.org/jira/browse/AXIS2-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4879: --- Assignee: Afkham Azeez > Enable setting ConfigContextTimeoutInterval OR LastTouchedTime to 0

[jira] Assigned: (AXIS2-4852) EncryptedData in body throws mustunderstand exception

[ https://issues.apache.org/jira/browse/AXIS2-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4852: --- Assignee: Prabath Siriwardena > EncryptedData in body throws mustunderstand exception > -

[jira] Assigned: (AXIS2-2956) ServiceGroupContext complete method

[ https://issues.apache.org/jira/browse/AXIS2-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-2956: --- Assignee: Afkham Azeez (was: Deepal Jayasinghe) > ServiceGroupContext complete method > ---

[jira] Assigned: (AXIS2-4902) Changes in Axiom OSGi support break Axis2 OSGi bundle

[ https://issues.apache.org/jira/browse/AXIS2-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4902: --- Assignee: Andreas Veithen > Changes in Axiom OSGi support break Axis2 OSGi bundle > -

[jira] Resolved: (AXIS2-1991) ServiceGroupContextID re-created by second client calling in scope=soapsession making first client session fail with exception unknown ServiceGroupContextID

[ https://issues.apache.org/jira/browse/AXIS2-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-1991. - Resolution: Fixed this should be fixed now since we have been able to run many concurrency tests

[jira] Resolved: (AXIS2-3100) How can I integrate Spring , Hibernate with Axis2?

[ https://issues.apache.org/jira/browse/AXIS2-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3100. - Resolution: Not A Problem Please do not use JIRA to ask questions. You could use the mailing list

[jira] Resolved: (AXIS2-3225) Destroy method is called again when undeploying Axis2

[ https://issues.apache.org/jira/browse/AXIS2-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3225. - Resolution: Fixed > Destroy method is called again when undeploying Axis2 > -

[jira] Resolved: (AXIS2-3386) i ran findbugs over the cobra's source code and its suggest that Class defines equals() and uses Object.hashCode()

[ https://issues.apache.org/jira/browse/AXIS2-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3386. - Resolution: Fixed public int hashCode() { return getValueAsString().hashCode(); } >

[jira] Resolved: (AXIS2-3446) How to Capture the Server Side Session Value From Axis Client

[ https://issues.apache.org/jira/browse/AXIS2-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3446. - Resolution: Not A Problem You should deploy your service on soapsession or transportsession scope

[jira] Commented: (AXIS2-3667) Axis2 generated code not compiles: toOM(Object, boolean) invocation is generated and the only implementation is toOM(Object, org.apache.axiom.soap.SOAPFactory, boolean)

[ https://issues.apache.org/jira/browse/AXIS2-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978364#action_12978364 ] Afkham Azeez commented on AXIS2-3667: - Dennis, Can you please verify this? > Axis2 g

[jira] Assigned: (AXIS2-3699) Termination of the soapsession

[ https://issues.apache.org/jira/browse/AXIS2-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3699: --- Assignee: Afkham Azeez > Termination of the soapsession > -- > >

[jira] Resolved: (AXIS2-3762) Problem with SimpleAxisServer

[ https://issues.apache.org/jira/browse/AXIS2-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3762. - Resolution: Fixed > Problem with SimpleAxisServer > - > >

[jira] Assigned: (AXIS2-3933) Axis2 kernel currently has a direct dependency on Commons HttpClient 3.1

[ https://issues.apache.org/jira/browse/AXIS2-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3933: --- Assignee: Andreas Veithen Andreas, Would you be able to look into this.? Thanks Azeez > Axi

[jira] Commented: (AXIS2-1109) ant task for deploying aar file to running axis2 web application

[ https://issues.apache.org/jira/browse/AXIS2-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978355#action_12978355 ] Reinout van Schouwen commented on AXIS2-1109: - Hi Deepal, Could you provide a

[jira] Resolved: (AXIS2-3980) InvocationResponse.ABORT Exception

[ https://issues.apache.org/jira/browse/AXIS2-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3980. - Resolution: Won't Fix You could throw an AxisFault from your handler with a proper fault message.

[jira] Updated: (AXIS2-3990) Produce Axis2 documentation in a form suitable for printing and offline reading

[ https://issues.apache.org/jira/browse/AXIS2-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez updated AXIS2-3990: Priority: Minor (was: Major) Assignee: Dennis Sosnoski > Produce Axis2 documentation in a form

[jira] Resolved: (AXIS2-4541) IllegalArgumentException with pojo based service using useOriginalwsdl=true and static WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4541. - Resolution: Fixed already fixed the issue > IllegalArgumentExcep

[jira] Resolved: (AXIS2-4851) Pojo with optional fields in WSDL - parameters are mapped by order rather than name

[ https://issues.apache.org/jira/browse/AXIS2-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4851. - Resolution: Fixed fixed already > Pojo with optional fields in W

[jira] Commented: (AXIS2-4003) Axis2 does not handle http.proxyUser and http.proxyPassword.

[ https://issues.apache.org/jira/browse/AXIS2-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978346#action_12978346 ] Afkham Azeez commented on AXIS2-4003: - Mark, That order looks correct. Can you please p

[jira] Resolved: (AXIS2-3199) Java2WSDL output for no parameters or void return type

[ https://issues.apache.org/jira/browse/AXIS2-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-3199. - Resolution: Fixed fixed with the basic profile support for POJO.

[jira] Resolved: (AXIS2-4049) Modules not engaged at message level.

[ https://issues.apache.org/jira/browse/AXIS2-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4049. - Resolution: Fixed Applied patch provide by Stefan Vladov > Modules not engaged at message level.

[jira] Resolved: (AXIS2-4619) DeploymentFileData missing NULL check -- NullPointerException guaranteed from DeploymentEngine.buildServiceGroup

[ https://issues.apache.org/jira/browse/AXIS2-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4619. - Resolution: Fixed this is not a valid senario. no need to add ser

[jira] Commented: (AXIS2-4692) Java2WSDL not generating location HTTPS

[ https://issues.apache.org/jira/browse/AXIS2-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978337#action_12978337 ] Vitor Manuel Alves Rodrigues commented on AXIS2-4692: - O colaborador em

Re: Axis2 Hackathon [04/01/11 - 06/01/11] - GMT+5:30

I guess we had a successful hackathon and continuing to fix the rest of the issues, targeting the 1.6 release from trunk by the end of this month. Thanks, Ruwan On Thu, Jan 6, 2011 at 9:36 AM, Ruwan Linton wrote: > Hi folks, > > In last 2 days of the hackathon, we have resolved all the Blocker

[jira] Assigned: (AXIS2-4087) WSDL with multiple schemas causes WS-Security to fail

[ https://issues.apache.org/jira/browse/AXIS2-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4087: --- Assignee: Prabath Siriwardena > WSDL with multiple schemas causes WS-Security to fail > -

[jira] Resolved: (AXIS2-4692) Java2WSDL not generating location HTTPS

[ https://issues.apache.org/jira/browse/AXIS2-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4692. - Resolution: Fixed resolving this issue since it is fixed in Axis2

[jira] Resolved: (AXIS2-4106) Clover Code coverage for Axis2

[ https://issues.apache.org/jira/browse/AXIS2-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4106. - Resolution: Won't Fix > Clover Code coverage for Axis2 > -- > >

[jira] Updated: (AXIS2-4365) Race condition in org.apache.axis2.jaxws.handler.HandlerChainProcessor

[ https://issues.apache.org/jira/browse/AXIS2-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi updated AXIS2-4365: Component/s: jaxws > Race condition in org.apache.axis2.jaxws.handl

[jira] Resolved: (AXIS2-4137) getAxisConfiguration cannot be called twice

[ https://issues.apache.org/jira/browse/AXIS2-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4137. - Resolution: Not A Problem The correct way to address this is by writing your own AxisConfigurator

[jira] Updated: (AXIS2-4426) axis2 responds on all endpoint urls, but delivers using the selected binding

[ https://issues.apache.org/jira/browse/AXIS2-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi updated AXIS2-4426: Component/s: jaxws > axis2 responds on all endpoint urls, but deliv

[jira] Resolved: (AXIS2-4409) update properties file(s) to correct message about valid provider/dispatch supported types

[ https://issues.apache.org/jira/browse/AXIS2-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4409. - Resolution: Fixed fixed with revision 1055890. > update properti

[jira] Resolved: (AXIS2-4334) Cannot turn off stdout messages when using WSDL 2.0

[ https://issues.apache.org/jira/browse/AXIS2-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4334. - Resolution: Fixed already fixed. Now it uses log4j to log the mes

[jira] Commented: (AXIS2-4331) Nullpointer while accessing service in weblogic8.1

[ https://issues.apache.org/jira/browse/AXIS2-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978326#action_12978326 ] Amila Chinthaka Suriarachchi commented on AXIS2-4331: - Please try with

[jira] Assigned: (AXIS2-4462) Add @Generated annotation on generated code

[ https://issues.apache.org/jira/browse/AXIS2-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4462: --- Assignee: Amila Chinthaka Suriarachchi > Add @Generated annotation on generated code > --

Hudson build is back to normal : Rampart #243

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] Assigned: (AXIS2-4610) ServiceLifeCycle shutDown() doesn't fire upon hot update

[ https://issues.apache.org/jira/browse/AXIS2-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4610: --- Assignee: Afkham Azeez > ServiceLifeCycle shutDown() doesn't fire upon hot update > -

[jira] Commented: (AXIS2-4611) JAX-WS services can no longer be deployed as AAR

[ https://issues.apache.org/jira/browse/AXIS2-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978318#action_12978318 ] Afkham Azeez commented on AXIS2-4611: - Perhaps, what we could do is have a mechanism of

[jira] Resolved: (AXIS2-4646) Publish updates schemas for module.xml and services.xml

[ https://issues.apache.org/jira/browse/AXIS2-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4646. - Resolution: Fixed Applied patch provided by Pradeeban. > Publish updates schemas for module.xml

[jira] Assigned: (AXIS2-4630) ADB generates code that doesn't compile when WSDL has abstract types.

[ https://issues.apache.org/jira/browse/AXIS2-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4630: --- Assignee: Amila Chinthaka Suriarachchi > ADB generates code that doesn't compile when WSDL ha

Re: Date string can not be less than 19 charactors

Please file a JIRA with the stacktraces, and relevant resources. We will take a look at this issue. It would be great if you could provide a test case as well. It would be even better if you could provide a patch :) Azeez On Thu, Jan 6, 2011 at 6:08 PM, Amarnath Reddy wrote: > Yes i am also faci

Re: Date string can not be less than 19 charactors

Yes i am also facing the same problem while sending request from the axis2 client(for java.util.date) On Thu, Jan 6, 2011 at 4:34 PM, Chinmoy Chakraborty wrote: > Hello, > > I am getting error "date string can not be less than 19 charactors" while > returning a date from a published service.

[jira] Commented: (AXIS2-3268) AxisCallback interface: add isComplete() method (if possible, add a default implementation class in the same package)

[ https://issues.apache.org/jira/browse/AXIS2-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978296#action_12978296 ] Afkham Azeez commented on AXIS2-3268: - For further details see the test1194 method in:

[jira] Resolved: (AXIS2-3073) commons-logging and log4j property files should not be placed at the root of axis2 binary distro

[ https://issues.apache.org/jira/browse/AXIS2-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3073. - Resolution: Fixed > commons-logging and log4j property files should not be placed at the root of

[jira] Resolved: (AXIS2-4718) Code generated by WSDL2JAVA is not compatible with original WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi resolved AXIS2-4718. -- Resolution: Not A Problem Thanks Supun for verifying the issue. As Su

[jira] Assigned: (AXIS2-4718) Code generated by WSDL2JAVA is not compatible with original WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reassigned AXIS2-4718: Assignee: Isuru Eranga Suriarachchi > Code generated by WSDL2JAVA i

[jira] Commented: (AXIS2-4718) Code generated by WSDL2JAVA is not compatible with original WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978287#action_12978287 ] Supun Malinga commented on AXIS2-4718: -- Hi, Found the actual problem. In the wsdl you

Re: Date string can not be less than 19 charactors

Can you debug the source and find the value of 'source' in line 892 of ConverterUtil? On Thu, Jan 6, 2011 at 5:01 PM, Chinmoy Chakraborty wrote: > its in org.apache.axis2.databinding.utils.ConverterUtil search for the > string and it is there > > > > > > On Thu, Jan 6, 2011 at 4:52 PM, Supun

[jira] Resolved: (AXIS2-4074) WSDL2Java not generating asynchronous client web service correctly

[ https://issues.apache.org/jira/browse/AXIS2-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4074. - Resolution: Not A Problem -s means generate synchronous only. > WSDL2Java not generating asynchr

Hudson build is back to normal : Axis2 #581

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build is back to normal : Axis2 » Apache Axis2 - Kernel #581

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] Resolved: (AXIS2-3848) writeReplace() should be deprecated in databinding/types/NegativeInteger.java et al.

[ https://issues.apache.org/jira/browse/AXIS2-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3848. - Resolution: Fixed > writeReplace() should be deprecated in databinding/types/NegativeInteger.java

[jira] Commented: (AXIS2-4350) RPCUtil handles wrapped style of SOAP messages wrongly.

[ https://issues.apache.org/jira/browse/AXIS2-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978281#action_12978281 ] Carles Royan commented on AXIS2-4350: - Em sap greu, estic de vacances fins el dia 10 de

[jira] Resolved: (AXIS2-4471) WSDL sorking in 1.4.1, don't Work in 1.5

[ https://issues.apache.org/jira/browse/AXIS2-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4471. - Resolution: Fixed already fixed in the trunk. Now we can put the

[jira] Resolved: (AXIS2-4350) RPCUtil handles wrapped style of SOAP messages wrongly.

[ https://issues.apache.org/jira/browse/AXIS2-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4350. - Resolution: Fixed Already fixed in the trunk > RPCUtil handles w

Re: Date string can not be less than 19 charactors

its in org.apache.axis2.databinding.utils.ConverterUtil search for the string and it is there On Thu, Jan 6, 2011 at 4:52 PM, Supun Malinga wrote: > Hi, > It will be easier to find the source of the error is you can send the stack > trace of the error. > > thanks, > > > On Thu, Jan 6, 20

Re: Date string can not be less than 19 charactors

Hi, It will be easier to find the source of the error is you can send the stack trace of the error. thanks, On Thu, Jan 6, 2011 at 4:34 PM, Chinmoy Chakraborty wrote: > Hello, > > I am getting error "date string can not be less than 19 charactors" while > returning a date from a published servic

[jira] Assigned: (AXIS2-3197) configurable hot deployment

[ https://issues.apache.org/jira/browse/AXIS2-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-3197: --- Assignee: Afkham Azeez (was: Deepal Jayasinghe) > configurable hot deployment >

[jira] Resolved: (AXIS2-3526) quickstartjibx sample's update() method doesn't work -- HashMap should be static?

[ https://issues.apache.org/jira/browse/AXIS2-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3526. - Resolution: Fixed Resolving as per the last comment. > quickstartjibx sample's update() method d

Re: Date string can not be less than 19 charactors

Yes, I searched the entire Axis2 code base for the typo 'charactors' and could not find any code having that string. On Thu, Jan 6, 2011 at 4:47 PM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote: > Looks like custom error from your service. > > ** > Martin > > 2011/1/6 Chinmoy Chakra

[jira] Resolved: (AXIS2-1871) Publishing a class without an access modifier as a service

[ https://issues.apache.org/jira/browse/AXIS2-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-1871. - Resolution: Fixed > Publishing a class without an access modifier as a service >

[jira] Resolved: (AXIS2-1890) Add @SuppressWarnings({"unchecked","unused"}) to Java code template

[ https://issues.apache.org/jira/browse/AXIS2-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-1890. - Resolution: Fixed > Add @SuppressWarnings({"unchecked","unused"}) to Java code template > ---

[jira] Updated: (AXIS2-4569) wsdl2java: Callback handlers have incorrectly capitalized methods

[ https://issues.apache.org/jira/browse/AXIS2-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez updated AXIS2-4569: Priority: Critical (was: Minor) > wsdl2java: Callback handlers have incorrectly capitalized metho

[jira] Assigned: (AXIS2-4569) wsdl2java: Callback handlers have incorrectly capitalized methods

[ https://issues.apache.org/jira/browse/AXIS2-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4569: --- Assignee: Amila Chinthaka Suriarachchi > wsdl2java: Callback handlers have incorrectly capit

Date string can not be less than 19 charactors

Hello, I am getting error "date string can not be less than 19 charactors" while returning a date from a published service. I am using Axis2 1.5.1. Could anyone give me a pointer about what causes this error? Chinmoy

[jira] Resolved: (AXIS2-3268) AxisCallback interface: add isComplete() method (if possible, add a default implementation class in the same package)

[ https://issues.apache.org/jira/browse/AXIS2-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3268. - Resolution: Not A Problem You can use a wait & notify mechanism. e.g. final org.wso2.interop.mi

[jira] Commented: (AXIS2-4718) Code generated by WSDL2JAVA is not compatible with original WSDL

[ https://issues.apache.org/jira/browse/AXIS2-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978265#action_12978265 ] Supun Malinga commented on AXIS2-4718: -- Hi, I tested the scenario and got the issue re

[jira] Issue Comment Edited: (AXIS2-3268) AxisCallback interface: add isComplete() method (if possible, add a default implementation class in the same package)

[ https://issues.apache.org/jira/browse/AXIS2-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978264#action_12978264 ] Afkham Azeez edited comment on AXIS2-3268 at 1/6/11 5:51 AM: - -

[jira] Reopened: (AXIS2-3268) AxisCallback interface: add isComplete() method (if possible, add a default implementation class in the same package)

[ https://issues.apache.org/jira/browse/AXIS2-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reopened AXIS2-3268: - > AxisCallback interface: add isComplete() method (if possible, add a default > implementation class

[jira] Resolved: (AXIS2-3268) AxisCallback interface: add isComplete() method (if possible, add a default implementation class in the same package)

[ https://issues.apache.org/jira/browse/AXIS2-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-3268. - Resolution: Fixed I guess this is addressed by the onComplete method > AxisCallback interface: a

[jira] Assigned: (AXIS2-4003) Axis2 does not handle http.proxyUser and http.proxyPassword.

[ https://issues.apache.org/jira/browse/AXIS2-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milinda Lakmal Pathirage reassigned AXIS2-4003: --- Assignee: Milinda Lakmal Pathirage > Axis2 does not handle http.proxy

[jira] Updated: (AXIS2-4174) wsdl2java -d adb doesn't generate correct java source of patttern when containg "

[ https://issues.apache.org/jira/browse/AXIS2-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez updated AXIS2-4174: Priority: Critical (was: Minor) > wsdl2java -d adb doesn't generate correct java source of pattter

[jira] Resolved: (AXIS2-2602) Permit axis2.xml/AxisServlet "servicePath" parameter to be empty

[ https://issues.apache.org/jira/browse/AXIS2-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-2602. - Resolution: Fixed > Permit axis2.xml/AxisServlet "servicePath" parameter to be empty > --

[jira] Resolved: (AXIS2-2856) Module Config Changes

[ https://issues.apache.org/jira/browse/AXIS2-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-2856. - Resolution: Won't Fix > Module Config Changes > - > > Key: AX

[jira] Resolved: (AXIS2-4080) AxisService's scope inside ServiceLifeCycle startUp() is always "request" scope regardless of actual

[ https://issues.apache.org/jira/browse/AXIS2-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4080. - Resolution: Fixed ServiceLifecycle.startup() is now called only after the entire AxisService obj

[jira] Resolved: (RAMPART-298) Client using SymmetricBinding runs slower and slower as more requests are made

[ https://issues.apache.org/jira/browse/RAMPART-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-298. -- Resolution: Fixed Fix Version/s: 1.6.0 Patch applied in revision 1055819. >

[jira] Assigned: (RAMPART-298) Client using SymmetricBinding runs slower and slower as more requests are made

[ https://issues.apache.org/jira/browse/RAMPART-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned RAMPART-298: Assignee: S.Uthaiyashankar > Client using SymmetricBinding runs slower and slower

[VOTE] Apache Rampart 1.5.1 release (Take 3)

Hi, This is the vote for Apache Rampart 1.5.1 release (Take3). Please review the signed artifacts: http://people.apache.org/~shankar/rampart/1.5.1/dist/ The m2 staging repository is available at: https://repository.apache.org/content/repositories/orgapacheaxis2-010/ The site is temporarily hos

[jira] Resolved: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi resolved AXIS2-4834. -- Resolution: Not A Problem Hi Dennis, I'm resolving this issue as this

[jira] Resolved: (AXIS2-3443) Axis2 should populate for custom exceptions for POJO services

[ https://issues.apache.org/jira/browse/AXIS2-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-3443. - Resolution: Fixed fixed already. Now POJO supports custom excepti

[jira] Updated: (AXIS2-2413) Invalid wsdl is generated by java2wsdl when rpc binding style is specified

[ https://issues.apache.org/jira/browse/AXIS2-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi updated AXIS2-2413: - Priority: Major (was: Critical) Issue Type: Improvement (was: Bug)

[jira] Resolved: (AXIS2-1377) Enable SOAP session support for both Axis 1.X clients and those not using WSA

[ https://issues.apache.org/jira/browse/AXIS2-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-1377. - Resolution: Won't Fix > Enable SOAP session support for both Axis 1.X clients and those not using

[jira] Resolved: (AXIS2-4131) Java http proxy settings override programmatic settings

[ https://issues.apache.org/jira/browse/AXIS2-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4131. - Resolution: Incomplete Resolving this since there has been no activity for over 2 years > Java h

[jira] Assigned: (AXIS2-4080) AxisService's scope inside ServiceLifeCycle startUp() is always "request" scope regardless of actual

[ https://issues.apache.org/jira/browse/AXIS2-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4080: --- Assignee: Afkham Azeez > AxisService's scope inside ServiceLifeCycle startUp() is always "req

[jira] Resolved: (AXIS2-4249) Axis2 - no WSDL-processing with axis2-1.4.1, but with axis2-1.3 possible

[ https://issues.apache.org/jira/browse/AXIS2-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amila Chinthaka Suriarachchi resolved AXIS2-4249. - Resolution: Fixed already fixed. can generate code with the curre

  1   2   >