[jira] Commented: (AXIS2-1916) jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp

[ https://issues.apache.org/jira/browse/AXIS2-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462162 ] Dejan Milosevic commented on AXIS2-1916: That doesn't work either. Here are the exact steps that indicate t

[jira] Updated: (AXIS2-1746) POJO client call failed with "Unexpected subelement"

[ https://issues.apache.org/jira/browse/AXIS2-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe updated AXIS2-1746: - Priority: Blocker (was: Major) I fixed this few months ago , but it has shown up again.

[jira] Resolved: (AXIS2-1774) axis2-jaxbri module does not compile

[ https://issues.apache.org/jira/browse/AXIS2-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Gunarathne resolved AXIS2-1774. --- Resolution: Fixed Fixed in the 1.1.1-RC1... We are building the release artifacts us

[jira] Commented: (AXIS2-1909) JMS samples for Axis2 release 1.2

[ https://issues.apache.org/jira/browse/AXIS2-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462157 ] Ali Sadik Kumlali commented on AXIS2-1909: -- To enable server side "log4j" logging, you should: - Put log4j'

[jira] Commented: (AXIS2-1928) Wrong code generation when xs:extension used in schema

[ https://issues.apache.org/jira/browse/AXIS2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462156 ] Amila Chinthaka Suriarachchi commented on AXIS2-1928: - I check this with the following schema

[jira] Commented: (AXIS2-1926) https access to service doesn't work

[ https://issues.apache.org/jira/browse/AXIS2-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462149 ] Deepal Jayasinghe commented on AXIS2-1926: -- Hi Gul, I tested https access using Axis2-1.1.1-RC1/tomcat 5.5.1

[jira] Resolved: (AXIS2-1922) RPCMessageReceiver obtain logger for wrong class. (Patch is attached)

[ https://issues.apache.org/jira/browse/AXIS2-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1922. -- Resolution: Fixed fixed in 1.1 branch > RPCMessageReceiver obtain logger for wrong cla

[jira] Commented: (AXIS2-1921) WSDL2JAVA fail to generate class from IBM Process Server BFM Web Service Service(BFMWS.wsdl)

[ https://issues.apache.org/jira/browse/AXIS2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462143 ] Amila Chinthaka Suriarachchi commented on AXIS2-1921: - I think the problem is with your xsd files

[jira] Commented: (AXIS2-1932) JavaScript services deployed in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462141 ] Thilina Gunarathne commented on AXIS2-1932: --- I think it's better to create a new module called javascript t

[jira] Assigned: (AXIS2-1915) Service lifecycle method shutDown() is invoked twice

[ https://issues.apache.org/jira/browse/AXIS2-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe reassigned AXIS2-1915: Assignee: Deepal Jayasinghe > Service lifecycle method shutDown() is invoked twice

[jira] Commented: (AXIS2-1916) jars, mars and aars are locked in the file system even after undeployment of the axis2 webapp

[ https://issues.apache.org/jira/browse/AXIS2-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462137 ] Deepal Jayasinghe commented on AXIS2-1916: -- If you want to do so, then you need to change axis2.xml a bit .

[jira] Commented: (AXIS2-1932) JavaScript services deployed in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462135 ] Deepal Jayasinghe commented on AXIS2-1932: -- Hi Saliya; where does this belong , is it going to be a sample

[jira] Resolved: (AXIS2-1897) WSDL2Java adding SOAPAction

[ https://issues.apache.org/jira/browse/AXIS2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1897. -- Resolution: Fixed Issue shoud be fixed in the current SVN code base (re-open if not so)

[jira] Resolved: (AXIS2-1327) Incorrect operation selected when no SOAPAction specified

[ https://issues.apache.org/jira/browse/AXIS2-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deepal Jayasinghe resolved AXIS2-1327. -- Resolution: Fixed fixed the issue in the current code base. > Incorrect operation sele

[jira] Updated: (AXIS2-1935) Wrong REST EPR shown in the admin console when enabling REST

[ https://issues.apache.org/jira/browse/AXIS2-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charitha Kankanamge updated AXIS2-1935: --- Attachment: RESTepr.JPG > Wrong REST EPR shown in the admin console when enabling RES

Re: Axis2 1.1 - ERROR http-8080-Processor25 org.apache.axis2.transport.http.AxisServlet - java.lang.ExceptionInInitializerError

Hi Danny; Is there any possibility of send me the service aar file , then I can have a look at that. Thanks Deepal Danny Lin wrote: > What could have caused this error? I am using Axis2 version 1.1 > release, Tomcat 5.0.28 in Windows XP environment. I am using XMLBeans > binding and I moved the

[jira] Created: (AXIS2-1935) Wrong REST EPR shown in the admin console when enabling REST

Wrong REST EPR shown in the admin console when enabling REST - Key: AXIS2-1935 URL: https://issues.apache.org/jira/browse/AXIS2-1935 Project: Apache Axis 2.0 (Axis2) Issue Type: Bu

[jira] Updated: (AXIS2-1934) Corrected an issue in rest-ws.html

[ https://issues.apache.org/jira/browse/AXIS2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charitha Kankanamge updated AXIS2-1934: --- Attachment: patch.patch > Corrected an issue in rest-ws.html > --

[jira] Created: (AXIS2-1934) Corrected an issue in rest-ws.html

Corrected an issue in rest-ws.html -- Key: AXIS2-1934 URL: https://issues.apache.org/jira/browse/AXIS2-1934 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1.1 Reporter: Ch

[jira] Commented: (AXIS2-1933) Getting Service not found operation terminated exception

[ https://issues.apache.org/jira/browse/AXIS2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462125 ] Deepal Jayasinghe commented on AXIS2-1933: -- Hi Harish Hirasave ; Please tell me how to re-create the issue

Re: [AXIS2] Proposal for saving the message context

On Wed, 2007-01-03 at 12:47 -0600, R J Scheuerle Jr wrote: > Ann's code is not fundamentally changing the MessageContext. The new > code may, over time, enhance the organization of the MessageContext > graph. I am in favor of adding this patch for the sake of iterative > development. Fine. I just

[jira] Commented: (AXIS2-1909) JMS samples for Axis2 release 1.2

[ https://issues.apache.org/jira/browse/AXIS2-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462116 ] Wu Gang commented on AXIS2-1909: Hi, Under jms sample src directory there is log4j.properties file, where to pu

[jira] Created: (AXIS2-1933) Getting Service not found operation terminated exception

Getting Service not found operation terminated exception Key: AXIS2-1933 URL: https://issues.apache.org/jira/browse/AXIS2-1933 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug

[jira] Updated: (AXIS2-1932) JavaScript services deployed in Axis2

[ https://issues.apache.org/jira/browse/AXIS2-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saliya Ekanayake updated AXIS2-1932: Attachment: JavaScriptService.zip > JavaScript services deployed in Axis2 > ---

Re: [AXIS2] Proposal for saving the message context

Ann's code is not fundamentally changing the MessageContext. The new code may, over time, enhance the organization of the MessageContext graph. I am in favor of adding this patch for the sake of iterative development. I am concerned that the arguments for/against are unduly based on company

[jira] Created: (AXIS2-1932) JavaScript services deployed in Axis2

JavaScript services deployed in Axis2 - Key: AXIS2-1932 URL: https://issues.apache.org/jira/browse/AXIS2-1932 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Reporter: Saliya Ekanayake

[jira] Commented: (AXIS2-1914) Null Pointer Exception

[ https://issues.apache.org/jira/browse/AXIS2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462013 ] new user commented on AXIS2-1914: - Hi, The error is coming from the targetEndpointaddresss. If I provide a wsdl file

[jira] Commented: (AXIS-2064) The format of multi-cookie in HTTP request head.

[ https://issues.apache.org/jira/browse/AXIS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462009 ] Amon Beckler commented on AXIS-2064: Given that we are now two "final" releases past when this bug and a potential

[jira] Commented: (AXIS2-1928) Wrong code generation when xs:extension used in schema

[ https://issues.apache.org/jira/browse/AXIS2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461981 ] Ole Dalgaard commented on AXIS2-1928: - I can reproduce this using Axis2 1.1.1-SNAPSHOT from 03-Jan-2007. The erro

[jira] Closed: (AXIS-2603) deserialization of a multiRef that contains an href to another multiRef (in fault processing)

[ https://issues.apache.org/jira/browse/AXIS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Scoda closed AXIS-2603. Resolution: Invalid The issue was not a bug in Axis. There was a WSDL difference of some sort between the

[jira] Commented: (AXIS-2603) deserialization of a multiRef that contains an href to another multiRef (in fault processing)

[ https://issues.apache.org/jira/browse/AXIS-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461968 ] Dave Scoda commented on AXIS-2603: -- This is not an issue with Axis. The error was caused by 1. the server did not c

[jira] Commented: (AXIS2-1928) Wrong code generation when xs:extension used in schema

[ https://issues.apache.org/jira/browse/AXIS2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461960 ] Ole Dalgaard commented on AXIS2-1928: - I experience exactly the same problem using Axis2 1.1 and IBM jdk 1.4.2 on

[jira] Created: (AXIS2-1931) wsdl output parameter named "return"

wsdl output parameter named "return" Key: AXIS2-1931 URL: https://issues.apache.org/jira/browse/AXIS2-1931 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions:

[jira] Commented: (AXIS2-1930) WSDL2Java - ParameterOrder

[ https://issues.apache.org/jira/browse/AXIS2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461955 ] Ajith Harshana Ranabahu commented on AXIS2-1930: Hi, Just changing the style in the binding will not

[jira] Resolved: (AXIS2-1924) No ability to set mustUnderstand=true on WS-A headers

[ https://issues.apache.org/jira/browse/AXIS2-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian DePradine resolved AXIS2-1924. Resolution: Fixed Fix Version/s: (was: 1.2) 1.1 Assig

Fwd: NTLM with Axis2 1.1

HI Jonathan, We've committed the changes to the Axis2 branch/trunk. Please take a checkout and build as mentioned in prior mail. Please be kind enough to let us know the status with the new fix. To get the NTLM auth working with host/port not given, you should have aim for a client as follow, =

[jira] Updated: (AXIS2-1930) WSDL2Java - ParameterOrder

[ https://issues.apache.org/jira/browse/AXIS2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laurent CHARTIER updated AXIS2-1930: Attachment: WSIdentLight.xsd WSIdentLight.wsdl > WSDL2Java - ParameterOrder

[jira] Commented: (AXIS2-1930) WSDL2Java - ParameterOrder

[ https://issues.apache.org/jira/browse/AXIS2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461931 ] Laurent CHARTIER commented on AXIS2-1930: - Changing style from RPC to Document makes WSDL2Java not to generat

[jira] Created: (AXIS2-1930) WSDL2Java - ParameterOrder

WSDL2Java - ParameterOrder -- Key: AXIS2-1930 URL: https://issues.apache.org/jira/browse/AXIS2-1930 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.1 Enviro

[jira] Commented: (AXIS2-1930) WSDL2Java - ParameterOrder

[ https://issues.apache.org/jira/browse/AXIS2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461930 ] Laurent CHARTIER commented on AXIS2-1930: - I assume you are using RPC/Literal style? Please file a JIRA with

[Axis2] Test failure in 1.1.1-SNAPSHOT

[junit] Running org.apache.axis2.engine.CallUnregisteredServiceTest [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 3.908 sec [junit] [ERROR] TEST org.apache.axis2.engine.CallUnregisteredServiceTestFAILED due to log4j:WARN No appenders could be found for logger ( org.apache.axi