[jira] Created: (AXIS2C-379) CLONE -LDFLAGS overridden by configure
CLONE -LDFLAGS overridden by configure -- Key: AXIS2C-379 URL: http://issues.apache.org/jira/browse/AXIS2C-379 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 0.94 Reporter: Chris Darroch Assigned To: Sanjaya Ratnaweera The configure.ac files contain the following line: LDFLAGS=-lpthread This has the effect of overriding any input LDFLAGS that the user specifies. The configure script's --help option says you can set CFLAGS, LDFLAGS, etc. prior to running ./configure: ./configure --help ... Some influential environment variables: CC C compiler command CFLAGS C compiler flags LDFLAGS linker flags, e.g. -Llib dir if you have libraries in a nonstandard directory lib dir ... The line should probably be LDFLAGS=$LDFLAGS -lpthread in all of the configure.ac files (configure, woden/configure, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2C-379) CLONE -LDFLAGS overridden by configure
[ http://issues.apache.org/jira/browse/AXIS2C-379?page=comments#action_12445326 ] Chris Darroch commented on AXIS2C-379: -- The woden/configure and xml_schema/configure files still need the fix. Thanks! CLONE -LDFLAGS overridden by configure -- Key: AXIS2C-379 URL: http://issues.apache.org/jira/browse/AXIS2C-379 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 0.94 Reporter: Chris Darroch Assigned To: Sanjaya Ratnaweera The configure.ac files contain the following line: LDFLAGS=-lpthread This has the effect of overriding any input LDFLAGS that the user specifies. The configure script's --help option says you can set CFLAGS, LDFLAGS, etc. prior to running ./configure: ./configure --help ... Some influential environment variables: CC C compiler command CFLAGS C compiler flags LDFLAGS linker flags, e.g. -Llib dir if you have libraries in a nonstandard directory lib dir ... The line should probably be LDFLAGS=$LDFLAGS -lpthread in all of the configure.ac files (configure, woden/configure, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-190) Document enabling REST in client side as well as server side
[ http://issues.apache.org/jira/browse/AXIS2C-190?page=all ] Samisa Abeysinghe closed AXIS2C-190. Fix Version/s: 0.95 Resolution: Fixed This is documented in the new manual Document enabling REST in client side as well as server side Key: AXIS2C-190 URL: http://issues.apache.org/jira/browse/AXIS2C-190 Project: Axis2-C Issue Type: Improvement Components: transport/http Affects Versions: Current (Nightly) Reporter: Sahan Gamage Priority: Minor Fix For: 0.95 We need to document the REST features. This should include how to enable REST programmatically as well as using configuration file axis2.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-374) A document on using Adressing in Axis2/C
[ http://issues.apache.org/jira/browse/AXIS2C-374?page=all ] Samisa Abeysinghe closed AXIS2C-374. Fix Version/s: 0.95 Resolution: Fixed This doc was included in manual. Thank you for the contribution. A document on using Adressing in Axis2/C Key: AXIS2C-374 URL: http://issues.apache.org/jira/browse/AXIS2C-374 Project: Axis2-C Issue Type: Improvement Affects Versions: 0.95 Reporter: Manjula Peiris Fix For: 0.95 Attachments: addressing.html Attached document describes the use of WS Addressing in Axis2/C -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1510) Included schema filenames impact wsdl2java with xmlbeans binding
[ http://issues.apache.org/jira/browse/AXIS2-1510?page=comments#action_12445093 ] Mariusz Woloncewicz commented on AXIS2-1510: Attached wsdl/schemas were written in xmlspy and passed validation. Could you point out these problems? Code generation with default ADB binding works fine. Included schema filenames impact wsdl2java with xmlbeans binding Key: AXIS2-1510 URL: http://issues.apache.org/jira/browse/AXIS2-1510 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Mariusz Woloncewicz Attachments: subscribe.xsd, TestServices.wsdl, TestServicesFAIL.wsdl, unsubscribe.xsd Types declaration in wsdl: xs:include schemaLocation=subscribe.xsd/ xs:include schemaLocation=unsubscribe.xsd/ xs:element name=subscribe type=tns:SubscribeType/ xs:element name=unsubscribe type=tns:UnsubscribeType/ Output generated by wsdl2java.bat -uri TestServices.wsdl -d xmlbeans : Retrieving schema at 'subscribe.xsd', relative to 'file:/C:/JIRA/'. Retrieving schema at 'unsubscribe.xsd', relative to 'file:/C:/JIRA/'. 2006-10-26 10:35:52 org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityR esolver resolveEntity INFO: Resolving schema with publicId [null] and systemId [subscribe.xsd] 2006-10-26 10:35:52 org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityR esolver resolveEntity INFO: Resolving schema with publicId [null] and systemId [unsubscribe.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetExcepti on at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB eansExtension.java:92) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:177) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB eansExtension.java:82) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: src-resolve: type '[EMAIL PROTECTED]/request/beans' not found. at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:241) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: src-resolve: type 'Subscribe [EMAIL PROTECTED]/request/beans' not found. at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(Sche maTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:167) ... 8 more Current workaround is renaming unsubscribe.xsd file (for instance, to unsubscription.xsd). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: svn commit: r468217 - in /webservices/axis2/branches/java/1_1: ./ modules/adb-codegen/ modules/adb/ modules/codegen/ modules/java2wsdl/ modules/kernel/ modules/parent/ modules/tool/ modules/tool/
On 10/27/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: Is it worth doing this for the 1.1 release branch at all? I would think, that it is particularly worth to do this in the release branch, because users will use that version of Axis2 and not so much the trunk. Besides, after finishing the work on the Maven plugins, I intend to pull these things up into the trunk. So, the work isn't lost. Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1510) Included schema filenames impact wsdl2java with xmlbeans binding
[ http://issues.apache.org/jira/browse/AXIS2-1510?page=comments#action_12445095 ] Mariusz Woloncewicz commented on AXIS2-1510: Nevertheless, renaming the file name of included schema has influence on code generation. It seems not to be a correct behaviour. Included schema filenames impact wsdl2java with xmlbeans binding Key: AXIS2-1510 URL: http://issues.apache.org/jira/browse/AXIS2-1510 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Mariusz Woloncewicz Attachments: subscribe.xsd, TestServices.wsdl, TestServicesFAIL.wsdl, unsubscribe.xsd Types declaration in wsdl: xs:include schemaLocation=subscribe.xsd/ xs:include schemaLocation=unsubscribe.xsd/ xs:element name=subscribe type=tns:SubscribeType/ xs:element name=unsubscribe type=tns:UnsubscribeType/ Output generated by wsdl2java.bat -uri TestServices.wsdl -d xmlbeans : Retrieving schema at 'subscribe.xsd', relative to 'file:/C:/JIRA/'. Retrieving schema at 'unsubscribe.xsd', relative to 'file:/C:/JIRA/'. 2006-10-26 10:35:52 org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityR esolver resolveEntity INFO: Resolving schema with publicId [null] and systemId [subscribe.xsd] 2006-10-26 10:35:52 org.apache.axis2.xmlbeans.CodeGenerationUtility$Axis2EntityR esolver resolveEntity INFO: Resolving schema with publicId [null] and systemId [unsubscribe.xsd] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException : java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:224) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetExcepti on at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB eansExtension.java:92) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener ationEngine.java:177) ... 2 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage(XMLB eansExtension.java:82) ... 3 more Caused by: java.lang.RuntimeException: org.apache.xmlbeans.XmlException: error: src-resolve: type '[EMAIL PROTECTED]/request/beans' not found. at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:241) ... 8 more Caused by: org.apache.xmlbeans.XmlException: error: src-resolve: type 'Subscribe [EMAIL PROTECTED]/request/beans' not found. at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(Sche maTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(CodeGe nerationUtility.java:167) ... 8 more Current workaround is renaming unsubscribe.xsd file (for instance, to unsubscription.xsd). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1521) Un-necessary test folder is created when the generated ant script was executed
Un-necessary test folder is created when the generated ant script was executed -- Key: AXIS2-1521 URL: http://issues.apache.org/jira/browse/AXIS2-1521 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: codegen Affects Versions: 1.1 Reporter: Eran Chinthaka Assigned To: Eran Chinthaka Priority: Minor When we code gen for a WSDL we also get a ant build script. When it was used to create the aar file, it also generates an empty folder named test. This empty folder better be cleaned up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1522) Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not in 1.0 stable
Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not in 1.0 stable - Key: AXIS2-1522 URL: http://issues.apache.org/jira/browse/AXIS2-1522 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: nightly Environment: Win2k, SUN JDK 1.5.0_08 Reporter: Frank Steimke Priority: Minor Hi, attached to this bugreport you will find the WSDL-File with three included Schemafiles for Type-Definitions. We are dealing with German eGovernment Applications, so there is a lot of documentation with German Text, inkluding German Umlaut. The main Schemafile, which is imported from WSDL, is xmeld-nachrichten.xsd. It was checked by IBMs Schema Quality Checker (SQC) without any Errors. Trying to generate Java Code by WSDL2Java works fine with AXIS2 1.0 standard Release, but compilation with ant jar.server failed. So I switched to nightly build from October 26. Trying to generate Java Code by WSDL2Java fails with a Malformed UTF-8 Character Exception. The Stacktrace gave some hints about this strange Character. Something seems to be wrong in a documentation where we find a German word with the Fragment 'über...', which is used a lot in these Files. So I removed all annotation Nodes within all three Schemata, and everything is fine. WSDL2Java generates Code without Exception, and this compiles to the *aar Archive without any Errors. This is a minor bug, as i have a Workaround to deal with it. But, besides of resolving the Error, my Question is: why did Axis2 1.0 standard work fine, and the snapshot did not? Did you change the the XML Parser or its configuration? Thanks in advance, Frank Steimke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1522) Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not in 1.0 stable
[ http://issues.apache.org/jira/browse/AXIS2-1522?page=all ] Frank Steimke updated AXIS2-1522: - Attachment: wsdl.zip WSDL File with imported Schema. The documentation wich causes the error is part of the Schema (don``t know which one in particular). This results in a Malformed UTF-8 Character Exception when doing WSDL2Java. Remove all annotations in the Schema, an everything is fine. Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not in 1.0 stable - Key: AXIS2-1522 URL: http://issues.apache.org/jira/browse/AXIS2-1522 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: nightly Environment: Win2k, SUN JDK 1.5.0_08 Reporter: Frank Steimke Priority: Minor Attachments: wsdl.zip Hi, attached to this bugreport you will find the WSDL-File with three included Schemafiles for Type-Definitions. We are dealing with German eGovernment Applications, so there is a lot of documentation with German Text, inkluding German Umlaut. The main Schemafile, which is imported from WSDL, is xmeld-nachrichten.xsd. It was checked by IBMs Schema Quality Checker (SQC) without any Errors. Trying to generate Java Code by WSDL2Java works fine with AXIS2 1.0 standard Release, but compilation with ant jar.server failed. So I switched to nightly build from October 26. Trying to generate Java Code by WSDL2Java fails with a Malformed UTF-8 Character Exception. The Stacktrace gave some hints about this strange Character. Something seems to be wrong in a documentation where we find a German word with the Fragment 'über...', which is used a lot in these Files. So I removed all annotation Nodes within all three Schemata, and everything is fine. WSDL2Java generates Code without Exception, and this compiles to the *aar Archive without any Errors. This is a minor bug, as i have a Workaround to deal with it. But, besides of resolving the Error, my Question is: why did Axis2 1.0 standard work fine, and the snapshot did not? Did you change the the XML Parser or its configuration? Thanks in advance, Frank Steimke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1457) RequestURIBasedDispatcher incorrectly resolves the WS-RM operations
[ http://issues.apache.org/jira/browse/AXIS2-1457?page=comments#action_12445104 ] David Illsley commented on AXIS2-1457: -- I committed slight modifications of these patches to trunk a couple of days ago. I included AXIS2-1457 in the first line of the commit but it's not appearing on the page, presumably because of the infra changes RequestURIBasedDispatcher incorrectly resolves the WS-RM operations --- Key: AXIS2-1457 URL: http://issues.apache.org/jira/browse/AXIS2-1457 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Reporter: Matt Lovett Assigned To: David Illsley Attachments: axisxml.patch, dispatch.patch I have a testcase that is an async 2-way scenario, with Sandesha enabled. Sending the request causes Sandesha to set up a CreateSequence message targeted at the To address of the service, the RM handshake completes, and the application request message goes out. When the other end generates the response message Sandesha again creates a sequence, this time inbound to the requester, using the To address of the reply message. As you would expect, the To address is generated from the ReplyTo EPR in the request. In my case the 2 addresses look like this: Request To: aixs2/services/RMSampleService Reply To: axis2/services/anonServiceuuid/anonOutInOp As the CreateSequence message comes into the latter of these, the RequestURIBasedDispatcher (wrongly) decides that we are targeting the anonOutInOp, when the SOAPAction and Addressing dispatchers would have identified the CreateSequence operation properly. With the current Sandesha code this is not an issue, as the inbound Sandesha handlers intercept and process the CreateSequence, ignoring the operation set in the message context. I am trying to restructure Sandesha so that the message is automatically routed to the Sandesha message receiver. Doing so will clean up the flow through Sandesha, but does rely on accurate operation resolution. I can see 2 ways to fix the issue: - Stop attempting to identify the operation in the RequestURIBasedDispatcher or - Generate ReplyTo addresses that do not include the operation name Patches for either of these are trivial, I'm happy to contribute them if people can tell me their preferred option. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1523) Axis2 Backward compatibility mode
Axis2 Backward compatibility mode - Key: AXIS2-1523 URL: http://issues.apache.org/jira/browse/AXIS2-1523 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: codegen Reporter: Eran Chinthaka When we code-gen out of a WSDL in Axis2 and when we compare that generated code with that you get from Axis 1.X there are couple of differences. Out of them if following can be done, when makeBackwardCompatible flag is on, it will great for users who are transferring from Axis 1.x to Axis2. 1. Remove the wrapping of generated request/response objects. Axis 1.x does not generate classes for top level element, or at least they are not visible in method signatures. 2. Rename the Axis2 generated impl/interface class to follow the same naming convention and interface as in axis1.1. For example: servicenameSkeleton.java (Axis2) should be renamed to servicenameBindingImpl (Axis1) servicenameSkeletonInterface (Axis2) should be renamed to sevicenameInterface (Axis1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1524) Server side interface is generated along with the skeleton even though it is not specified with code gen long options
Server side interface is generated along with the skeleton even though it is not specified with code gen long options - Key: AXIS2-1524 URL: http://issues.apache.org/jira/browse/AXIS2-1524 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.1 Environment: Win XP, Jdk 1.4 Reporter: Charitha Kankanamge I specified the following command line code generation long options. wsdl2java -uri C:\Axis\axis-rc\axis2-1.1\samples\wsdl\Axis2SampleDocLit.wsdl --package org.mypackage --server-side --service-descr iption --databinding-method xmlbeans -output C:\rctesting\longoptions\server1 I noticed that the Axis2SampleDocLitServiceSkeletonInterface was also generated with the server side skeleton. It was supposed to be generated only if the '--serverside-interface' option is specified. This worked correctly with the short options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote][Axis2] Amila, Keith and Sandakith as committers
+1! On 10/26/06, R J Scheuerle Jr [EMAIL PROTECTED] wrote: +1 for all three. Welcome aboard ! Rich Scheuerle IBM Web Services Apache Axis2 ([EMAIL PROTECTED]) 512-838-5115 (IBM TL 678-5115) -- Srinath Perera: Indiana University, Bloomington http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for XML Filter (AXIS2-1085)
Henry said: henry One of the possible use cases for filter is for checking uniqness of a piece of data, if this is implemented in using filter, the check and enforcement can be done during the parsing of the message. This will save the walking of the OM tree again. /henry A uniquenes check requires the inspection of the entire message. If a uniquess check is performed with a handler solution, there are several undesirable outcomes: 1) the OM tree will be traversed, which is expensive. 2) the OM tree will be expanded and cached, which kills performance. If a uniquess check is performed with a filter and handler solution: 1) The filter can inspect the StAX events as they are read. The filter will not affect the caching of the OM tree. The filter will not pull StAX events. 2) The filter will store its results on the MessageContext. Handlers pull StAX events. Filters don't pull StAX events. They intercept and propogate StAX events. Comments ? Takahide / Henry can you provide more justifications or feedback for this request ? Thanks, Let me add comment to the second outcomes of the handler solution, (2) the OM tree will be expanded and cached, which kills performance takahideand consuming memory space/takahide Regards, --- Takahide Nogayama
Re: Request for XML Filter (AXIS2-1085)
Sanjiva said: The second point is what's fundamentally inconsistent with Axis2's architecture. If you want to introduce a StAX filter that one's thing. But doing that and having access to the message context doesn't make sense: we create an OMElement for the envelope giving just the StAX stream and then create a message context using that envelope. Sorry I am not sure that I understand your point, but in my understanding, Message context is created at AxisServilet and many information are added by AxisServlet, TransportUtils (envelope is created here), AxisEngine, Dispatcher, and Handler while the message is propagated to message receiver. The information means AxisConfiguration, URL, character encoding type, SOAPAction, WSA-Action, AxisOperation, and so on. They will be used at Handler layer to provide QOS. Sanjiva said: If you want a StAX filter then it must be a StAX filter: StAX in, StAX out. I don't agree with the proposed change because its inconsistent with the design and appears to mix layers of processing. Filter might not be clean design in terms of mixed layer processing. But handler with filter is good for performance/memory perspective. Filter enables us to have an option of doing some part of the job of the handler on StAX event layer or on handler layer. It might not be must-have but nice-to-have. I think that mix layers of processing and performance improvement are trade-off problem. Regards, --- Takahide Nogayama
[jira] Created: (AXIS2-1525) Axis2 admin console crashers when rampart-1.0.mar is deployed as a module
Axis2 admin console crashers when rampart-1.0.mar is deployed as a module - Key: AXIS2-1525 URL: http://issues.apache.org/jira/browse/AXIS2-1525 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: 1.1 Environment: jdk 1.4.2, Tomcat 4.1.30 Reporter: Keith Godwin Chapman Axis2 admin console crashers when rampart-1.0.mar is deployed as a module. When the server is restarted after deploying this module cannot acces the admin console. The following is the error diaplayed on the browser org.apache.jasper.JasperException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822) at org.apache.jsp.index_jsp._jspService(index_jsp.java:64) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534) root cause java.lang.NullPointerException at org.apache.jsp.httpbase_jsp.jspInit(httpbase_jsp.java:22) at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:119) at
[jira] Created: (AXIS2-1526) Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException
Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException --- Key: AXIS2-1526 URL: http://issues.apache.org/jira/browse/AXIS2-1526 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: modules Affects Versions: 1.1 Environment: Windows XP, JDK 1.4.2_12, Latest Axis2 Nightly (27 Oct 2006), Latest Rampart Nightly (26 Oct 2006) Reporter: Ali Sadik Kumlali I've followed the README.TXT both under 'samples' and 'basic' directories and got the following exception at the first sample (service.01). You may follow the steps here: C:\axis2-rampart\samplesset AXIS2_HOME=c:/axis2 C:\axis2-rampart\samplesant Buildfile: build.xml check.dependency: setup: [copy] Copying 6 files to C:\axis2\lib [copy] Copying 2 files to C:\axis2\repository\modules BUILD SUCCESSFUL Total time: 1 second C:\axis2-rampart\samplescd basic C:\axis2-rampart\samples\basicant service.01 Buildfile: build.xml check.dependency: service.01: [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp\META-INF [javac] Compiling 1 source file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp\META-INF [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [jar] Building jar: C:\axis2-rampart\samples\basic\build\service_repositor ies\sample01\services\sample01.aar [delete] Deleting directory C:\axis2-rampart\samples\basic\build\temp [java] [SimpleHTTPServer] Starting [java] [SimpleHTTPServer] Using the Axis2 Repository C:\axis2-rampart\sampl es\basic\build\service_repositories\sample01 [java] [SimpleHTTPServer] Listening on port 8080 [java] Oct 27, 2006 1:59:32 PM org.apache.axis2.deployment.DeploymentEngine doDeploy [java] INFO: Deploying module : addressing-1.1 [java] Oct 27, 2006 1:59:33 PM org.apache.axis2.transport.http.SimpleHTTPSe rver main [java] SEVERE: Error starting SimpleHTTPServer [java] java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyExc eption [java] at java.lang.Class.getDeclaredConstructors0(Native Method) [java] at java.lang.Class.privateGetDeclaredConstructors(Class.java:161 8) [java] at java.lang.Class.getConstructor0(Class.java:1930) [java] at java.lang.Class.newInstance0(Class.java:278) [java] at java.lang.Class.newInstance(Class.java:261) [java] at org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils. java:69) [java] at org.apache.axis2.deployment.DeploymentEngine.addNewModule(Dep loymentEngine.java:326) [java] at org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deploym entEngine.java:598) [java] at org.apache.axis2.deployment.RepositoryListener.init(Repositor yListener.java:160) [java] at org.apache.axis2.deployment.RepositoryListener.init(Reposit oryListener.java:53) [java] at org.apache.axis2.deployment.DeploymentEngine.loadRepository(D eploymentEngine.java:104) [java] at org.apache.axis2.deployment.FileSystemConfigurator.getAxisCon figuration(FileSystemConfigurator.java:116) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContext(ConfigurationContextFactory.java:61) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContextFromFileSystem(ConfigurationContextFactory.java:180) [java] at org.apache.axis2.transport.http.SimpleHTTPServer.main(SimpleH TTPServer.java:157) [java] [SimpleHTTPServer] Shutting down BUILD SUCCESSFUL Total time: 3 seconds C:\axis2-rampart\samples\basic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2][ANN]Apache Axis2/C 0.95 Released
We are pleased to announce the release of Apache Axis2/C version 0.95.You can download this release from http://ws.apache.org/axis2/c/download.cgiKey Features 1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 Messages. This has complete XML infoset support. 2. Support for one-way messaging (In-Only) and request response messaging (In-Out) 3. Description hierarchy (configuration, service groups, services, operations and messages) 4. Directory based deployment model 5. Archive based deployment model 6. Context hierarchy (corresponding contexts to map to each level of description hierarchy) 7. Raw XML message receiver 8. Module architecture, mechanism to extend the SOAP processing model 9. Module version support 10. Transports supports: HTTP o Both simple axis server and Apache2 httpd module for server side o Client transport with ability to enable SSL support 11. Service client and operation client APIs 12. REST support (HTTP POST case) 13. WS-Addressing, both the submission (2004/08) and final (2005/08) versions 14. MTOM/XOP support 15. Code generation tool for stub and skeleton generation for a given WSDL (based on Java tool) o Axis Data Binding (ADB) support 16. Security module with UsernameToken support 17. REST support (HTTP GET case) 18. Dynamic invocation support (based on XML schema and WSDL implementations) 19. Guththila pull parser support 20. WSDL2C code generation tool- with schema code generation 21. TCP Monitor - C implementation 22. Axis2/C Manual - NewMajor Changes Since Last Release 1. Major Memory leak fixes 2. Many Bug Fixes 3. Improved DocumentationTODOs Remaining for 1.0 1. Complete API documentation and API improvements 2. Fix further memory leaks 3. Put in place a comprehensive functional test framework We welcome your early feedback on this implementation.Thanks for your interest in Axis2C-- Apache Axis2C Team --
[jira] Created: (AXIS2-1527) Description on OMElement in 'Write the Implementation Class' section on MyService sample is missing
Description on OMElement in 'Write the Implementation Class' section on MyService sample is missing --- Key: AXIS2-1527 URL: http://issues.apache.org/jira/browse/AXIS2-1527 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: 1.1 Environment: Windows XP/JDK 1.4 Reporter: Chatra Nakkawita Assigned To: Thilina Gunarathne Fix For: 1.1 With reference to document https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1/xmlbased-server.html The section 'Step1 :Write the Implementation Class' contains sample code from MyService that uses OMElement. For details on OMElement it links to http://ws.apache.org/commons/axiom/OMTutorial.html which is too complicated for the normal user. Can we have a adequate description on OMElement on the mentioned section itself, just enough for user to understand the use of OMElement in the code fragment. For further reference they can check out the OM Tutorial in the AXIOM site. Thanks, Chatra -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1526) Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException
[ http://issues.apache.org/jira/browse/AXIS2-1526?page=comments#action_12445145 ] Ali Sadik Kumlali commented on AXIS2-1526: -- Mentioned file resides under org/apache/ws/security/policy of the wss4j-SNAPSHOT.jar but it looks it up in org/apache/ws/secpolicy. Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException --- Key: AXIS2-1526 URL: http://issues.apache.org/jira/browse/AXIS2-1526 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: modules Affects Versions: 1.1 Environment: Windows XP, JDK 1.4.2_12, Latest Axis2 Nightly (27 Oct 2006), Latest Rampart Nightly (26 Oct 2006) Reporter: Ali Sadik Kumlali I've followed the README.TXT both under 'samples' and 'basic' directories and got the following exception at the first sample (service.01). You may follow the steps here: C:\axis2-rampart\samplesset AXIS2_HOME=c:/axis2 C:\axis2-rampart\samplesant Buildfile: build.xml check.dependency: setup: [copy] Copying 6 files to C:\axis2\lib [copy] Copying 2 files to C:\axis2\repository\modules BUILD SUCCESSFUL Total time: 1 second C:\axis2-rampart\samplescd basic C:\axis2-rampart\samples\basicant service.01 Buildfile: build.xml check.dependency: service.01: [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp\META-INF [javac] Compiling 1 source file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp\META-INF [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [jar] Building jar: C:\axis2-rampart\samples\basic\build\service_repositor ies\sample01\services\sample01.aar [delete] Deleting directory C:\axis2-rampart\samples\basic\build\temp [java] [SimpleHTTPServer] Starting [java] [SimpleHTTPServer] Using the Axis2 Repository C:\axis2-rampart\sampl es\basic\build\service_repositories\sample01 [java] [SimpleHTTPServer] Listening on port 8080 [java] Oct 27, 2006 1:59:32 PM org.apache.axis2.deployment.DeploymentEngine doDeploy [java] INFO: Deploying module : addressing-1.1 [java] Oct 27, 2006 1:59:33 PM org.apache.axis2.transport.http.SimpleHTTPSe rver main [java] SEVERE: Error starting SimpleHTTPServer [java] java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyExc eption [java] at java.lang.Class.getDeclaredConstructors0(Native Method) [java] at java.lang.Class.privateGetDeclaredConstructors(Class.java:161 8) [java] at java.lang.Class.getConstructor0(Class.java:1930) [java] at java.lang.Class.newInstance0(Class.java:278) [java] at java.lang.Class.newInstance(Class.java:261) [java] at org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils. java:69) [java] at org.apache.axis2.deployment.DeploymentEngine.addNewModule(Dep loymentEngine.java:326) [java] at org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deploym entEngine.java:598) [java] at org.apache.axis2.deployment.RepositoryListener.init(Repositor yListener.java:160) [java] at org.apache.axis2.deployment.RepositoryListener.init(Reposit oryListener.java:53) [java] at org.apache.axis2.deployment.DeploymentEngine.loadRepository(D eploymentEngine.java:104) [java] at org.apache.axis2.deployment.FileSystemConfigurator.getAxisCon figuration(FileSystemConfigurator.java:116) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContext(ConfigurationContextFactory.java:61) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContextFromFileSystem(ConfigurationContextFactory.java:180) [java] at org.apache.axis2.transport.http.SimpleHTTPServer.main(SimpleH TTPServer.java:157) [java] [SimpleHTTPServer] Shutting down BUILD SUCCESSFUL Total time: 3 seconds C:\axis2-rampart\samples\basic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To
[jira] Created: (AXIS2-1528) No command options available to generate both sync and async clients using the command line version of the tool
No command options available to generate both sync and async clients using the command line version of the tool --- Key: AXIS2-1528 URL: http://issues.apache.org/jira/browse/AXIS2-1528 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Environment: Windows XP, jdk1.5.0_08 Reporter: Evanthika Amarasiri There are no commands given to generate both sync and async clients through the command line version of the tool. But options are available to create async and sync code seperately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1526) Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException
[ http://issues.apache.org/jira/browse/AXIS2-1526?page=all ] Ruchith Udayanga Fernando resolved AXIS2-1526. -- Fix Version/s: 1.1 Resolution: Fixed This issue is fixed in in the latest 1_1 svn[1]. We don't use org.apache.ws.security.policy.* stuff anymore. Instead we use org.apache.ws.secpolicy.* Thanks, Ruchith [1] http://svn.apache.org/viewvc?view=revrev=468272 Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException --- Key: AXIS2-1526 URL: http://issues.apache.org/jira/browse/AXIS2-1526 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: modules Affects Versions: 1.1 Environment: Windows XP, JDK 1.4.2_12, Latest Axis2 Nightly (27 Oct 2006), Latest Rampart Nightly (26 Oct 2006) Reporter: Ali Sadik Kumlali Fix For: 1.1 I've followed the README.TXT both under 'samples' and 'basic' directories and got the following exception at the first sample (service.01). You may follow the steps here: C:\axis2-rampart\samplesset AXIS2_HOME=c:/axis2 C:\axis2-rampart\samplesant Buildfile: build.xml check.dependency: setup: [copy] Copying 6 files to C:\axis2\lib [copy] Copying 2 files to C:\axis2\repository\modules BUILD SUCCESSFUL Total time: 1 second C:\axis2-rampart\samplescd basic C:\axis2-rampart\samples\basicant service.01 Buildfile: build.xml check.dependency: service.01: [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp\META-INF [javac] Compiling 1 source file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp\META-INF [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [jar] Building jar: C:\axis2-rampart\samples\basic\build\service_repositor ies\sample01\services\sample01.aar [delete] Deleting directory C:\axis2-rampart\samples\basic\build\temp [java] [SimpleHTTPServer] Starting [java] [SimpleHTTPServer] Using the Axis2 Repository C:\axis2-rampart\sampl es\basic\build\service_repositories\sample01 [java] [SimpleHTTPServer] Listening on port 8080 [java] Oct 27, 2006 1:59:32 PM org.apache.axis2.deployment.DeploymentEngine doDeploy [java] INFO: Deploying module : addressing-1.1 [java] Oct 27, 2006 1:59:33 PM org.apache.axis2.transport.http.SimpleHTTPSe rver main [java] SEVERE: Error starting SimpleHTTPServer [java] java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyExc eption [java] at java.lang.Class.getDeclaredConstructors0(Native Method) [java] at java.lang.Class.privateGetDeclaredConstructors(Class.java:161 8) [java] at java.lang.Class.getConstructor0(Class.java:1930) [java] at java.lang.Class.newInstance0(Class.java:278) [java] at java.lang.Class.newInstance(Class.java:261) [java] at org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils. java:69) [java] at org.apache.axis2.deployment.DeploymentEngine.addNewModule(Dep loymentEngine.java:326) [java] at org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deploym entEngine.java:598) [java] at org.apache.axis2.deployment.RepositoryListener.init(Repositor yListener.java:160) [java] at org.apache.axis2.deployment.RepositoryListener.init(Reposit oryListener.java:53) [java] at org.apache.axis2.deployment.DeploymentEngine.loadRepository(D eploymentEngine.java:104) [java] at org.apache.axis2.deployment.FileSystemConfigurator.getAxisCon figuration(FileSystemConfigurator.java:116) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContext(ConfigurationContextFactory.java:61) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContextFromFileSystem(ConfigurationContextFactory.java:180) [java] at org.apache.axis2.transport.http.SimpleHTTPServer.main(SimpleH TTPServer.java:157) [java] [SimpleHTTPServer] Shutting down BUILD SUCCESSFUL Total time: 3 seconds C:\axis2-rampart\samples\basic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on
Axis2 - Error in WSDL2Java generating classes for the OTA specification
Hello, When I try to generate the java classes from an WSDL that uses the schema files from the OTA specification the script WSDL2Java fails. I am using the adb binding (actually, it fails in all bindings that I tried). I am using axis 2 1.1 snapshot from today (October 27th) and jsdk 1.5.0. The messages that WSDL2Java generates are: Retrieving schema at 'xsd/OTA_CancelRQ.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CommonTypes.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'xsd/OTA_CancelRS.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength0to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength1to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StreetNmbrType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}FreeTextType missing! It says that the type StringLength0to128 is missing, but it is defined in the file SimpleTypes.xsl. Any hint if this is a bug or I am doing something wrong? The same wsdl and xsl files work fine in axis1. If you want I can provide you with the wsdl and schema files that I am using. Thank you very much for any help provided. Regards, Manuel Valladares - - Jose Manuel Valladares Pernas - [EMAIL PROTECTED] - [EMAIL PROTECTED] - __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1529) curently create-project.xml ant build file does not generate eclipse plugin
[ http://issues.apache.org/jira/browse/AXIS2-1529?page=all ] Eran Chinthaka resolved AXIS2-1529. --- Fix Version/s: 1.1 Resolution: Fixed Fixed in r468352. Thanks Sandakith. curently create-project.xml ant build file does not generate eclipse plugin --- Key: AXIS2-1529 URL: http://issues.apache.org/jira/browse/AXIS2-1529 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: ide plugins Affects Versions: 1.1 Environment: windows,linux eclipse3.1.*/eclipse3.2 Reporter: Lahiru Sandakith Fix For: 1.1 Attachments: eclipse-servise-arcihve-plugin-27102006-patch.txt currently eclipse plugins can not be generated thorough a build script. The create-project.xml only generate the eclipse workspace project. Then by loading the project through the eclipse workbench, it can be exported as the working eclipse plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1525) Axis2 admin console crashers when rampart-1.0.mar is deployed as a module
[ http://issues.apache.org/jira/browse/AXIS2-1525?page=all ] Ruchith Udayanga Fernando resolved AXIS2-1525. -- Resolution: Invalid Rampart 1.0 will NOT work with Axis2-1.1 Axis2 admin console crashers when rampart-1.0.mar is deployed as a module - Key: AXIS2-1525 URL: http://issues.apache.org/jira/browse/AXIS2-1525 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: 1.1 Environment: jdk 1.4.2, Tomcat 4.1.30 Reporter: Keith Godwin Chapman Axis2 admin console crashers when rampart-1.0.mar is deployed as a module. When the server is restarted after deploying this module cannot acces the admin console. The following is the error diaplayed on the browser org.apache.jasper.JasperException at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822) at org.apache.jsp.index_jsp._jspService(index_jsp.java:64) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2422) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:163) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:199) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:700) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:584) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534)
[jira] Commented: (AXIS2-935) Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open
[ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12445182 ] Davanum Srinivas commented on AXIS2-935: If they use REUSE_HTTP_CLIENT, they can access the HTTPClient and tweak whatever they need to tweak. So let's leave it alone. thanks, dims Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open - Key: AXIS2-935 URL: http://issues.apache.org/jira/browse/AXIS2-935 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.0 Environment: Weblogic 8.1.2, Solaris 8 (dont ask!) Reporter: Jeff Peterson Assigned To: Deepal Jayasinghe Priority: Blocker Attachments: AXIS2-935.patch It appears that org.apache.axis2.transport.http.SOAPOverHTTPSender does not properly cleanup the http post connection after payload has been sent. The symptoms of this problem show up in `netstat` as literally hundreds of connections in the CLOSE_WAIT state. On a busy server this can cause the application to report exceptions with the message Too many open files. I looked in the source code for axis2 1.0 and discovered that in SOAPOverHTTPSender.java the releaseConnection() is never called on the postMethod variable. This seems to be a likely candidate for the source of the issue. See SOAPOverHTTPSender.java:97-118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-935) Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open
[ http://issues.apache.org/jira/browse/AXIS2-935?page=all ] Davanum Srinivas updated AXIS2-935: --- Priority: Critical (was: Blocker) Not a blocker. Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open - Key: AXIS2-935 URL: http://issues.apache.org/jira/browse/AXIS2-935 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.0 Environment: Weblogic 8.1.2, Solaris 8 (dont ask!) Reporter: Jeff Peterson Assigned To: Deepal Jayasinghe Priority: Critical Attachments: AXIS2-935.patch It appears that org.apache.axis2.transport.http.SOAPOverHTTPSender does not properly cleanup the http post connection after payload has been sent. The symptoms of this problem show up in `netstat` as literally hundreds of connections in the CLOSE_WAIT state. On a busy server this can cause the application to report exceptions with the message Too many open files. I looked in the source code for axis2 1.0 and discovered that in SOAPOverHTTPSender.java the releaseConnection() is never called on the postMethod variable. This seems to be a likely candidate for the source of the issue. See SOAPOverHTTPSender.java:97-118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1488) Axis2 WAR distribution needs to start listed transports on initialization (similarly to the standalone dist)
[ http://issues.apache.org/jira/browse/AXIS2-1488?page=all ] Davanum Srinivas updated AXIS2-1488: Priority: Critical (was: Blocker) Not a blocker as mentioned in prev comment. Axis2 WAR distribution needs to start listed transports on initialization (similarly to the standalone dist) Key: AXIS2-1488 URL: http://issues.apache.org/jira/browse/AXIS2-1488 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.1 Reporter: Asankha C. Perera Assigned To: Deepal Jayasinghe Priority: Critical Axis2 WAR distribution needs to start listed transports on initialization (similarly to the standalone dist) Axis2 has been recently updated to start all listed transports during initialization. This has been done already for the standalone dist, but needs to be fixed for WAR. Else, other transports such as JMS etc cannot be started/used -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 - Error in WSDL2Java generating classes for the OTA specification
Please create a JIRA issue and then upload a zip of your wsdl and xsd's. thanks, dims On 10/27/06, Jose Manuel Valladares Pernas [EMAIL PROTECTED] wrote: Hello, When I try to generate the java classes from an WSDL that uses the schema files from the OTA specification the script WSDL2Java fails. I am using the adb binding (actually, it fails in all bindings that I tried). I am using axis 2 1.1 snapshot from today (October 27th) and jsdk 1.5.0. The messages that WSDL2Java generates are: Retrieving schema at 'xsd/OTA_CancelRQ.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CommonTypes.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'xsd/OTA_CancelRS.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength0to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength1to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StreetNmbrType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}FreeTextType missing! It says that the type StringLength0to128 is missing, but it is defined in the file SimpleTypes.xsl. Any hint if this is a bug or I am doing something wrong? The same wsdl and xsl files work fine in axis1. If you want I can provide you with the wsdl and schema files that I am using. Thank you very much for any help provided. Regards, Manuel Valladares - - Jose Manuel Valladares Pernas - [EMAIL PROTECTED] - [EMAIL PROTECTED] - __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] Some thoughts on all public methods being exposed as operations
Hi Deepal, Thanks for the comments.And my apologies for not commenting on this when it was first discussed. did you mean setOperationContext() ?Axis2 automatically ignore them , and will not display at the ?wsdlPls explain this a bit , if you mean smt else. By getters and setters what I meant was something like (not axis2 specific methods) publicvoid setGreetingService(GreetingService srv) and public GreetingService getGreetingService() For example if youWebService has some properties to be set for example by spring, then it is going to be a real pain point to exclude them. Think abt the scenario where you have service impl class with 50 publicmethods , in that case user has to go and write operation elementsforall the public methods (what ever he want to expose) Exactly , this is my point. If your Web Service defines 50 operations in the same class, then that's poor programing practice and bad design. In most use cases,you may want to have 3 or 4 public methods exposed as operations and in the same class you may have about 10-15 public methods (mostly getters/setters) that u want to hide. So this will make a person do more work, bcos now instead of explicitly defining 5 operations in the services.xml, we now have to define 10-15 excludes. This method is not going to help a good programmers life. Instead we are encouraging lazy people to write humongous, monolithic pieces of code that is hard to maintain. Why are we encouraging a culture of bad programming practices around axis2 Regards, Rajith On 10/26/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Rajith;Rajith Attapattu wrote: Hi All, I noticed that all public methods in your web services is exposed as operations. I would really like to know the reasons for doing so and why this is a better approach than the previous way of only exposing what you want.I think you need to go and read mail archives :) , we discussed this in the mailing list and after that we decided to do so. What I don't like about this approach is that we need to exclude operations and you end up writing more in your services.xml.I think you can fix your problem by writing service impl class carefully , I mean you can write your service impl class to have publics method aswell as private method (and remember to have public method only if youwant to expose that). So Axis2 will expose your public method and it will not touch private method.Think abt the scenario where you have service impl class with 50 publicmethods , in that case user has to go and write operation elementsforall the public methods (what ever he want to expose) in the services.xml, but now he does not want to do that since we have thatnicefeature. Here are some pain points 1. If you have getters and setters i(lets say for dependency injection), this becomes a reall PIA, as I have to exclude them all. did you mean setOperationContext() ?Axis2 automatically ignore them , and will not display at the ?wsdlPls explain this a bit , if you mean smt else. 2. If u need to do anything operation specific like use Aysnc MR, instead of a Synch receiver or if u need some module engaged at operation level you anyhow have to define that in the services.xmlnot for all the operation , only the operation that you need to override. So this really doesn't add much value in my opinion and can be a real PIA if I have a bunch of getters/setters. I would like to see some comments on this. Regards, Rajith-To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1530) Error in WSDL2Java generating classes for the OTA specification
Error in WSDL2Java generating classes for the OTA specification --- Key: AXIS2-1530 URL: http://issues.apache.org/jira/browse/AXIS2-1530 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: nightly Environment: axis2 1.1 snapshot October 27 2006 jsdk 1.5.0_06-b05 openSuse 10.1 Reporter: Jose Manuel Valladares Pernas Generating the java classes from an WSDL that uses the schema files from the OTA specification the script WSDL2Java fails. I am using the adb binding (actually, it fails in all bindings that I tried). I am using axis 2 1.1 snapshot from today (October 27th) and jsdk 1.5.0. The messages that WSDL2Java generates are: Retrieving schema at 'xsd/OTA_CancelRQ.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CommonTypes.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'xsd/OTA_CancelRS.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength0to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength1to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StreetNmbrType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}FreeTextType missing! I am providing the WSDL and schema files I used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1530) Error in WSDL2Java generating classes for the OTA specification
[ http://issues.apache.org/jira/browse/AXIS2-1530?page=all ] Jose Manuel Valladares Pernas updated AXIS2-1530: - Attachment: files.ZIP Wsdl and xsd files to generate the java classes Error in WSDL2Java generating classes for the OTA specification --- Key: AXIS2-1530 URL: http://issues.apache.org/jira/browse/AXIS2-1530 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: nightly Environment: axis2 1.1 snapshot October 27 2006 jsdk 1.5.0_06-b05 openSuse 10.1 Reporter: Jose Manuel Valladares Pernas Attachments: files.ZIP Generating the java classes from an WSDL that uses the schema files from the OTA specification the script WSDL2Java fails. I am using the adb binding (actually, it fails in all bindings that I tried). I am using axis 2 1.1 snapshot from today (October 27th) and jsdk 1.5.0. The messages that WSDL2Java generates are: Retrieving schema at 'xsd/OTA_CancelRQ.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CommonTypes.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_AirCommonTypes.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRQ.xsd'. Retrieving schema at 'xsd/OTA_CancelRS.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/'. Retrieving schema at 'OTA_CommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_AirCommonTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Retrieving schema at 'OTA_SimpleTypes.xsd', relative to 'file:/home/jmanuel/src/MiraiOTA/axis_2/OTA_Cancel/xsd/OTA_CancelRS.xsd'. Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength0to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StringLength1to128 missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}StreetNmbrType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}LocationType missing! Oct 27, 2006 2:31:42 PM org.apache.axis2.schema.SchemaCompiler findClassName WARNING: Type {http://www.opentravel.org/OTA/2003/05}FreeTextType missing! I am providing the WSDL and schema files I used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-935) Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open
[ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12445196 ] Oleg Kalnichevski commented on AXIS2-935: - Deepal, The re-use of HttpClient instance(s) is in fact highly recommended. So, you should probably keep the option. When REUSE_HTTP_CLIENT is set to false, always shut down the connection manager associated with the HttpClient instances before dereferencing it MultiThreadedHttpConnectionManager connManager = (MultiThreadedHttpConnectionManager) httpclient.getHttpConnectionManager(); connManager.shutdown(); This should take care of the problem. Oleg Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open - Key: AXIS2-935 URL: http://issues.apache.org/jira/browse/AXIS2-935 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.0 Environment: Weblogic 8.1.2, Solaris 8 (dont ask!) Reporter: Jeff Peterson Assigned To: Deepal Jayasinghe Priority: Critical Attachments: AXIS2-935.patch It appears that org.apache.axis2.transport.http.SOAPOverHTTPSender does not properly cleanup the http post connection after payload has been sent. The symptoms of this problem show up in `netstat` as literally hundreds of connections in the CLOSE_WAIT state. On a busy server this can cause the application to report exceptions with the message Too many open files. I looked in the source code for axis2 1.0 and discovered that in SOAPOverHTTPSender.java the releaseConnection() is never called on the postMethod variable. This seems to be a likely candidate for the source of the issue. See SOAPOverHTTPSender.java:97-118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Which App server do you use?
For a while ago, I deployed (or extracted?) on JONAS. IIRC, it worked without problem. Ali Sadik Kumlali - Original Message From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org axis-user@ws.apache.org Cc: Axis developer list axis-dev@ws.apache.org Sent: Friday, October 27, 2006 5:00:50 PM Subject: [Axis2] Which App server do you use? Folks, We got Axis2 war working under Weblogic 9.2 and Websphere 6.1 (non-exploded) yesterday. For weblogic, you need to add a weblogic.xml with the prefer-web-inf stuff. In websphere, you need to set the class loader order to Classes loaded with parent class loader first and the WAR class loader policy to Class loader for each WAR file in application. Getting back the $subject? Which App server do you use? So that we can focus testing... thanks, dims -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Shouldn't the war be included in the release?
search for build.xml, run ant in that directory... axis2.sh is a helperExample i use it for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java to run w2j :) it basically sets up the classpath and then you can invoke any class. Another use is to run say a client class that needs axis2 classpath set up. -- dims On 10/27/06, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I just built axis2 from the latest svn the way I always do: maven clean release That way I get the std-bin and the war. This however no longer produces the war. I thought we agreed that we are going to include the war in the release? Secondly, I remember some talk about a script to generate the war. I found axis2.sh in the bin directory. Its not clear what this does either from the comments or the source. When I run it I get a confused jvm: /axis2.sh Using AXIS2_HOME: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT Using JAVA_HOME: /usr/local/jdk1.5.0_08 Usage: java [-options] class [args...] So I see no new way in the faq to generate the war, and I see nowhere in xdocs anything on axis2.sh . What am I missing? Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1526) Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException
[ http://issues.apache.org/jira/browse/AXIS2-1526?page=comments#action_12445203 ] Ali Sadik Kumlali commented on AXIS2-1526: -- Yep :) It works with the SVN. Thanks. Rampart - Samples - service.01 - java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyException --- Key: AXIS2-1526 URL: http://issues.apache.org/jira/browse/AXIS2-1526 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: modules Affects Versions: 1.1 Environment: Windows XP, JDK 1.4.2_12, Latest Axis2 Nightly (27 Oct 2006), Latest Rampart Nightly (26 Oct 2006) Reporter: Ali Sadik Kumlali Fix For: 1.1 I've followed the README.TXT both under 'samples' and 'basic' directories and got the following exception at the first sample (service.01). You may follow the steps here: C:\axis2-rampart\samplesset AXIS2_HOME=c:/axis2 C:\axis2-rampart\samplesant Buildfile: build.xml check.dependency: setup: [copy] Copying 6 files to C:\axis2\lib [copy] Copying 2 files to C:\axis2\repository\modules BUILD SUCCESSFUL Total time: 1 second C:\axis2-rampart\samplescd basic C:\axis2-rampart\samples\basicant service.01 Buildfile: build.xml check.dependency: service.01: [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\service_repos itories\sample01\modules [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp [mkdir] Created dir: C:\axis2-rampart\samples\basic\build\temp\META-INF [javac] Compiling 1 source file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp\META-INF [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [copy] Copying 1 file to C:\axis2-rampart\samples\basic\build\temp [jar] Building jar: C:\axis2-rampart\samples\basic\build\service_repositor ies\sample01\services\sample01.aar [delete] Deleting directory C:\axis2-rampart\samples\basic\build\temp [java] [SimpleHTTPServer] Starting [java] [SimpleHTTPServer] Using the Axis2 Repository C:\axis2-rampart\sampl es\basic\build\service_repositories\sample01 [java] [SimpleHTTPServer] Listening on port 8080 [java] Oct 27, 2006 1:59:32 PM org.apache.axis2.deployment.DeploymentEngine doDeploy [java] INFO: Deploying module : addressing-1.1 [java] Oct 27, 2006 1:59:33 PM org.apache.axis2.transport.http.SimpleHTTPSe rver main [java] SEVERE: Error starting SimpleHTTPServer [java] java.lang.NoClassDefFoundError: org/apache/ws/secpolicy/WSSPolicyExc eption [java] at java.lang.Class.getDeclaredConstructors0(Native Method) [java] at java.lang.Class.privateGetDeclaredConstructors(Class.java:161 8) [java] at java.lang.Class.getConstructor0(Class.java:1930) [java] at java.lang.Class.newInstance0(Class.java:278) [java] at java.lang.Class.newInstance(Class.java:261) [java] at org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils. java:69) [java] at org.apache.axis2.deployment.DeploymentEngine.addNewModule(Dep loymentEngine.java:326) [java] at org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deploym entEngine.java:598) [java] at org.apache.axis2.deployment.RepositoryListener.init(Repositor yListener.java:160) [java] at org.apache.axis2.deployment.RepositoryListener.init(Reposit oryListener.java:53) [java] at org.apache.axis2.deployment.DeploymentEngine.loadRepository(D eploymentEngine.java:104) [java] at org.apache.axis2.deployment.FileSystemConfigurator.getAxisCon figuration(FileSystemConfigurator.java:116) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContext(ConfigurationContextFactory.java:61) [java] at org.apache.axis2.context.ConfigurationContextFactory.createCo nfigurationContextFromFileSystem(ConfigurationContextFactory.java:180) [java] at org.apache.axis2.transport.http.SimpleHTTPServer.main(SimpleH TTPServer.java:157) [java] [SimpleHTTPServer] Shutting down BUILD SUCCESSFUL Total time: 3 seconds C:\axis2-rampart\samples\basic -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
Re: [Axis2] Shouldn't the war be included in the release?
Hmm, I found the build.xml which has a default task of creating the war, and I get: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp ant Buildfile: build.xml init: prepare.repo: BUILD FAILED /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp/build.xml:31: The pathconvert type doesn't support the nested flattenmapper element. I'm using ant 1.6.2 As for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java ... kool, although my trusty old ant task calling WSDLJava directly still works so that's good enough for me. Anyways ... why isn't the war in the release? I thought we agreed to that. And I see no docs for axis2.sh . Robert On 10/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote: search for build.xml, run ant in that directory... axis2.sh is a helperExample i use it for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java to run w2j :) it basically sets up the classpath and then you can invoke any class. Another use is to run say a client class that needs axis2 classpath set up. -- dims On 10/27/06, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I just built axis2 from the latest svn the way I always do: maven clean release That way I get the std-bin and the war. This however no longer produces the war. I thought we agreed that we are going to include the war in the release? Secondly, I remember some talk about a script to generate the war. I found axis2.sh in the bin directory. Its not clear what this does either from the comments or the source. When I run it I get a confused jvm: /axis2.sh Using AXIS2_HOME: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT Using JAVA_HOME: /usr/local/jdk1.5.0_08 Usage: java [-options] class [args...] So I see no new way in the faq to generate the war, and I see nowhere in xdocs anything on axis2.sh . What am I missing? Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1520) Enhancements to DBC (Description Builder Composite) processing to add tests and increased functionality
[ http://issues.apache.org/jira/browse/AXIS2-1520?page=all ] Jeff Barrett resolved AXIS2-1520. - Resolution: Fixed Patches committed to revision 468396. Thanks, Roy! Enhancements to DBC (Description Builder Composite) processing to add tests and increased functionality Key: AXIS2-1520 URL: http://issues.apache.org/jira/browse/AXIS2-1520 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Roy A. Wood Jr. Priority: Minor Attachments: DBCPatch1026_src.txt, DBCPatch1026_tests.txt This is an improvement to the DBC processing software . It provides more tests, as well as, increased functionality -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-1520) Enhancements to DBC (Description Builder Composite) processing to add tests and increased functionality
[ http://issues.apache.org/jira/browse/AXIS2-1520?page=all ] Jeff Barrett closed AXIS2-1520. --- Enhancements to DBC (Description Builder Composite) processing to add tests and increased functionality Key: AXIS2-1520 URL: http://issues.apache.org/jira/browse/AXIS2-1520 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Reporter: Roy A. Wood Jr. Priority: Minor Attachments: DBCPatch1026_src.txt, DBCPatch1026_tests.txt This is an improvement to the DBC processing software . It provides more tests, as well as, increased functionality -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1531) Trying to migrate webservice using WSDL2JAVA
Trying to migrate webservice using WSDL2JAVA Key: AXIS2-1531 URL: http://issues.apache.org/jira/browse/AXIS2-1531 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: caroline First of all i'm a bit new to axis 2 and axis in general so i apologise in advance. I'm trying to migrate an existing functioning websercive(written with axis 1.1) to axis 2 using WSDL2JAVA. However i'm encountering problems with the following node :- complexType name=ArrayOf_tns1_PDPItemBean It is generating an interface called ArrayOfTns1PDPItemBean. I t is also generating a package _116._10._20._10.cpssoap.services.cpsgateway; (my namescpace is http://10.20.10.116:9000/cpssoap/services/CPSGateway). I realise there must be some problem with the way the wsdl is being interpreted , however the wsdl had been generated by axis1.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Please unscubscribe me for sometime
Please unscubscribe me for sometime -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2006 8:33 PM To: axis-dev@ws.apache.org; [EMAIL PROTECTED] Subject: Re: [Axis2] Shouldn't the war be included in the release? Hmm, I found the build.xml which has a default task of creating the war, and I get: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp ant Buildfile: build.xml init: prepare.repo: BUILD FAILED /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp/build.xml:31: The pathconvert type doesn't support the nested flattenmapper element. I'm using ant 1.6.2 As for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java ... kool, although my trusty old ant task calling WSDLJava directly still works so that's good enough for me. Anyways ... why isn't the war in the release? I thought we agreed to that. And I see no docs for axis2.sh . Robert On 10/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote: search for build.xml, run ant in that directory... axis2.sh is a helperExample i use it for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java to run w2j :) it basically sets up the classpath and then you can invoke any class. Another use is to run say a client class that needs axis2 classpath set up. -- dims On 10/27/06, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I just built axis2 from the latest svn the way I always do: maven clean release That way I get the std-bin and the war. This however no longer produces the war. I thought we agreed that we are going to include the war in the release? Secondly, I remember some talk about a script to generate the war. I found axis2.sh in the bin directory. Its not clear what this does either from the comments or the source. When I run it I get a confused jvm: /axis2.sh Using AXIS2_HOME: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT Using JAVA_HOME: /usr/local/jdk1.5.0_08 Usage: java [-options] class [args...] So I see no new way in the faq to generate the war, and I see nowhere in xdocs anything on axis2.sh . What am I missing? Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Shouldn't the war be included in the release?
please upgrade to 1.6.5. i remember seeing a discussion on documenting that requirement. war will be in RC2. - dims On 10/27/06, robert lazarski [EMAIL PROTECTED] wrote: Hmm, I found the build.xml which has a default task of creating the war, and I get: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp ant Buildfile: build.xml init: prepare.repo: BUILD FAILED /home/iksrazal/nigel/axis2-1.1-SNAPSHOT/webapp/build.xml:31: The pathconvert type doesn't support the nested flattenmapper element. I'm using ant 1.6.2 As for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java ... kool, although my trusty old ant task calling WSDLJava directly still works so that's good enough for me. Anyways ... why isn't the war in the release? I thought we agreed to that. And I see no docs for axis2.sh . Robert On 10/27/06, Davanum Srinivas [EMAIL PROTECTED] wrote: search for build.xml, run ant in that directory... axis2.sh is a helperExample i use it for ./axis2.sh org.apache.axis2.wsdl.WSDL2Java to run w2j :) it basically sets up the classpath and then you can invoke any class. Another use is to run say a client class that needs axis2 classpath set up. -- dims On 10/27/06, robert lazarski [EMAIL PROTECTED] wrote: Hi all, I just built axis2 from the latest svn the way I always do: maven clean release That way I get the std-bin and the war. This however no longer produces the war. I thought we agreed that we are going to include the war in the release? Secondly, I remember some talk about a script to generate the war. I found axis2.sh in the bin directory. Its not clear what this does either from the comments or the source. When I run it I get a confused jvm: /axis2.sh Using AXIS2_HOME: /home/iksrazal/nigel/axis2-1.1-SNAPSHOT Using JAVA_HOME: /usr/local/jdk1.5.0_08 Usage: java [-options] class [args...] So I see no new way in the faq to generate the war, and I see nowhere in xdocs anything on axis2.sh . What am I missing? Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-935) Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open
[ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12445214 ] Jeff Peterson commented on AXIS2-935: - I'm pretty sure that I did not have REUSE_HTTP_CLIENT set, unless its the default. I still think this is a garbage collection/cleanup related issue. Even if you dont intend to reuse the HttpClient, the act of creating a HttpClient object also creates a new HttpConnectionManager for that client instance. The sockets associated with the HttpConnectionManager do not get cleaned up until garbage connection is triggered. So, in the non-reuse case, lots of http client objects are created (one per request). Each one has its own HttpConnectionManager, which is never explicitly cleaned up. Instead, it is up to the container to garbage collect them and free their sockets. Unfortunately, if the container is slow to get around to garbage collection, this can leave a lot of sockets open. Connections are not properly released causing them to stick in the CLOSE_WAIT state and cause Too many files open - Key: AXIS2-935 URL: http://issues.apache.org/jira/browse/AXIS2-935 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.0 Environment: Weblogic 8.1.2, Solaris 8 (dont ask!) Reporter: Jeff Peterson Assigned To: Deepal Jayasinghe Priority: Critical Attachments: AXIS2-935.patch It appears that org.apache.axis2.transport.http.SOAPOverHTTPSender does not properly cleanup the http post connection after payload has been sent. The symptoms of this problem show up in `netstat` as literally hundreds of connections in the CLOSE_WAIT state. On a busy server this can cause the application to report exceptions with the message Too many open files. I looked in the source code for axis2 1.0 and discovered that in SOAPOverHTTPSender.java the releaseConnection() is never called on the postMethod variable. This seems to be a likely candidate for the source of the issue. See SOAPOverHTTPSender.java:97-118 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1513) ADB codegen problem when server send null values
[ http://issues.apache.org/jira/browse/AXIS2-1513?page=all ] Davanum Srinivas resolved AXIS2-1513. - Resolution: Fixed Amila, Could you please check my fix? http://svn.apache.org/viewvc?view=revrevision=468444 Deepal, Thanks! -- dims ADB codegen problem when server send null values Key: AXIS2-1513 URL: http://issues.apache.org/jira/browse/AXIS2-1513 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe Priority: Blocker Attachments: Man.java, MyBeanImpl.java, MyService.java I generate a pojo using attached java classes , and then code gen using adb. And invoke the service. Then I got the following exception. java.lang.RuntimeException: Unexpected subelement man at org.apache.ws.axis2.MyServiceStub.fromOM(MyServiceStub.java:3408) at org.apache.ws.axis2.MyServiceStub.SayHello(MyServiceStub.java:333) at org.apache.ws.axis2.MyCleint.main(MyCleint.java:32) As I can understand the problem is in following code in generated stub; while (!reader.isStartElement() !reader.isEndElement()) reader.next(); and I think it should change to while (!reader.isStartElement()) reader.next(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1519) empty arrays are not parsed correctly by Axis client
[ http://issues.apache.org/jira/browse/AXIS2-1519?page=comments#action_12445224 ] Amila Chinthaka Suriarachchi commented on AXIS2-1519: - hi shahar, can you please attach you skelton which produces this output soap message? As I can see here is your xsd element for response, xs:element name=getServiceConnectionsResponse xs:complexType xs:sequence xs:element maxOccurs=unbounded name=return nillable=true type=ns0:ServiceConnection/ /xs:sequence /xs:complexType /xs:element Since minOccurs is *not zero* it can not produce such an output as your output soap xml. It should be some thing like this if the GetServiceConnectionsResponse object is empty. ns1:getServiceConnectionsResponse xmlns:ns1=http://axis2.runtime.server.applinx.sabratec.com/xsd;ns1:return xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true //ns1:getServiceConnectionsResponse empty arrays are not parsed correctly by Axis client Key: AXIS2-1519 URL: http://issues.apache.org/jira/browse/AXIS2-1519 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: om Environment: Windows XP Pro Reporter: Shahar Kedar Attachments: inSoapMessage.xml, outSoapMessage.xml, ServiceManager.wsdl My webservice sometimes returns an empty array of some object (which is properly declared in the WSDL). In those cases, the Axis2 generated client fails to parse to SOAP message. I'm getting the following error message: java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement getServiceSessionsResponse at org.apache.ws.axis2.SessionManagerStub.fromOM(SessionManagerStub.java:8176) at org.apache.ws.axis2.SessionManagerStub.getServiceSessions(SessionManagerStub.java:269) at org.apache.ws.axis2.SessionManagerTest.testgetServiceSessions(SessionManagerTest.java:33) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.RuntimeException: Unexpected subelement getServiceSessionsResponse at org.apache.ws.axis2.SessionManagerStub$GetServiceSessionsResponse$Factory.parse(SessionManagerStub.java:4937) at org.apache.ws.axis2.SessionManagerStub.fromOM(SessionManagerStub.java:8086) ... 20 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1532) Remove the minimal distribution from releases
Remove the minimal distribution from releases - Key: AXIS2-1532 URL: http://issues.apache.org/jira/browse/AXIS2-1532 Project: Apache Axis 2.0 (Axis2) Issue Type: Task Components: samples, build,site Reporter: Eran Chinthaka Assigned To: Eran Chinthaka Remove the minimal distribution from the releases as per http://marc.theaimsgroup.com/?l=axis-devm=116183350630084w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] kill the minimum distro
JIRA created for this http://issues.apache.org/jira/browse/AXIS2-1532. Changed the script to removed the minimal distro from release (revision 468469). Task done. -- Chinthaka Eran Chinthaka wrote: I just looked at the minimal distribution and all it contains are the jar files from adb, kernel and java2wsdl modules and there dependencies. , which can be easily downloaded from maven. +1 for removing minimal distro. Thilina Gunarathne wrote: Hi all, +1 from me to kill the min-dist.. If anybody is using or has a really blocking need thay can reply to this thread.. So let's wait for couple of days to see if there are any objections... Thanks, Thilina On 10/26/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Sanjiva Weerawarana wrote: I'd like to propose that we kill the minimum distro. We started that apparently for folks like Synapse to embed but realistically they're pulling jars off the maven repo anyway. And in any case, if someone knows the guts of Axis2 then choosing the right jars is easier (and we can document it). +1 for removing min-dist from the release. My motivation is to reduce complexity to users: you download either binary or the source distro and you're good to go. Oh yeah there's that (mostly useless ;-)) WAR distro too. but we conclude to have WAR in th release :) Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
[jira] Commented: (AXIS2-1531) Trying to migrate webservice using WSDL2JAVA
[ http://issues.apache.org/jira/browse/AXIS2-1531?page=comments#action_12445227 ] Amila Chinthaka Suriarachchi commented on AXIS2-1531: - the package name is determine by the namespace. if you can see org.apache.axis2.util.URLProcessor class you can see the logic. Run a small test as follows, you will get that package name String packageNmae = URLProcessor.makePackageName(http://10.20.10.116:9000/cpssoap/services/CPSGateway;); System.out.println(Package Name == + packageNmae); Trying to migrate webservice using WSDL2JAVA Key: AXIS2-1531 URL: http://issues.apache.org/jira/browse/AXIS2-1531 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: caroline First of all i'm a bit new to axis 2 and axis in general so i apologise in advance. I'm trying to migrate an existing functioning websercive(written with axis 1.1) to axis 2 using WSDL2JAVA. However i'm encountering problems with the following node :- complexType name=ArrayOf_tns1_PDPItemBean It is generating an interface called ArrayOfTns1PDPItemBean. I t is also generating a package _116._10._20._10.cpssoap.services.cpsgateway; (my namescpace is http://10.20.10.116:9000/cpssoap/services/CPSGateway). I realise there must be some problem with the way the wsdl is being interpreted , however the wsdl had been generated by axis1.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1532) Remove the minimal distribution from releases
[ http://issues.apache.org/jira/browse/AXIS2-1532?page=all ] Eran Chinthaka resolved AXIS2-1532. --- Fix Version/s: 1.1 Resolution: Fixed Fixed in revision 468469. Remove the minimal distribution from releases - Key: AXIS2-1532 URL: http://issues.apache.org/jira/browse/AXIS2-1532 Project: Apache Axis 2.0 (Axis2) Issue Type: Task Components: samples, build,site Reporter: Eran Chinthaka Assigned To: Eran Chinthaka Fix For: 1.1 Remove the minimal distribution from the releases as per http://marc.theaimsgroup.com/?l=axis-devm=116183350630084w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Which App server do you use?
For making sure, just tried it again and saw no problem with JOnAS. Here are the details: - jonas4.3.3-tomcat5.0.30, JRE 1.5.0_01, Win XP Professional - axis2.war from Axis2 1.1 RC1 (10 Oct 2006) - No expansion. Just droped the war under JONAS_HOME\webapps. - Deployed using web admin console. - JOnAS expanded the war into JONAS_HOME\work\webapps\jonas\ - Called http://localhost:9000/axis2 and walked through the pages. - Saw no problem. Regards, Ali Sadik Kumlali - Original Message From: Ali Sadik Kumlali [EMAIL PROTECTED] To: axis-dev@ws.apache.org Sent: Friday, October 27, 2006 5:39:02 PM Subject: Re: [Axis2] Which App server do you use? For a while ago, I deployed (or extracted?) on JONAS. IIRC, it worked without problem. Ali Sadik Kumlali - Original Message From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org axis-user@ws.apache.org Cc: Axis developer list axis-dev@ws.apache.org Sent: Friday, October 27, 2006 5:00:50 PM Subject: [Axis2] Which App server do you use? Folks, We got Axis2 war working under Weblogic 9.2 and Websphere 6.1 (non-exploded) yesterday. For weblogic, you need to add a weblogic.xml with the prefer-web-inf stuff. In websphere, you need to set the class loader order to Classes loaded with parent class loader first and the WAR class loader policy to Class loader for each WAR file in application. Getting back the $subject? Which App server do you use? So that we can focus testing... thanks, dims -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1110) Java 2 Security
[ http://issues.apache.org/jira/browse/AXIS2-1110?page=all ] Ming Cheung updated AXIS2-1110: --- Attachment: patch_02.txt I have verified the following patch, which can be used for both Apache AXIS2 and IBM CS, with Linux, Windows, JDK 1.4, and 1.5. And the test results are good. Within this new patch, it fixes 3 things: a) inappropriated letter size for classpath. b) classfile syntax work for both Windows and Linux and alike. c) moved snapshots dependency jars from Kernel module's to etc directory. Java 2 Security --- Key: AXIS2-1110 URL: http://issues.apache.org/jira/browse/AXIS2-1110 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: kernel Environment: Supporting Axis2 runs inside of an environment with Java 2 Security enabled Reporter: Ming Cheung Assigned To: Rich Scheuerle Attachments: patch.txt, patch_02.txt We need a feature which can provide us fine-grained access control to grant privileges when the codes needed, and to have code operate with the minimum necessray privileges. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1533) FaultCode is not set in the AxisFault object
FaultCode is not set in the AxisFault object Key: AXIS2-1533 URL: http://issues.apache.org/jira/browse/AXIS2-1533 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Environment: java 1.4.2, tomcat 4, Axis 2 rc1 1.1 Reporter: Todd Doolittle Priority: Blocker I set this as a blocker because it's going to be a big problem for our organization. We need to be able to see the fault codes coming back from existing services. I understand if this is not considered a blocker by others. I generated a service from WSDL using java2wsdl. The skeleton simply does this... throw new AxisFault(This is a fault message, This is the fault code); I then generated a client using wsdl2javva that catches the fault and does this... catch(AxisFault f) { System.out.println(Fault = + f); System.out.println(Fault Reason = + f.getReason()); System.out.println(Fault Code = + f.getFaultCode()); } The output from the client looks like this... Fault = org.apache.axis2.AxisFault: This is a fault message Fault Reason = null Fault Code = null The faultcode element is definately in the XML. When I hit the service with a non-axis2 client I get the fault code. But the axis 2 client fault.getFaultCode() always returns NULL.The XML from the service looks like this... HTTP/1.1 500 Internal Server Error Set-Cookie: JSESSIONID=1CCF3E951167E01316F12E7EC314837B; Path=/axis2 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Fri, 27 Oct 2006 18:44:06 GMT Server: Apache-Coyote/1.1 Connection: close f12 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body soapenv:Fault xmlns:axis2=http://ws.apache.org/namespaces/axis2; faultcodeaxis2:This is the fault code/faultcode faultstringThis is a fault message/faultstring detail Exception org.apache.axis2.AxisFault: This is a fault message#xd; at org.tempuri.DbpocSkeleton.Dbinfo(DbpocSkeleton.java:26)#xd; at org.tempuri.DbpocMessageReceiverInOut.invokeBusinessLogic(DbpocMessageReceiverInOut.java:53)#xd; at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)#xd; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)#xd; at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324)#xd; at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:203)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:716)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)#xd; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200)#xd; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146)#xd; at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209)#xd; at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)#xd; at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)#xd; at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)#xd; at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)#xd; at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)#xd; at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)#xd; at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)#xd; at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)#xd; at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)#xd; at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)#xd; at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118)#xd; at
[jira] Resolved: (AXIS2-1140) Axis2 AAR Plugin should allow dependencies to be added to the lib directory in the aar file
[ http://issues.apache.org/jira/browse/AXIS2-1140?page=all ] Jochen Wiedmann resolved AXIS2-1140. Fix Version/s: 1.1 Resolution: Fixed Assignee: Jochen Wiedmann Applied to the 1.1 branch. Axis2 AAR Plugin should allow dependencies to be added to the lib directory in the aar file --- Key: AXIS2-1140 URL: http://issues.apache.org/jira/browse/AXIS2-1140 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Environment: All Reporter: John Pfeifer Assigned To: Jochen Wiedmann Fix For: 1.1 Attachments: AbstractAarMojo.java Axis2 AAR files are supposed to include their dependencies in the lib file of the .aar archive. When the .aar file is deployed, any libraries in the lib directory of the aar file are included in the classpath for the web service. This feature should probably be optional since some users may not want to include the dependencies inside the .aar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1534) Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app
Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app - Key: AXIS2-1534 URL: http://issues.apache.org/jira/browse/AXIS2-1534 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Mike Rheinheimer Attachments: patch.txt Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app. If a user put in a bad endpoint address, for example, that exception would get absorbed, causing a later NPE to be thrown. This is now fixed, along with a new testcase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1534) Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app
[ http://issues.apache.org/jira/browse/AXIS2-1534?page=all ] Mike Rheinheimer updated AXIS2-1534: Attachment: patch.txt Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app - Key: AXIS2-1534 URL: http://issues.apache.org/jira/browse/AXIS2-1534 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Mike Rheinheimer Attachments: patch.txt Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app. If a user put in a bad endpoint address, for example, that exception would get absorbed, causing a later NPE to be thrown. This is now fixed, along with a new testcase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1534) Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app
[ http://issues.apache.org/jira/browse/AXIS2-1534?page=comments#action_12445266 ] Mike Rheinheimer commented on AXIS2-1534: - Sorry, got the wrong component, can't find where to change it. Should be jaxws. Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app - Key: AXIS2-1534 URL: http://issues.apache.org/jira/browse/AXIS2-1534 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Mike Rheinheimer Attachments: patch.txt Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app. If a user put in a bad endpoint address, for example, that exception would get absorbed, causing a later NPE to be thrown. This is now fixed, along with a new testcase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1535) Some of Rampart samples throws exception
Some of Rampart samples throws exception Key: AXIS2-1535 URL: http://issues.apache.org/jira/browse/AXIS2-1535 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: 1.1 Environment: WinXP Professional, JRE 1.5.0_01, Axis2 1.1 SVN (rev: 468353) Reporter: Ali Sadik Kumlali Priority: Minor I ran across some problems while running Basic samples of Rampart and will attach a patch to get rid of them. Details -- 1) SimpleService of sample03 still uses setOperationContext() which is not supported anymore due to [1]. 2) xalan-2.7.0.jar is needed for sample04 (and *maybe* for subsequent samples), if JDK 1.5 is used. [1] http://issues.apache.org/jira/browse/AXIS2-1224 Regards, Ali Sadik Kumlali -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1534) Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app
[ http://issues.apache.org/jira/browse/AXIS2-1534?page=all ] Nick Gallardo updated AXIS2-1534: - Component/s: jaxws Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app - Key: AXIS2-1534 URL: http://issues.apache.org/jira/browse/AXIS2-1534 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Mike Rheinheimer Attachments: patch.txt Fault processing bug fix. Exceptions thrown on client now thrown properly back to client app. If a user put in a bad endpoint address, for example, that exception would get absorbed, causing a later NPE to be thrown. This is now fixed, along with a new testcase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-1536) JAX-WS Attachment Implementation Update
[ http://issues.apache.org/jira/browse/AXIS2-1536?page=all ] Rich Scheuerle reassigned AXIS2-1536: - Assignee: Rich Scheuerle JAX-WS Attachment Implementation Update --- Key: AXIS2-1536 URL: http://issues.apache.org/jira/browse/AXIS2-1536 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assigned To: Rich Scheuerle JAX-WS Attachment Update Summary of changes: * Increased the functionality of the JAX-WS Attachment object (added MimeHeader support) * Consolidated the code that puts a JAX-WS Message on an Axis2 MessageContext * Consolidated the code that builds a JAX-WS Message from a Axis2 MessageContext * Added code to convert SAAJ AttachmentPart - JAX-WS Attachment * Changes to the SoapMessageProvider test to anticipate Attachment changes...the new test is currently disabled. * Scrubbed jaxws code to remove System.out.println The code is a foundation for swaref support through jaxws -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1536) JAX-WS Attachment Implementation Update
JAX-WS Attachment Implementation Update --- Key: AXIS2-1536 URL: http://issues.apache.org/jira/browse/AXIS2-1536 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle JAX-WS Attachment Update Summary of changes: * Increased the functionality of the JAX-WS Attachment object (added MimeHeader support) * Consolidated the code that puts a JAX-WS Message on an Axis2 MessageContext * Consolidated the code that builds a JAX-WS Message from a Axis2 MessageContext * Added code to convert SAAJ AttachmentPart - JAX-WS Attachment * Changes to the SoapMessageProvider test to anticipate Attachment changes...the new test is currently disabled. * Scrubbed jaxws code to remove System.out.println The code is a foundation for swaref support through jaxws -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1536) JAX-WS Attachment Implementation Update
[ http://issues.apache.org/jira/browse/AXIS2-1536?page=all ] Rich Scheuerle updated AXIS2-1536: -- Attachment: patch.txt JAX-WS Attachment Implementation Update --- Key: AXIS2-1536 URL: http://issues.apache.org/jira/browse/AXIS2-1536 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assigned To: Rich Scheuerle Attachments: patch.txt JAX-WS Attachment Update Summary of changes: * Increased the functionality of the JAX-WS Attachment object (added MimeHeader support) * Consolidated the code that puts a JAX-WS Message on an Axis2 MessageContext * Consolidated the code that builds a JAX-WS Message from a Axis2 MessageContext * Added code to convert SAAJ AttachmentPart - JAX-WS Attachment * Changes to the SoapMessageProvider test to anticipate Attachment changes...the new test is currently disabled. * Scrubbed jaxws code to remove System.out.println The code is a foundation for swaref support through jaxws -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] 1.1 Release note
Hi all, I started drafting the release note for Axis2 1.1 release in here [1].. Please go ahead and review it.. Feel free to edit it.. Specially the last what's new part.. I've just put together some things came to my mind.. Will try to polish it up over the next couple of days.. Thanks, Thilina [1] http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.1/release_note -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1533) FaultCode is not set in the AxisFault object
[ http://issues.apache.org/jira/browse/AXIS2-1533?page=all ] Davanum Srinivas resolved AXIS2-1533. - Resolution: Fixed Whew! managed to sneak in a fix for this one. svn revision 468620 thanks, dims FaultCode is not set in the AxisFault object Key: AXIS2-1533 URL: http://issues.apache.org/jira/browse/AXIS2-1533 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: client-api Affects Versions: 1.1 Environment: java 1.4.2, tomcat 4, Axis 2 rc1 1.1 Reporter: Todd Doolittle Priority: Blocker I set this as a blocker because it's going to be a big problem for our organization. We need to be able to see the fault codes coming back from existing services. I understand if this is not considered a blocker by others. I generated a service from WSDL using java2wsdl. The skeleton simply does this... throw new AxisFault(This is a fault message, This is the fault code); I then generated a client using wsdl2javva that catches the fault and does this... catch(AxisFault f) { System.out.println(Fault = + f); System.out.println(Fault Reason = + f.getReason()); System.out.println(Fault Code = + f.getFaultCode()); } The output from the client looks like this... Fault = org.apache.axis2.AxisFault: This is a fault message Fault Reason = null Fault Code = null The faultcode element is definately in the XML. When I hit the service with a non-axis2 client I get the fault code. But the axis 2 client fault.getFaultCode() always returns NULL.The XML from the service looks like this... HTTP/1.1 500 Internal Server Error Set-Cookie: JSESSIONID=1CCF3E951167E01316F12E7EC314837B; Path=/axis2 Content-Type: text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Fri, 27 Oct 2006 18:44:06 GMT Server: Apache-Coyote/1.1 Connection: close f12 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body soapenv:Fault xmlns:axis2=http://ws.apache.org/namespaces/axis2; faultcodeaxis2:This is the fault code/faultcode faultstringThis is a fault message/faultstring detail Exception org.apache.axis2.AxisFault: This is a fault message#xd; at org.tempuri.DbpocSkeleton.Dbinfo(DbpocSkeleton.java:26)#xd; at org.tempuri.DbpocMessageReceiverInOut.invokeBusinessLogic(DbpocMessageReceiverInOut.java:53)#xd; at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)#xd; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)#xd; at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324)#xd; at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:203)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:716)#xd; at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)#xd; at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200)#xd; at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146)#xd; at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209)#xd; at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)#xd; at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)#xd; at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)#xd; at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)#xd; at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)#xd; at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)#xd; at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)#xd; at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)#xd; at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)#xd; at
[jira] Resolved: (AXIS2-1535) Some of Rampart samples throws exception
[ http://issues.apache.org/jira/browse/AXIS2-1535?page=all ] Ruchith Udayanga Fernando resolved AXIS2-1535. -- Resolution: Fixed Thanks for the patch ... I realized that I had made a mistake by adding authentication logic into the service. This is because the authentication happens at the callback handler. Please see : org.apache.rampart.samples.sample03.PWCBHandler Note the pwcb.getUsage() == WSPasswordCallback.USERNAME_TOKEN_UNKNOWN case. I removed the extra auth logic from the service and add your changes to the README.txt Some of Rampart samples throws exception Key: AXIS2-1535 URL: http://issues.apache.org/jira/browse/AXIS2-1535 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: 1.1 Environment: WinXP Professional, JRE 1.5.0_01, Axis2 1.1 SVN (rev: 468353) Reporter: Ali Sadik Kumlali Priority: Minor Attachments: samples_security_patch.txt I ran across some problems while running Basic samples of Rampart and will attach a patch to get rid of them. Details -- 1) SimpleService of sample03 still uses setOperationContext() which is not supported anymore due to [1]. 2) xalan-2.7.0.jar is needed for sample04 (and *maybe* for subsequent samples), if JDK 1.5 is used. [1] http://issues.apache.org/jira/browse/AXIS2-1224 Regards, Ali Sadik Kumlali -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]