[jira] Commented: (AXIS2-937) WSDL2Java not generating parameters for stub methods
[ http://issues.apache.org/jira/browse/AXIS2-937?page=comments#action_12434599 ] William Ferguson commented on AXIS2-937: Yes the #schedule method is a void oepration, but it should take a single paramater of type ReportConfig. WSDL2Java from the 1.0 release correctly generates the method, WSDL2Java from the nightlies does not, it generates a method that takes NO parameters. .. > WSDL2Java not generating parameters for stub methods > > > Key: AXIS2-937 > URL: http://issues.apache.org/jira/browse/AXIS2-937 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: William Ferguson > Assigned To: Deepal Jayasinghe >Priority: Blocker > Attachments: axis2-937.zip, JasperService.wsdl, JasperServiceStub.java > > > WSDL2Java from the nightly snapshot of 23-jul-2006 generates the > stub/interface, but tyhe methods on the stub don't have any parameters when > they should. The stub is created fine using WSDL2Java from Axis2-1.0 > WSDL2Java params: > > > > > > > > > > > I will attach the WSDL in question -- 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-1094) Throw NullPointerException when invoking a service and return a customer JavaBean.
[ http://issues.apache.org/jira/browse/AXIS2-1094?page=all ] Deepal Jayasinghe resolved AXIS2-1094. -- Resolution: Fixed problem is fixed in the current SVN no NPE at the server side. > Throw NullPointerException when invoking a service and return a customer > JavaBean. > -- > > Key: AXIS2-1094 > URL: http://issues.apache.org/jira/browse/AXIS2-1094 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.0 > Environment: WinXP Pro. Java 5 (1.5.0_07), Axis2 (1.0) >Reporter: Eric Chow > Assigned To: Deepal Jayasinghe >Priority: Critical > Attachments: testservice.zip > > > I tried to use Axis2-1.0 to create a simple echo web service that to return a > simple Java bean. But was not success and throws NullPointerException. > I tried to return a String, it was very well without any error. > All the codes were generated by Wsdl2Java. I tried to use ADB and Xmlbeans, > but also failed. The following is the exception when I run the client in > eClipse-3.2. The attachment is the sources, AAR and WSDL, please check. > log4j:WARN No appenders could be found for logger > (org.apache.axiom.om.impl.builder.StAXOMBuilder). > log4j:WARN Please initialize the log4j system properly. > Testing1234... > Exception in thread "main" org.apache.axis2.AxisFault: > java.lang.NullPointerException > at > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:287) > at test.gen.EchoserviceStub.echo(EchoserviceStub.java:244) > at test.client.Client.main(Client.java:39) > Caused by: java.lang.Exception: org.apache.axis2.AxisFault: > java.lang.NullPointerException; nested exception is: > org.apache.axiom.om.OMException: java.lang.NullPointerException > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) > at > org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:136) > at > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284) > at > org.apache.axis2.transport.http.HTTPWorker.processRequest(HTTPWorker.java:255) > at > org.apache.axis2.transport.http.server.SimpleConnectionThread.run(SimpleConnectionThread.java:92) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.apache.axiom.om.OMException: java.lang.NullPointerException > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206) > at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:298) > at > org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:584) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:118) > at > org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:240) > at > org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:197) > at > org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:71) > at > org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:130) > ... 8 more > Caused by: java.lang.NullPointerException > at > org.apache.axis2.databinding.utils.reader.WrappingXMLStreamReader.getEventType(WrappingXMLStreamReader.java:141) > at > org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.processProperties(ADBXMLStreamReaderImpl.java:964) > at > org.apache.axis2.databinding.utils.reader.ADBXMLStreamReaderImpl.next(ADBXMLStreamReaderImpl.java:807) > at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:68) > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:123) > ... 15 more > at org.apache.axis2.AxisFault.(AxisFault.java:159) > ... 3 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] Resolved: (AXIS2-937) WSDL2Java not generating parameters for stub methods
[ http://issues.apache.org/jira/browse/AXIS2-937?page=all ] Deepal Jayasinghe resolved AXIS2-937. - Resolution: Fixed In the case of "scheduleReport " according to the wsdl which should be a void operation. So the generated method signatures is correct , and I tested other method as well and all of them have correct method signature according to the wsdl. > WSDL2Java not generating parameters for stub methods > > > Key: AXIS2-937 > URL: http://issues.apache.org/jira/browse/AXIS2-937 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Reporter: William Ferguson > Assigned To: Deepal Jayasinghe >Priority: Blocker > Attachments: axis2-937.zip, JasperService.wsdl, JasperServiceStub.java > > > WSDL2Java from the nightly snapshot of 23-jul-2006 generates the > stub/interface, but tyhe methods on the stub don't have any parameters when > they should. The stub is created fine using WSDL2Java from Axis2-1.0 > WSDL2Java params: > > > > > > > > > > > I will attach the WSDL in question -- 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: Is axis2-om-M1.jar needed in webapps/axis2/WEB-INF/lib ??
can you please use Axis2 1.0 release. Thanks Deepal >>I depooyed a service arr file, and go errors below. >> >>It appeared that it was complaining about not finding OMElement. >> >>I seared and found this class in axis2-om-M1.jar, so I put it in >> webapps\axis2\WEB-INF\lib >> >>Then I restarted the web server, but still have the same problem. >> >>Any ideas what's causing this? >> >>Thanks, >>cyw >> >>_ERRORS >>This Web axisService has deployment faults >>Error: java.lang.NoClassDefFoundError: org/apache/axis2/om/OMElement at >>java.lang.Class.getDeclaredMethods0(Native Method) at >>java.lang.Class.privateGetDeclaredMethods(Unknown Source) at >>java.lang.Class.privateGetPublicMethods(Unknown Source) at >>java.lang.Class.getMethods(Unknown Source) at >>org.apache.ws.java2wsdl.bytecode.MethodTable.loadMethods(MethodTable.java:40 >>) at org.apache.ws.java2wsdl.bytecode.MethodTable.(MethodTable.java:30) at >>org.apache.ws.java2wsdl.SchemaGenerator.(SchemaGenerator.java:71) at >>org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:209) at >> >> >> >>- >>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: Is axis2-om-M1.jar needed in webapps/axis2/WEB-INF/lib ??
I am using axis2 1.0. downloaded from: http://ws.apache.org/axis2/download/1_0/download.cgi The unpacked war has the following jars in webapps/axis2/WEB-INF/lib directory. Thanks, cyw drwxrwx---+ 7 Administrators SYSTEM 0 Sep 13 21:24 ../ -rwxrwx---+ 1 Administrators SYSTEM 110688 May 5 00:33 XmlSchema-1.0.2.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 XmlSchema-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 248639 May 5 00:33 annogen-0.1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 annongen-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 248221 May 5 00:33 axiom-api-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 axiom-api-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 axiom-dom-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 105647 May 5 00:33 axiom-impl-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 axiom-impl-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 112808 May 5 00:33 axis2-adb-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 axis2-adb-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 189558 May 5 00:33 axis2-codegen-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 41165 May 5 00:33 axis2-java2wsdl-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM4065 May 5 00:33 axis2-jibx-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 63 May 5 00:33 axis2-kernel-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 26368 May 5 00:33 axis2-soapmonitor-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM9284 May 5 00:33 axis2-xmlbeans-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 329586 May 5 00:33 backport-util-concurrent-2.1.jar* -rwxrwx---+ 1 Administrators SYSTEM2295 May 5 00:33 backport-util-concurrent-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 46725 May 5 00:33 commons-codec-1.3.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 commons-codec-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 22379 May 5 00:33 commons-fileupload-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 commons-fileupload-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 279383 May 5 00:33 commons-httpclient-3.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 commons-httpclient-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 38015 May 5 00:33 commons-logging-1.0.4.jar* -rwxrwx---+ 1 Administrators SYSTEM 11359 May 5 00:33 commons-logging-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 31528 May 5 00:33 geronimo-spec-activation-1.0.2-rc4.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 geronimo-spec-activation-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 112700 May 5 00:33 geronimo-spec-javamail-1.3.1-rc5.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 geronimo-spec-javamail-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 30838 May 5 00:33 geronimo-spec-jms-1.1-rc4.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 geronimo-spec-jms-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 231706 May 5 00:33 jaxen-1.1-beta-8.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 jaxen-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 71161 May 5 00:33 jibx-run-1.1-beta3.jar* -rwxrwx---+ 1 Administrators SYSTEM1489 May 5 00:33 jibx-run-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 358180 May 5 00:33 log4j-1.2.13.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 log4j-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 44356 May 5 00:33 neethi-1.0.1.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 neethi-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 26396 May 5 00:33 stax-api-1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 stax-api-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 127124 May 5 00:33 wsdl4j-1.5.2.jar* -rwxrwx---+ 1 Administrators SYSTEM 11560 May 5 00:33 wsdl4j-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 11359 May 5 00:33 wstx-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 436827 May 5 00:33 wstx-asl-2.9.3.jar* -rwxrwx---+ 1 Administrators SYSTEM 2637587 May 5 00:33 xbean-2.1.0.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 xerces-LICENSE.txt* -rwxrwx---+ 1 Administrators SYSTEM 1203860 May 5 00:33 xercesImpl-2.7.1.jar* -rwxrwx---+ 1 Administrators SYSTEM 194205 May 5 00:33 xml-apis-1.3.02.jar* -rwxrwx---+ 1 Administrators SYSTEM 11358 May 5 00:33 xml-apis-LICENSE.txt* soft-eng6:/cygdrive/c/prog/tomcat/webapps/axis2/WEB-INF/lib$ -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 11:32 PM To: axis-dev@ws.apache.org Subject: Re: Is axis2-om-M1.jar needed in webapps/axis2/WEB-INF/lib ?? Hi ; can you please you Axis2 1.0 realse. Thanks Deepal CYW wrote: >I depooyed a service arr file, and go errors below. > >It appeared that it was complaining about not finding OMElement. > >I seared and found this class in axis2
[jira] Commented: (AXIS2-1129) Doubled wrapper elements around XMLBeans-generated XML
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434588 ]
Davanum Srinivas commented on AXIS2-1129:
-
FWIW, with this change (http://svn.apache.org/viewvc?view=rev&revision=443228),
your original wsdl/xsd will work fine.
> Doubled wrapper elements around XMLBeans-generated XML
> --
>
> Key: AXIS2-1129
> URL: http://issues.apache.org/jira/browse/AXIS2-1129
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: om, core, databinding, client-api, wsdl
>Affects Versions: 1.0
>Reporter: Derek Foster
>Priority: Blocker
>
> I recently noticed a big problem in how Axis2 generates XML for XMLBeans
> objects. It appears to be creating the wrapper element around
> an XMLBean twice, thus generating erroneous XML for a SOAP message. This
> appears to be a big problem that would affect a lot of web services, and is
> making it impossible for my company to use Axis2 to talk to our server.
> This error was found in the latest nightly build (September 8), but has
> apparently been around for some time.
> I have a particular WSDL, as follows:
>
> targetNamespace="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c";
>xmlns:F="http://www.dummy-temp-address";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns="http://schemas.xmlsoap.org/wsdl/";>
>
> http://www.c-corp.com/wsdl/2004-10-01/F";>
> http://www.dummy-temp-address";
> schemaLocation="F.xsd"/>
>
>
>
> http://www.c-corp.com/wsdl/2004-10-01/c";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> F Port Type
>
>
>
>
>
>
>
> F Soap Binding
>transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
> use="literal"/>
>
>
>
>
>
>
>
>
>
>
>
> F Web Service
>
> location="http://localhost:8080/axis/services/FService"/>
>
>
>
> My WSDL references the following XML schema:
>
> http://www.dummy-temp-address";
>xmlns="http://www.dummy-temp-address";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation";
>elementFormDefault="unqualified"
>attributeFormDefault="unqualified"
>version="DRAFT">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> After running WSDL2Java to generate the appropriate classes, I am using the
> following code to generate and transmit a client message to my SOAP server:
>protected ReturnDocument executeTest (
> final String targetEndpoint,
> final CLoginDocument login,
> final CPasswordDocument password )
> throws Exception
>{
> final FServiceStub service = new FServiceStub( null, targetEndpoint );
> final Options options = service._getServiceClient().getOptions();
> options.setProperty(
> org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE );
> service._getServiceClient().setOptions( options );
> final FullDocument full = Full.Factory.newInstance();
> full.setFull( getSituation() );
> return service.acceptFEvent( full, login, password );
>}
>private Full getSituation ()
> throws XmlException
>{
> return Full.Factory.parse(
> " http://www.dummy-temp-address\";>\n" +
> " \n" +
> ... and so forth: see output for the rest of this string ...
> " \n" +
> " \n" );
>}
> When I execute the above code, I get the following message sent to my server:
> POST /axis2/services/FService HTTP/1.1
> SOAPAction: acceptFEventAction
> User-Agent: Axis2
> Host: 127.0.0.1
> Content-Length: 8785
> Content-Type: text/xml; charset=UTF-8
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> xmlns="http://www.c-corp.com/wsdl/2004-10-01/c";>admin xmlns="http://www.dummy-temp-address";>
>
>
> QSenderOrganizationID
> QSenderCenterID
>
> 1
> 435
>
> 20040625
> 201225
> -0400
>
>
> 20040625
> 221222
> -0
Re: Is axis2-om-M1.jar needed in webapps/axis2/WEB-INF/lib ??
Hi ; can you please you Axis2 1.0 realse. Thanks Deepal CYW wrote: >I depooyed a service arr file, and go errors below. > >It appeared that it was complaining about not finding OMElement. > >I seared and found this class in axis2-om-M1.jar, so I put it in > webapps\axis2\WEB-INF\lib > >Then I restarted the web server, but still have the same problem. > >Any ideas what's causing this? > >Thanks, >cyw > >_ERRORS >This Web axisService has deployment faults >Error: java.lang.NoClassDefFoundError: org/apache/axis2/om/OMElement at >java.lang.Class.getDeclaredMethods0(Native Method) at >java.lang.Class.privateGetDeclaredMethods(Unknown Source) at >java.lang.Class.privateGetPublicMethods(Unknown Source) at >java.lang.Class.getMethods(Unknown Source) at >org.apache.ws.java2wsdl.bytecode.MethodTable.loadMethods(MethodTable.java:40 >) at org.apache.ws.java2wsdl.bytecode.MethodTable.(MethodTable.java:30) at >org.apache.ws.java2wsdl.SchemaGenerator.(SchemaGenerator.java:71) at >org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:209) at > > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2][Vote] Create a branch for the Axis2 1.1 release
Sanjiva Weerawarana wrote: > On Wed, 2006-09-13 at 10:55 -0700, Bill Nagy wrote: >> Hi all, >> >> I would like to propose that we create a branch in Subversion for the >> 1.1 release (and all future releases) so that we can continue >> development on the main trunk while the release is occurring. This >> would also enable us to make point fixes to each release without >> requiring that users adopt a whole bag of new features (i.e. the next >> release) in order to get bug fixes. (I'm not saying that we will >> backport all bug fixes, just that having the release branch would enable >> us to do so.) > > +1 from me but can we do that a bit closer to the release? Its easier to > not have to merge too much stuff .. +1 to Sanjiva's comment. I hope we don't want to make the life harder for the people who are working hard for the release, by an effort to make the life easier (is it?) to the rest. Merging is, at least theorotically, a great idea and a concept. But when conflicts are coming, practically its a nightmare. And as Bill suggested, we can *not* do quick releases after minor fixes. The release process of Axis2 is becoming problematic due to the dependencies to other projects. So you can not decide at one point, at least now, and release an Axis2 version. Simple example for you to understand is releasing Axis2 with SNAPSHOTs. Hope everyone who involved during past releases can remember the pain we had when once we released Axis2 with a SNAPSHOT. Please understand that I'm not opposing Bill's idea. But I know the pain we are/were going thru whenever we are/were releasing. -- Chinthaka > > Sanjiva. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > signature.asc Description: OpenPGP digital signature
[jira] Created: (AXIS2-1150) ADB does not handle elementFormDefault correctly
ADB does not handle elementFormDefault correctly Key: AXIS2-1150 URL: http://issues.apache.org/jira/browse/AXIS2-1150 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe Priority: Blocker I generate stub for the WSDL which has elementFormDefault=false , but when I send the request I found that it send the qualified element. I think this is a bug and need to fix before 1.1 FYI : when code gen for the same wsdl using xmlbeans it works fine -- 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-663) WSDL2Java: allow user to specify separate destination folders for src and resources
[ http://issues.apache.org/jira/browse/AXIS2-663?page=comments#action_12434584 ] Derek Foster commented on AXIS2-663: I have run into this problem too. It is really frustrating. Suppose I have services Service1 and Service2. They both include the same XML schema file, Schema1, as well as some other schemas that are individual to each service. Now I run WSDL2Java on each, and put the output in Output1 and Output2 respectively. Now I have two copies of Schema1's files, including generated .java files: one in Output1 and one in Output2. This causes my IDE and compiler to complain that there are two duplicate copies of each of the Java classes in Schema1 if I try to include these both into the same project or compilation unit. On the other hand, if I try to have the output generated into the same directory for both services, the Java classes work OK. (Identical source files overwrite each other when WSDL2Java runs, but that is fine). However, the .wsdl and .xsb and build.xml and so forth files overwrite each other in some cases, so when I try to use the Java files for one service, it may crash because it was expecting to find it's own files, but is finding the other services' instead. As a workaround, I tried using the namespace2package option to remap each schema into its own directory, so that the classes from the two services which share the same schema are placed in different directories and packages. This works... sort of... but it means that if I have a particular element type in the schema named, say, MyElement, that I now have two different classes named MyElement, in different packages, and therefore if I wish to write a utility routine that is shared by both services and which takes a parameter of type MyElement, I can't do it: What was supposed to be one type is now two. The -o option really isn't enough. There really needs to be a way to cause source code for identical schemas in multiple services to be shared (when the same schema is used in multiple services), while allowing the data files to be distinct. > WSDL2Java: allow user to specify separate destination folders for src and > resources > --- > > Key: AXIS2-663 > URL: http://issues.apache.org/jira/browse/AXIS2-663 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: Tools >Affects Versions: 1.0 > Environment: Axis2 1.0 RC5 >Reporter: Thilo Frotscher > Assigned To: Ajith Harshana Ranabahu >Priority: Blocker > > WSDL2Java generates source code, resources (service.xml, wsdl, xsd) and a > build.xml file. > The user can specify a destination folder for all of these files, but they > all go into the same folder. > When generating code for more than one service, you'll generally want to have > the source code for all services in the same src-folder. > That's why you would specify the same destination folder for all services. > However, in this causes the problem that the build.xml files > and the resources for all the services go into the same folder as well and > interfere with each other, or a overwritten respectively. > Therefore, it would be great if the user could specify two separate > destination folders: one for the source code and the second one for > the build file and the resources. Of course, the build files would have to > reflect the new folder structure. > Alternative suggestion: WSDL2Java could do this automatically by introducing > a service-specific folder > under resouces: > /resources/MyService1/service.xml > /resources/MyService1/MyService.wsdl > /resources/MyService1/MyService.xsd > /resources/MyService2/service.xml > /resources/MyService2/MyService.wsdl > /resources/MyService2/MyService.xsd > For the build files a similar solution could be 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][Vote] Create a branch for the Axis2 1.1 release
On Wed, 2006-09-13 at 10:55 -0700, Bill Nagy wrote: > Hi all, > > I would like to propose that we create a branch in Subversion for the > 1.1 release (and all future releases) so that we can continue > development on the main trunk while the release is occurring. This > would also enable us to make point fixes to each release without > requiring that users adopt a whole bag of new features (i.e. the next > release) in order to get bug fixes. (I'm not saying that we will > backport all bug fixes, just that having the release branch would enable > us to do so.) +1 from me but can we do that a bit closer to the release? Its easier to not have to merge too much stuff .. Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error at running jar_wsdl ant task
Right. I need to make two directories, 'lib' and 'dist', manually.Thank you so much, now I can load my aar into Axis >Does C:\research\AXIS2\test3\lib\ exist or does your ant task create >it ? Either way, it needs to be there . >Robert
Is axis2-om-M1.jar needed in webapps/axis2/WEB-INF/lib ??
I depooyed a service arr file, and go errors below. It appeared that it was complaining about not finding OMElement. I seared and found this class in axis2-om-M1.jar, so I put it in webapps\axis2\WEB-INF\lib Then I restarted the web server, but still have the same problem. Any ideas what's causing this? Thanks, cyw _ERRORS This Web axisService has deployment faults Error: java.lang.NoClassDefFoundError: org/apache/axis2/om/OMElement at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.lang.Class.privateGetPublicMethods(Unknown Source) at java.lang.Class.getMethods(Unknown Source) at org.apache.ws.java2wsdl.bytecode.MethodTable.loadMethods(MethodTable.java:40 ) at org.apache.ws.java2wsdl.bytecode.MethodTable.(MethodTable.java:30) at org.apache.ws.java2wsdl.SchemaGenerator.(SchemaGenerator.java:71) at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:209) at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1147) Wrong request message from ADB stub for rpc-lit wsdl
[ http://issues.apache.org/jira/browse/AXIS2-1147?page=all ] Davanum Srinivas resolved AXIS2-1147. - Resolution: Fixed fixed. > Wrong request message from ADB stub for rpc-lit wsdl > > > Key: AXIS2-1147 > URL: http://issues.apache.org/jira/browse/AXIS2-1147 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding >Reporter: Deepal Jayasinghe >Priority: Blocker > > I generated stub for the [1] wsdl , which is of course RPC-LIT wsdl. Then I > try to invoke the service , but I realized it send the wrong request as shown > below (for the method RetChar); > http://tempuri.org/";> > xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/";>97 > > But As I know it should send the following request ; > http://tempuri.org/";> > 97 > > Part element should not be qualified for the RPC-LIT wsdl. > [1] > -http://131.107.72.15/SoapWsdl_BaseDataTypes_XmlFormatter_Service_Indigo/BaseDataTypesRpcLit.svc?wsdl > -- 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-1149) JAXWS Proxy failing while invoking a operation with no parameters.
[ http://issues.apache.org/jira/browse/AXIS2-1149?page=all ] Nikhil Thaker updated AXIS2-1149: - Attachment: JIRA_1149_oneWayWithNoParamFix.txt Here's the fix for this issue. > JAXWS Proxy failing while invoking a operation with no parameters. > -- > > Key: AXIS2-1149 > URL: http://issues.apache.org/jira/browse/AXIS2-1149 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Nikhil Thaker >Priority: Minor > Attachments: JIRA_1149_oneWayWithNoParamFix.txt > > > Following error occured when proxy invoked operation with no parameters. > java.lang.reflect.UndeclaredThrowableException > at $Proxy6.oneWayVoid(Unknown Source) > at > jaxws.proxy.wsfvt.test.DocLitWrappedTest.testOneWayEmpty(DocLitWrappedTest.java:130) > Caused by: org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperException: Internal > Assertion Error. >Number of child objects does not match the number of child names > in wrap() method. > at > org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperToolImpl.wrap(JAXBWrapperToolImpl.java:96) > at > org.apache.axis2.jaxws.client.proxy.DocLitProxyHandler.createDocLitWrappedRequest(DocLitProxyHandler.java:110) > at > org.apache.axis2.jaxws.client.proxy.DocLitProxyHandler.createRequest(DocLitProxyHandler.java:68) > at > org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.InvokeSEIMethod(BaseProxyHandler.java:142) > at > org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.invoke(BaseProxyHandler.java:125) > I will be attaching the fix for this issue -- 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-1149) JAXWS Proxy failing while invoking a operation with no parameters.
JAXWS Proxy failing while invoking a operation with no parameters. -- Key: AXIS2-1149 URL: http://issues.apache.org/jira/browse/AXIS2-1149 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Nikhil Thaker Priority: Minor Following error occured when proxy invoked operation with no parameters. java.lang.reflect.UndeclaredThrowableException at $Proxy6.oneWayVoid(Unknown Source) at jaxws.proxy.wsfvt.test.DocLitWrappedTest.testOneWayEmpty(DocLitWrappedTest.java:130) Caused by: org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperException: Internal Assertion Error. Number of child objects does not match the number of child names in wrap() method. at org.apache.axis2.jaxws.wrapper.impl.JAXBWrapperToolImpl.wrap(JAXBWrapperToolImpl.java:96) at org.apache.axis2.jaxws.client.proxy.DocLitProxyHandler.createDocLitWrappedRequest(DocLitProxyHandler.java:110) at org.apache.axis2.jaxws.client.proxy.DocLitProxyHandler.createRequest(DocLitProxyHandler.java:68) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.InvokeSEIMethod(BaseProxyHandler.java:142) at org.apache.axis2.jaxws.client.proxy.BaseProxyHandler.invoke(BaseProxyHandler.java:125) I will be attaching the fix for this issue -- 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-1129) Doubled wrapper elements around XMLBeans-generated XML
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434548 ]
Davanum Srinivas commented on AXIS2-1129:
-
No, my work around is for another bug that we introduced recently. You are
absolutely right that the changes should have no effect on a correctly written
XML Schema Parser.
Thanks,
dims
> Doubled wrapper elements around XMLBeans-generated XML
> --
>
> Key: AXIS2-1129
> URL: http://issues.apache.org/jira/browse/AXIS2-1129
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: om, core, databinding, client-api, wsdl
>Affects Versions: 1.0
>Reporter: Derek Foster
>Priority: Blocker
>
> I recently noticed a big problem in how Axis2 generates XML for XMLBeans
> objects. It appears to be creating the wrapper element around
> an XMLBean twice, thus generating erroneous XML for a SOAP message. This
> appears to be a big problem that would affect a lot of web services, and is
> making it impossible for my company to use Axis2 to talk to our server.
> This error was found in the latest nightly build (September 8), but has
> apparently been around for some time.
> I have a particular WSDL, as follows:
>
> targetNamespace="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c";
>xmlns:F="http://www.dummy-temp-address";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns="http://schemas.xmlsoap.org/wsdl/";>
>
> http://www.c-corp.com/wsdl/2004-10-01/F";>
> http://www.dummy-temp-address";
> schemaLocation="F.xsd"/>
>
>
>
> http://www.c-corp.com/wsdl/2004-10-01/c";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> F Port Type
>
>
>
>
>
>
>
> F Soap Binding
>transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
> use="literal"/>
>
>
>
>
>
>
>
>
>
>
>
> F Web Service
>
> location="http://localhost:8080/axis/services/FService"/>
>
>
>
> My WSDL references the following XML schema:
>
> http://www.dummy-temp-address";
>xmlns="http://www.dummy-temp-address";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation";
>elementFormDefault="unqualified"
>attributeFormDefault="unqualified"
>version="DRAFT">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> After running WSDL2Java to generate the appropriate classes, I am using the
> following code to generate and transmit a client message to my SOAP server:
>protected ReturnDocument executeTest (
> final String targetEndpoint,
> final CLoginDocument login,
> final CPasswordDocument password )
> throws Exception
>{
> final FServiceStub service = new FServiceStub( null, targetEndpoint );
> final Options options = service._getServiceClient().getOptions();
> options.setProperty(
> org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE );
> service._getServiceClient().setOptions( options );
> final FullDocument full = Full.Factory.newInstance();
> full.setFull( getSituation() );
> return service.acceptFEvent( full, login, password );
>}
>private Full getSituation ()
> throws XmlException
>{
> return Full.Factory.parse(
> " http://www.dummy-temp-address\";>\n" +
> " \n" +
> ... and so forth: see output for the rest of this string ...
> " \n" +
> " \n" );
>}
> When I execute the above code, I get the following message sent to my server:
> POST /axis2/services/FService HTTP/1.1
> SOAPAction: acceptFEventAction
> User-Agent: Axis2
> Host: 127.0.0.1
> Content-Length: 8785
> Content-Type: text/xml; charset=UTF-8
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> xmlns="http://www.c-corp.com/wsdl/2004-10-01/c";>admin xmlns="http://www.dummy-temp-address";>
>
>
> QSenderOrganizationID
> QSenderCenterID
>
> 1
> 435
>
> 20040625
> 201225
> -0400
>
>
[jira] Commented: (AXIS2-919) Unable to print out entire SOAP message: bug in OMElement.serialize()
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12434546 ]
Derek Foster commented on AXIS2-919:
Thank you!
> Unable to print out entire SOAP message: bug in OMElement.serialize()
> -
>
> Key: AXIS2-919
> URL: http://issues.apache.org/jira/browse/AXIS2-919
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core, om
>Affects Versions: 1.0
>Reporter: Derek Foster
> Assigned To: Eran Chinthaka
>Priority: Blocker
>
> I was attempting, inside an XMLBeans-generated service method, to print out
> the entire SOAP message to a log file. Towards that end, I tried to execute
> the following code:
> final StringWriter writer = new StringWriter();
> messageContext.getEnvelope().serialize(writer);
> System.out.println(writer.toString());
> However, I was surprised to get the following exception resulting from this:
> org.apache.axiom.om.OMException
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:266)
> at
> org.apache.axiom.om.impl.traverse.OMChildrenIterator.next(OMChildrenIterator.java:111)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:771)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:177)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:310)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:352)
>...
> The cause of the problem appears to be the fact that the SOAP envelope is a
> top-level XML object. Thus, the item immediately following it is a
> DOCUMENT_END. The OMElementImpl.internalSerialize(XMLStreamWriter, boolean
> cache) method contains the following code:
> Iterator children = this.getChildren();
> while (children.hasNext()) {
> ((OMNodeEx) children.next()).internalSerialize(writer);
> which seems plausible. However, the iterator that is returned is of type
> OMChildrenIterator. Its hasNext method looks like this:
> /**
> * Returns true if the iteration has more elements. (In other
> * words, returns true if next would return an element
> * rather than throwing an exception.)
> *
> * @return Returns true if the iterator has more elements.
> */
> public boolean hasNext() {
> return (currentChild != null);
> }
> but its next() method looks like this:
> /**
> * Returns the next element in the iteration.
> *
> * @return Returns the next element in the iteration.
> * @throws java.util.NoSuchElementException
> * iteration has no more elements.
> */
> public Object next() {
> nextCalled = true;
> removeCalled = false;
> if (hasNext()) {
> lastChild = currentChild;
> currentChild = currentChild.getNextOMSibling();
> return lastChild;
> }
> return null;
> }
> which is a problem, because currentChild.getNextOMSibling() looks like this:
> /**
> * Gets the next sibling. This can be an OMAttribute or OMText or
> * OMELement for others.
> *
> * @throws OMException
> */
> public OMNode getNextOMSibling() throws OMException {
> while (!done) {
> int token = builder.next();
> if (token == XMLStreamConstants.END_DOCUMENT) {
> throw new OMException();
> }
> }
> return super.getNextOMSibling();
> }
> which will under some circumstances throw an OMException, which is not in the
> contract of the iterator's next() method to throw.
> Thus, iterator.hasNext() is returning true, implying that there is a next
> element, but when next() is actually called, the iterator discovers that it
> has reached the end of the document, and that therefore there really is no
> next element. It therefore throws an OMException.
> Firstly, if the next() method is going to be implemented this way, then
> hasNext() should perform enough lookahead on the document to detect that the
> next item in the input stream is indeed a END_DOCUMENT, and should therefore
> return false, since under these circumstances there truly isn't a next
> element (and calling next() would therefore always throw an OMException).
> That way, when the end of the document is hit, the serialize method will
> simply stop and return its results rather than trying to advance past the end
> of the document as it does now.
> Secondly, this OMException really should have some meaningful error text in
> it, such as "Can't call 'next()' on an iterator which is positi
[jira] Commented: (AXIS2-1129) Doubled wrapper elements around XMLBeans-generated XML
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434542 ]
Derek Foster commented on AXIS2-1129:
-
Hmm. I still think it's a real bug (especially considering your workaround
seems to require changes to the XML schema in order to make it work, and that
those changes should have no effect whatsoever on a correctly written XML
schema parser), but I do agree with you that it's an XMLBeans bug, not an Axis2
bug.
I have created XMLBEANS-288 to track this issue further.
Thanks for your time in finding the workaround.
> Doubled wrapper elements around XMLBeans-generated XML
> --
>
> Key: AXIS2-1129
> URL: http://issues.apache.org/jira/browse/AXIS2-1129
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core, om, wsdl, client-api, databinding
>Affects Versions: 1.0
>Reporter: Derek Foster
>Priority: Blocker
>
> I recently noticed a big problem in how Axis2 generates XML for XMLBeans
> objects. It appears to be creating the wrapper element around
> an XMLBean twice, thus generating erroneous XML for a SOAP message. This
> appears to be a big problem that would affect a lot of web services, and is
> making it impossible for my company to use Axis2 to talk to our server.
> This error was found in the latest nightly build (September 8), but has
> apparently been around for some time.
> I have a particular WSDL, as follows:
>
> targetNamespace="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c";
>xmlns:F="http://www.dummy-temp-address";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns="http://schemas.xmlsoap.org/wsdl/";>
>
> http://www.c-corp.com/wsdl/2004-10-01/F";>
> http://www.dummy-temp-address";
> schemaLocation="F.xsd"/>
>
>
>
> http://www.c-corp.com/wsdl/2004-10-01/c";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> F Port Type
>
>
>
>
>
>
>
> F Soap Binding
>transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
> use="literal"/>
>
>
>
>
>
>
>
>
>
>
>
> F Web Service
>
> location="http://localhost:8080/axis/services/FService"/>
>
>
>
> My WSDL references the following XML schema:
>
> http://www.dummy-temp-address";
>xmlns="http://www.dummy-temp-address";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation";
>elementFormDefault="unqualified"
>attributeFormDefault="unqualified"
>version="DRAFT">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> After running WSDL2Java to generate the appropriate classes, I am using the
> following code to generate and transmit a client message to my SOAP server:
>protected ReturnDocument executeTest (
> final String targetEndpoint,
> final CLoginDocument login,
> final CPasswordDocument password )
> throws Exception
>{
> final FServiceStub service = new FServiceStub( null, targetEndpoint );
> final Options options = service._getServiceClient().getOptions();
> options.setProperty(
> org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE );
> service._getServiceClient().setOptions( options );
> final FullDocument full = Full.Factory.newInstance();
> full.setFull( getSituation() );
> return service.acceptFEvent( full, login, password );
>}
>private Full getSituation ()
> throws XmlException
>{
> return Full.Factory.parse(
> " http://www.dummy-temp-address\";>\n" +
> " \n" +
> ... and so forth: see output for the rest of this string ...
> " \n" +
> " \n" );
>}
> When I execute the above code, I get the following message sent to my server:
> POST /axis2/services/FService HTTP/1.1
> SOAPAction: acceptFEventAction
> User-Agent: Axis2
> Host: 127.0.0.1
> Content-Length: 8785
> Content-Type: text/xml; charset=UTF-8
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> xmlns="http://www.c-corp.com/wsdl/2004-10-01/c";>admin xmlns="http://www.dummy-temp-add
Re: error at running jar_wsdl ant task
Does C:\research\AXIS2\test3\lib\ exist or does your ant task create it ? Either way, it needs to be there . Robert On 9/13/06, SEOGCHAN OH <[EMAIL PROTECTED]> wrote: Dear: I got an error when I run jar_wsdl ant task. Main error is said that "SimpleValue has been deprecated" The full error message is given below. Could you guide me to address it? [javac] C:\research\AXIS2\test3\output\src\org\apache\axis2\userguide\xsd\im pl\EchoStringArrayParamDocumentImpl.java:15: warning: [deprecation] listValue() in org.apache.xmlbeans.SimpleValue has been deprecated [javac] public class EchoStringArrayParamDocumentImpl extends org.apache.xml beans.impl.values.XmlComplexContentImpl implements org.apache.axis2.userguide.xs d.EchoStringArrayParamDocument [javac] ^ [javac] Note: Some input files additionally use or override a deprecated API . [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 100 warnings jar_wsdl: [jar] Building jar: C:\research\AXIS2\test3\lib\axis2_example_wsdl.jar BUILD FAILED C:\research\AXIS2\test3\build.xml:110: Problem creating jar: C:\research\AXIS2\t est3\lib\axis2_example_wsdl.jar (The system cannot find the path specified) (and the archive is probably corrupt but I could not delete it) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
error at running jar_wsdl ant task
Dear:I got an error when I run jar_wsdl ant task.Main error is said that "SimpleValue has been deprecated"The full error message is given below.Could you guide me to address it?[javac] C:\research\AXIS2\test3\output\src\org\apache\axis2\userguide\xsd\impl\EchoStringArrayParamDocumentImpl.java:15: warning: [deprecation] listValue()in org.apache.xmlbeans.SimpleValue has been deprecated[javac] public class EchoStringArrayParamDocumentImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements org.apache.axis2.userguide.xsd.EchoStringArrayParamDocument[javac] ^[javac] Note: Some input files additionally use or override a deprecated API.[javac] Note: Some input files use unchecked or unsafe operations.[javac] Note: Recompile with -Xlint:unchecked for details.[javac] 100 warningsjar_wsdl:[jar] Building jar: C:\research\AXIS2\test3\lib\axis2_example_wsdl.jarBUILD FAILEDC:\research\AXIS2\test3\build.xml:110: Problem creating jar: C:\research\AXIS2\test3\lib\axis2_example_wsdl.jar (The system cannot find the path specified) (andthe archive is probably corrupt but I could not delete it)
[jira] Commented: (AXIS2-928) Not all added header elements are included in outgoing SOAP header unless run under debugger - bug in OMElement caching?
[ http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12434525 ] Derek Foster commented on AXIS2-928: Thanks to you and everyone who helped fix this! > Not all added header elements are included in outgoing SOAP header unless run > under debugger - bug in OMElement caching? > > > Key: AXIS2-928 > URL: http://issues.apache.org/jira/browse/AXIS2-928 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: client-api >Affects Versions: 1.0 >Reporter: Derek Foster > Assigned To: Eran Chinthaka >Priority: Blocker > > Hi, folks. > I have two custom headers, CARSLogin and CARSPassword, that are declared and > used in my WSDL like so: > > http://www.c-corp.com/wsdl/2004-10-01/f";> > http://www.dummy-temp-address"; > schemaLocation="F.xsd"/> > > > > http://www.c-corp.com/wsdl/2004-10-01/C";> > > > > > > > > > > > > > > > > > > > > > F Port Type > > > > > > > > F Soap Binding >transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > use="literal"/> > > > > > > > > > > > Now, when I use WSDL2Java to generate XMLBeans Java code for these, and try > to write a client that will send a message in this format, I write something > like this: > final CLoginDocument login = CLoginDocument.Factory.newInstance(); > login.setCLogin( "testlogin" ); > final CPasswordDocument password = > CPasswordDocument.Factory.newInstance(); > password.setCPassword( "testpassword" ); > final FServiceStub service = new FServiceStub( null, targetEndpoint ); > final FullEventUpdateDocument fullEventUpdate = > FullEventUpdateDocument.Factory.newInstance(); > fullEventUpdate.setFullEventUpdate( getSituation() ); > return service.acceptFEvent( fullEventUpdate, login, password ); > This seems reasonable, and mostly works. Except that when I look at the SOAP > output using TCPMon, the SOAP header that is included in the outgoing SOAP > message contains the CLogin element as expected, but totally omits the > CPassword element (!). I can find no reason for this. Both were passed to the > stub, and both are non-null, so both should be included in the output. > When I step through the code in the stub using a debugger, however, then the > code seems to correctly generate the header including both the login and > password, as I would expect. So this is a stereotypical "heisenbug" as per > the Jargon File: everything works fine when I run it under the debugger and > watch what is happening, but it fails when run normally. > My theory is that the debugger is calling toString() on various items such as > the SOAP envelope which is constructed to contain both the CLogin and CHeader > elements. I suspect that calling toString() in this fashion forces the > underlying OMElements to cache the results of parsing the XML, and that when > it comes time to generate the SOAP message for output, reading from this > cache works differently from parsing the header elements directly somehow. > Regardless, this seems like a pretty serious bug in Axis2: If I add multiple > header elements to a message, I expect that they all should be included in > the outgoing SOAP message, but that is not happening unless I run the program > under a debugger. The fact that this is nondeterministic hints at a caching > or multithreading bug at some level within the Axis architecture, which is > quite worrisome, since the process of formatting and sending a SOAP message > should be completely deterministic and repeatable. > Derek -- 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-1129) Doubled wrapper elements around XMLBeans-generated XML
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434523 ]
Davanum Srinivas commented on AXIS2-1129:
-
No bug fix involved. Problem is in XMLBeans code. It's quirkiness as far as i
am concerned as it is nothing to do with Axis2.
-- dims
> Doubled wrapper elements around XMLBeans-generated XML
> --
>
> Key: AXIS2-1129
> URL: http://issues.apache.org/jira/browse/AXIS2-1129
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: om, core, databinding, client-api, wsdl
>Affects Versions: 1.0
>Reporter: Derek Foster
>Priority: Blocker
>
> I recently noticed a big problem in how Axis2 generates XML for XMLBeans
> objects. It appears to be creating the wrapper element around
> an XMLBean twice, thus generating erroneous XML for a SOAP message. This
> appears to be a big problem that would affect a lot of web services, and is
> making it impossible for my company to use Axis2 to talk to our server.
> This error was found in the latest nightly build (September 8), but has
> apparently been around for some time.
> I have a particular WSDL, as follows:
>
> targetNamespace="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c";
>xmlns:F="http://www.dummy-temp-address";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns="http://schemas.xmlsoap.org/wsdl/";>
>
> http://www.c-corp.com/wsdl/2004-10-01/F";>
> http://www.dummy-temp-address";
> schemaLocation="F.xsd"/>
>
>
>
> http://www.c-corp.com/wsdl/2004-10-01/c";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> F Port Type
>
>
>
>
>
>
>
> F Soap Binding
>transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
> use="literal"/>
>
>
>
>
>
>
>
>
>
>
>
> F Web Service
>
> location="http://localhost:8080/axis/services/FService"/>
>
>
>
> My WSDL references the following XML schema:
>
> http://www.dummy-temp-address";
>xmlns="http://www.dummy-temp-address";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation";
>elementFormDefault="unqualified"
>attributeFormDefault="unqualified"
>version="DRAFT">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> After running WSDL2Java to generate the appropriate classes, I am using the
> following code to generate and transmit a client message to my SOAP server:
>protected ReturnDocument executeTest (
> final String targetEndpoint,
> final CLoginDocument login,
> final CPasswordDocument password )
> throws Exception
>{
> final FServiceStub service = new FServiceStub( null, targetEndpoint );
> final Options options = service._getServiceClient().getOptions();
> options.setProperty(
> org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE );
> service._getServiceClient().setOptions( options );
> final FullDocument full = Full.Factory.newInstance();
> full.setFull( getSituation() );
> return service.acceptFEvent( full, login, password );
>}
>private Full getSituation ()
> throws XmlException
>{
> return Full.Factory.parse(
> " http://www.dummy-temp-address\";>\n" +
> " \n" +
> ... and so forth: see output for the rest of this string ...
> " \n" +
> " \n" );
>}
> When I execute the above code, I get the following message sent to my server:
> POST /axis2/services/FService HTTP/1.1
> SOAPAction: acceptFEventAction
> User-Agent: Axis2
> Host: 127.0.0.1
> Content-Length: 8785
> Content-Type: text/xml; charset=UTF-8
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> xmlns="http://www.c-corp.com/wsdl/2004-10-01/c";>admin xmlns="http://www.dummy-temp-address";>
>
>
> QSenderOrganizationID
> QSenderCenterID
>
> 1
> 435
>
> 20040625
> 201225
> -0400
>
>
> 20040625
> 221222
[jira] Commented: (AXIS2-1129) Doubled wrapper elements around XMLBeans-generated XML
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434520 ]
Derek Foster commented on AXIS2-1129:
-
Hmm. In reading the above comment, it's not clear to me whether Dims found and
fixed an actual bug in the Axis2 or XMLBeans code, or whether he is simply
suggesting a workaround. It looks to me like the latter is true.
In regards to the comment "If you wrap it in a FullDocument and then call
toString() you will see the same problem that we are having. ", I think I
stated that in my initial bug report...?
Anyway, I think that the proposed workaround will probably allow me to get my
server working (once the other bugs I have filed are fixed), and so it's useful
and possibly worth having this bug no longer be considered a blocker for Axis
1.3, but isn't the original problem still a problem? It seems to me that if I
execute "full = Full.Factory.parse(whatever)" and then call
fullDocument.setFull(full), and then call fullDocument.toString(), that I
should not get a doubled 'full' element in the result. That seems to me to be a
bug, not just "quirkiness."
Please clarify: Was there an actual bugfix involved here, or is this just a
suggested workaround?
Derek
> Doubled wrapper elements around XMLBeans-generated XML
> --
>
> Key: AXIS2-1129
> URL: http://issues.apache.org/jira/browse/AXIS2-1129
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: om, core, databinding, client-api, wsdl
>Affects Versions: 1.0
>Reporter: Derek Foster
>Priority: Blocker
>
> I recently noticed a big problem in how Axis2 generates XML for XMLBeans
> objects. It appears to be creating the wrapper element around
> an XMLBean twice, thus generating erroneous XML for a SOAP message. This
> appears to be a big problem that would affect a lot of web services, and is
> making it impossible for my company to use Axis2 to talk to our server.
> This error was found in the latest nightly build (September 8), but has
> apparently been around for some time.
> I have a particular WSDL, as follows:
>
> targetNamespace="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:tns="http://www.c-corp.com/wsdl/2004-10-01/F";
>xmlns:c="http://www.c-corp.com/wsdl/2004-10-01/c";
>xmlns:F="http://www.dummy-temp-address";
>xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns="http://schemas.xmlsoap.org/wsdl/";>
>
> http://www.c-corp.com/wsdl/2004-10-01/F";>
> http://www.dummy-temp-address";
> schemaLocation="F.xsd"/>
>
>
>
> http://www.c-corp.com/wsdl/2004-10-01/c";>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> F Port Type
>
>
>
>
>
>
>
> F Soap Binding
>transport="http://schemas.xmlsoap.org/soap/http"/>
>
>
>
>
> use="literal"/>
>
>
>
>
>
>
>
>
>
>
>
> F Web Service
>
> location="http://localhost:8080/axis/services/FService"/>
>
>
>
> My WSDL references the following XML schema:
>
> http://www.dummy-temp-address";
>xmlns="http://www.dummy-temp-address";
>xmlns:xs="http://www.w3.org/2001/XMLSchema";
>xmlns:c="http://www.c-corp.com/schemas/c/schema_annotation";
>elementFormDefault="unqualified"
>attributeFormDefault="unqualified"
>version="DRAFT">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> After running WSDL2Java to generate the appropriate classes, I am using the
> following code to generate and transmit a client message to my SOAP server:
>protected ReturnDocument executeTest (
> final String targetEndpoint,
> final CLoginDocument login,
> final CPasswordDocument password )
> throws Exception
>{
> final FServiceStub service = new FServiceStub( null, targetEndpoint );
> final Options options = service._getServiceClient().getOptions();
> options.setProperty(
> org.apache.axis2.transport.http.HTTPConstants.CHUNKED, Boolean.FALSE );
> service._getServiceClient().setOptions( options );
> final FullDocument full = Full.Factory.newInstance();
> full.setFull( getSituation() );
> return service.acceptFEvent( full, login, password );
>}
>private Full getSituation ()
> throws XmlExc
[jira] Commented: (AXIS2-1147) Wrong request message from ADB stub for rpc-lit wsdl
[ http://issues.apache.org/jira/browse/AXIS2-1147?page=comments#action_12434512 ] Davanum Srinivas commented on AXIS2-1147: - Hmm, latest SVN r442957 gives me this request. http://tempuri.org/";> http://schemas.microsoft.com/2003/10/Serialization/";>12345 > Wrong request message from ADB stub for rpc-lit wsdl > > > Key: AXIS2-1147 > URL: http://issues.apache.org/jira/browse/AXIS2-1147 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding >Reporter: Deepal Jayasinghe >Priority: Blocker > > I generated stub for the [1] wsdl , which is of course RPC-LIT wsdl. Then I > try to invoke the service , but I realized it send the wrong request as shown > below (for the method RetChar); > http://tempuri.org/";> > xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/";>97 > > But As I know it should send the following request ; > http://tempuri.org/";> > 97 > > Part element should not be qualified for the RPC-LIT wsdl. > [1] > -http://131.107.72.15/SoapWsdl_BaseDataTypes_XmlFormatter_Service_Indigo/BaseDataTypesRpcLit.svc?wsdl > -- 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-928) Not all added header elements are included in outgoing SOAP header unless run under debugger - bug in OMElement caching?
[ http://issues.apache.org/jira/browse/AXIS2-928?page=all ] Eran Chinthaka resolved AXIS2-928. -- Resolution: Fixed I tested this and its working fine for me. So this should be fixed by now. Thanks Derek for finding this bug as this unveiled a bug (I'd say a blocker) in Axiom. > Not all added header elements are included in outgoing SOAP header unless run > under debugger - bug in OMElement caching? > > > Key: AXIS2-928 > URL: http://issues.apache.org/jira/browse/AXIS2-928 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: client-api >Affects Versions: 1.0 >Reporter: Derek Foster > Assigned To: Eran Chinthaka >Priority: Blocker > > Hi, folks. > I have two custom headers, CARSLogin and CARSPassword, that are declared and > used in my WSDL like so: > > http://www.c-corp.com/wsdl/2004-10-01/f";> > http://www.dummy-temp-address"; > schemaLocation="F.xsd"/> > > > > http://www.c-corp.com/wsdl/2004-10-01/C";> > > > > > > > > > > > > > > > > > > > > > F Port Type > > > > > > > > F Soap Binding >transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > use="literal"/> > > > > > > > > > > > Now, when I use WSDL2Java to generate XMLBeans Java code for these, and try > to write a client that will send a message in this format, I write something > like this: > final CLoginDocument login = CLoginDocument.Factory.newInstance(); > login.setCLogin( "testlogin" ); > final CPasswordDocument password = > CPasswordDocument.Factory.newInstance(); > password.setCPassword( "testpassword" ); > final FServiceStub service = new FServiceStub( null, targetEndpoint ); > final FullEventUpdateDocument fullEventUpdate = > FullEventUpdateDocument.Factory.newInstance(); > fullEventUpdate.setFullEventUpdate( getSituation() ); > return service.acceptFEvent( fullEventUpdate, login, password ); > This seems reasonable, and mostly works. Except that when I look at the SOAP > output using TCPMon, the SOAP header that is included in the outgoing SOAP > message contains the CLogin element as expected, but totally omits the > CPassword element (!). I can find no reason for this. Both were passed to the > stub, and both are non-null, so both should be included in the output. > When I step through the code in the stub using a debugger, however, then the > code seems to correctly generate the header including both the login and > password, as I would expect. So this is a stereotypical "heisenbug" as per > the Jargon File: everything works fine when I run it under the debugger and > watch what is happening, but it fails when run normally. > My theory is that the debugger is calling toString() on various items such as > the SOAP envelope which is constructed to contain both the CLogin and CHeader > elements. I suspect that calling toString() in this fashion forces the > underlying OMElements to cache the results of parsing the XML, and that when > it comes time to generate the SOAP message for output, reading from this > cache works differently from parsing the header elements directly somehow. > Regardless, this seems like a pretty serious bug in Axis2: If I add multiple > header elements to a message, I expect that they all should be included in > the outgoing SOAP message, but that is not happening unless I run the program > under a debugger. The fact that this is nondeterministic hints at a caching > or multithreading bug at some level within the Axis architecture, which is > quite worrisome, since the process of formatting and sending a SOAP message > should be completely deterministic and repeatable. > Derek -- 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: (AXIS-2545) wsdl2java mix up order of elements and arrays in super constructor call
[ http://issues.apache.org/jira/browse/AXIS-2545?page=comments#action_12434502 ] Michael Hu commented on AXIS-2545: -- Our project has encountered this bug as well when attempting to upgrade from Axis 1.3 to Axis 1.4. The bug is not present in 1.3 so it appears to have been introduced in 1.4. We are unable to upgrade as a result. Will a fix be available in 1.5? > wsdl2java mix up order of elements and arrays in super constructor call > --- > > Key: AXIS-2545 > URL: http://issues.apache.org/jira/browse/AXIS-2545 > Project: Apache Axis > Issue Type: Bug > Components: Basic Architecture >Affects Versions: 1.4 > Environment: Windows 2000 professional. > java version "1.4.2_05" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) > Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) >Reporter: Siegfried Sauter-Fischer > > I tried to create dataobjects using the following WSDL > > targetNamespace="http://axis-test.t-mobile.de/test/order"; > xmlns:order="http://axis-test.t-mobile.de/test/order"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> > > http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > type="xsd:string"/> > > > > > > > As a result I got a compiler error. > [javac] Compiling 2 source files to > Y:\wfa_source\pcm\src\WebserviceGateway\build_ProdVersion > [javac] > Y:\wfa_source\pcm\src\WebserviceGateway\generated_ProdVersion\de\t_mobile\axis_test\test\order\SubBean.java:17: > cannot resolve symbol > [javac] symbol : constructor SuperBean (int,java.lang.String) > [javac] location: class de.t_mobile.axis_test.test.order.SuperBean > [javac] super( > [javac] ^ > [javac] 1 error > The reason of this is a mix up in the order of the arguments in super class. > The constructor of SuperBean has the signature > public SuperBean( java.lang.String superContent, int superAttribute) > but in the constructor of SubBean you find the call > super( superAttribute, superContent); -- 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: (AXIS-2533) NullPointerException when redeploy axis context using Embedded Tomcat, first time deploy is working fine (other context are fine)
[ http://issues.apache.org/jira/browse/AXIS-2533?page=comments#action_12434498 ] Curtis Porter commented on AXIS-2533: - Copying axis.jar into WEB-INF/lib is a workaround, but it bloats the size of the webapp's .war file. > NullPointerException when redeploy axis context using Embedded Tomcat, first > time deploy is working fine (other context are fine) > - > > Key: AXIS-2533 > URL: http://issues.apache.org/jira/browse/AXIS-2533 > Project: Apache Axis > Issue Type: Bug > Components: Deployment / Registries >Affects Versions: 1.4 > Environment: Tomcat 5.0.28 as Embedded host, Axis 1.4, JDK 1.4.2_11, > Windows XP Pro SP 2 >Reporter: Patrick >Priority: Blocker > > We are using Tomcat 5.0.28 as Embedded host, then deploying /axis context to > handle web services. > When the application starts up initially, deploying /axis context works fine. > But we want to be able to make changes to the web services deployed under > axis, so we need to be able to undeploy the /axis context in the embedded > Tomcat, then redeploy the /axis context again, which at this point the > exception occurs (stack trace below). I think - correct me if I'm wrong - > it's something to do between axis and commons-discovery caching the class > loader (even though it is a new context - hence using new class loader)? I > have looked at the issue database, while there are something along the lines > of redeploy problem, I found none with similar exception (stack trace), hence > I'm posting this. > StandardContext[/axis]Servlet /axis threw load() exception > javax.servlet.ServletException: Servlet.init() for servlet AdminServlet threw > exception > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1071) > at > org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862) > at > org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4357) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) > at > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) > ... > - Root Cause - > java.lang.NullPointerException > at > org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:956) > at java.lang.ClassLoader.getResources(ClassLoader.java:851) > at > org.apache.commons.discovery.jdk.JDK12Hooks.getResources(JDK12Hooks.java:150) > at > org.apache.commons.discovery.resource.DiscoverResources$1.getNextResources(DiscoverResources.java:153) > at > org.apache.commons.discovery.resource.DiscoverResources$1.getNextResource(DiscoverResources.java:129) > at > org.apache.commons.discovery.resource.DiscoverResources$1.hasNext(DiscoverResources.java:116) > at > org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassNames(DiscoverNamesInFile.java:186) > at > org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassName(DiscoverNamesInFile.java:170) > at > org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.hasNext(DiscoverNamesInFile.java:157) > at > org.apache.commons.discovery.resource.names.NameDiscoverers$1.getNextIterator(NameDiscoverers.java:143) > at > org.apache.commons.discovery.resource.names.NameDiscoverers$1.hasNext(NameDiscoverers.java:126) > at > org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.getNextResource(ResourceClassDiscoverImpl.java:159) > at > org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.hasNext(ResourceClassDiscoverImpl.java:147) > at > org.apache.axis.configuration.EngineConfigurationFactoryFinder$1.run(EngineConfigurationFactoryFinder.java:120) > at java.security.AccessController.doPrivileged(Native Method) > at > org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(EngineConfigurationFactoryFinder.java:113) > at > org.apache.axis.transport.http.AxisServletBase.getEngineEnvironment(AxisServletBase.java:273) > at > org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:172) > at > org.apache.axis.transport.http.AxisServletBase.getOption(AxisServletBase.java:396) > at > org.apache.axis.transport.http.AxisServletBase.init(AxisServletBase.java:112) > at javax.servlet.GenericServlet.init(GenericServlet.java:261) > at > org.apache.catalina.core.Stan
[Axis2][Vote] Create a branch for the Axis2 1.1 release
Hi all, I would like to propose that we create a branch in Subversion for the 1.1 release (and all future releases) so that we can continue development on the main trunk while the release is occurring. This would also enable us to make point fixes to each release without requiring that users adopt a whole bag of new features (i.e. the next release) in order to get bug fixes. (I'm not saying that we will backport all bug fixes, just that having the release branch would enable us to do so.) -Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (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 ] John Pfeifer updated AXIS2-1140: Attachment: AbstractAarMojo.java I have made the necessary changes to fix the bug. Basically, I copied similar code from the maven-war-plugin which puts project dependencies into the WEB-INF/lib directory. In this case, I simply put the project dependencies in the lib directory of the .aar file. > 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 > 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] Updated: (AXIS2-1110) Java 2 Security
[ http://issues.apache.org/jira/browse/AXIS2-1110?page=all ] Ming Cheung updated AXIS2-1110: --- Attachment: patch.txt The attachment introduces a new utility class, AccessController.java and a testcase which demostrates the usage of the doPrivileged constructs. I encourage everyone to use the AccessController utility class to instrument AXIS2 codes as where need the doPrivileged construct. > 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: core > Environment: Supporting Axis2 runs inside of an environment with Java > 2 Security enabled >Reporter: Ming Cheung > Attachments: patch.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] Commented: (AXIS2-1070) Codegen & Service Archiver Eclipse plugins fail to load in Eclipse.
[ http://issues.apache.org/jira/browse/AXIS2-1070?page=comments#action_12434483 ] robert.onslow commented on AXIS2-1070: -- I had a similar problem when running Eclipse 3.2 for the first couple of times. But after closing Eclipse and restarting a couple of times, the problem cleared. I didn't rename the directory. > Codegen & Service Archiver Eclipse plugins fail to load in Eclipse. > --- > > Key: AXIS2-1070 > URL: http://issues.apache.org/jira/browse/AXIS2-1070 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.0 > Environment: Axis2 1.0 > Eclipse 3.2 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) > Windows XP Pro x64 >Reporter: Eric Schlenz > > The distributables for the Axis2 plugins do not load within Eclipse 3.2, and > possibly other versions. > I believe the problem is related to the naming convention used for the > subfolder within the "plugins" folder of the zip. For example, the Service > Archiver distributable contains the path > "plugins/Axis_Service_Archiver_1.0.0". As is, Eclipse does not recognize this. > BUT, if I change the name of the folder (after unpacking) to > "org.apache.axis2_servicearchiver_1.0" and restart Eclipse it shows up. > The exact same thing applies to the Codegen 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] Commented: (AXIS2-1145) Eclipse WSDL2JAVA client not creating newInstance() on Factory class
[ http://issues.apache.org/jira/browse/AXIS2-1145?page=comments#action_12434482 ] robert.onslow commented on AXIS2-1145: -- Same with WSDL2Java.bat in 1.0 distribution > Eclipse WSDL2JAVA client not creating newInstance() on Factory class > > > Key: AXIS2-1145 > URL: http://issues.apache.org/jira/browse/AXIS2-1145 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.0 > Environment: Eclipse 3.2 > XP >Reporter: robert.onslow > Attachments: BusinessCalendarWS.wsdl, BusinessCalendarWSStub.java > > > As the subject says -- 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-1148) Bug in TransportUtils with the file caching
[
http://issues.apache.org/jira/browse/AXIS2-1148?page=comments#action_12434460 ]
Roshan Punnoose commented on AXIS2-1148:
Instead of putting the whole file in here, here is the snippet I changed:
Two changes:
1. Line 179: cacheAttachmentString = (String) cacheAttachmentProperty
2. Line 212: attachmentSizeThreshold = (String) attachmentSizeThresholdProperty;
Below is the snippet of code from selectBuilderForMIME: (I added instanceofs
because we can't assume the properties will be Strings)
Object cacheAttachmentProperty = msgContext
.getProperty(Constants.Configuration.CACHE_ATTACHMENTS);
String cacheAttachmentString = null;
boolean fileCacheForAttachments;
if (cacheAttachmentProperty != null && cacheAttachmentProperty
instanceof String) {
cacheAttachmentString = (String)
cacheAttachmentProperty;
fileCacheForAttachments = (Constants.VALUE_TRUE
.equals(cacheAttachmentString));
} else {
Parameter parameter_cache_attachment = msgContext
.getParameter(Constants.Configuration.CACHE_ATTACHMENTS);
cacheAttachmentString = (parameter_cache_attachment !=
null) ? (String) parameter_cache_attachment
.getValue()
: null;
}
fileCacheForAttachments = (Constants.VALUE_TRUE
.equals(cacheAttachmentString));
String attachmentRepoDir = null;
String attachmentSizeThreshold = null;
if (fileCacheForAttachments) {
Object attachmentRepoDirProperty = msgContext
.getProperty(Constants.Configuration.ATTACHMENT_TEMP_DIR);
if (attachmentRepoDirProperty != null) {
attachmentRepoDir = (String)
attachmentRepoDirProperty;
} else {
Parameter attachmentRepoDirParameter =
msgContext
.getParameter(Constants.Configuration.ATTACHMENT_TEMP_DIR);
attachmentRepoDir = (attachmentRepoDirParameter
!= null) ? (String) attachmentRepoDirParameter
.getValue()
: null;
}
Object attachmentSizeThresholdProperty = msgContext
.getProperty(Constants.Configuration.FILE_SIZE_THRESHOLD);
if (attachmentSizeThresholdProperty != null &&
attachmentSizeThresholdProperty instanceof String) {
attachmentSizeThreshold = (String)
attachmentSizeThresholdProperty;
} else {
Parameter attachmentSizeThresholdParameter =
msgContext
.getParameter(Constants.Configuration.FILE_SIZE_THRESHOLD);
attachmentSizeThreshold =
attachmentSizeThresholdParameter
.getValue().toString();
}
}
> Bug in TransportUtils with the file caching
> ---
>
> Key: AXIS2-1148
> URL: http://issues.apache.org/jira/browse/AXIS2-1148
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core
>Affects Versions: 1.0
> Environment: Weblogic 8.1, Axis2 Client
>Reporter: Roshan Punnoose
>
> Ok, maybe I'm not looking at this right, but I think I see a bug in
> TransportUtils.selectBuilderForMIME(...):
> Object cacheAttachmentProperty = msgContext
> .getProperty(Constants.Configuration.CACHE_ATTACHMENTS);
> String cacheAttachmentString = null;
> boolean fileCacheForAttachments;
> if (cacheAttachmentProperty != null) {
> cacheAttachmentProperty =
> cacheAttachmentProperty;
> fileCacheForAttachments = (Constants.VALUE_TRUE
> .equals(cacheAttachmentString));
> The cacheAttachmentString is always going to be null right? Then, the
> client will never actually cache the attachment in the temp directory if
> the properties have been set. Right? Am I going crazy?
> If you want, I can post my fix for it.
--
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 JIR
[jira] Commented: (AXIS2-1147) Wrong request message from ADB stub for rpc-lit wsdl
[ http://issues.apache.org/jira/browse/AXIS2-1147?page=comments#action_12434449 ] Davanum Srinivas commented on AXIS2-1147: - Deepal, Slight typo. the request should be http://tempuri.org/";> 97 Note that the inChar is not namespace qualified. To better illustrate, the following is also equivalent http://tempuri.org/";> 97 thanks, dims > Wrong request message from ADB stub for rpc-lit wsdl > > > Key: AXIS2-1147 > URL: http://issues.apache.org/jira/browse/AXIS2-1147 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding >Reporter: Deepal Jayasinghe >Priority: Blocker > > I generated stub for the [1] wsdl , which is of course RPC-LIT wsdl. Then I > try to invoke the service , but I realized it send the wrong request as shown > below (for the method RetChar); > http://tempuri.org/";> > xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/";>97 > > But As I know it should send the following request ; > http://tempuri.org/";> > 97 > > Part element should not be qualified for the RPC-LIT wsdl. > [1] > -http://131.107.72.15/SoapWsdl_BaseDataTypes_XmlFormatter_Service_Indigo/BaseDataTypesRpcLit.svc?wsdl > -- 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-1113) If callObjec.invokeOneWay() is being used for a huge data transfer, client side system is encountering Socket create exception
[ http://issues.apache.org/jira/browse/AXIS2-1113?page=comments#action_12434433 ] Hari H Krishna commented on AXIS2-1113: --- You are right. Thanks for your findings. I will open a defect in Apache 1.x > If callObjec.invokeOneWay() is being used for a huge data transfer, client > side system is encountering Socket create exception > -- > > Key: AXIS2-1113 > URL: http://issues.apache.org/jira/browse/AXIS2-1113 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports > Environment: ALL >Reporter: Hari H Krishna > > Basic problem is, invokeOneway() function of call object internally spawns a > new thread for each call to invokeOne way. > One of our sub-component that is a part of Generic Log Adapter uses > invokeOneWay() function internally to send events/data to WS-Notification > resource. This functionality is working fine when small number of events are > sent, but when large number of events are sent, too many ports are being > opened and at certain point the ws-notification is left with no port and is > throwing Socket create exception. > The requirement is, there shoud be a way to control the number of threads > that are being created inside invokeOneWay(). -- 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: (AXIS-2558) If callObjec.invokeOneWay() is being used for a huge data transfer, client side system is encountering Socket create exception
If callObjec.invokeOneWay() is being used for a huge data transfer, client side system is encountering Socket create exception -- Key: AXIS-2558 URL: http://issues.apache.org/jira/browse/AXIS-2558 Project: Apache Axis Issue Type: Bug Reporter: Hari H Krishna Basic problem is, invokeOneway() function of call object internally spawns a new thread for each call to invokeOne way. One of our sub-component that is a part of Generic Log Adapter uses invokeOneWay() function internally to send events/data to WS-Notification resource. This functionality is working fine when small number of events are sent, but when large number of events are sent, too many ports are being opened and at certain point the ws-notification is left with no port and is throwing Socket create exception. The requirement is, there shoud be a way to control the number of threads that are being created inside invokeOneWay(). -- 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-1148) Bug in TransportUtils with the file caching
Bug in TransportUtils with the file caching
---
Key: AXIS2-1148
URL: http://issues.apache.org/jira/browse/AXIS2-1148
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: core
Affects Versions: 1.0
Environment: Weblogic 8.1, Axis2 Client
Reporter: Roshan Punnoose
Ok, maybe I'm not looking at this right, but I think I see a bug in
TransportUtils.selectBuilderForMIME(...):
Object cacheAttachmentProperty = msgContext
.getProperty(Constants.Configuration.CACHE_ATTACHMENTS);
String cacheAttachmentString = null;
boolean fileCacheForAttachments;
if (cacheAttachmentProperty != null) {
cacheAttachmentProperty =
cacheAttachmentProperty;
fileCacheForAttachments = (Constants.VALUE_TRUE
.equals(cacheAttachmentString));
The cacheAttachmentString is always going to be null right? Then, the
client will never actually cache the attachment in the temp directory if
the properties have been set. Right? Am I going crazy?
If you want, I can post my fix for it.
--
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-1147) Wrong request message from ADB stub for rpc-lit wsdl
Wrong request message from ADB stub for rpc-lit wsdl Key: AXIS2-1147 URL: http://issues.apache.org/jira/browse/AXIS2-1147 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Reporter: Deepal Jayasinghe Priority: Blocker I generated stub for the [1] wsdl , which is of course RPC-LIT wsdl. Then I try to invoke the service , but I realized it send the wrong request as shown below (for the method RetChar); http://tempuri.org/";> http://schemas.microsoft.com/2003/10/Serialization/";>97 But As I know it should send the following request ; http://tempuri.org/";> 97 Part element should not be qualified for the RPC-LIT wsdl. [1] -http://131.107.72.15/SoapWsdl_BaseDataTypes_XmlFormatter_Service_Indigo/BaseDataTypesRpcLit.svc?wsdl -- 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: Ant
Ant is _not_ bundled with axis2, it is a seperate project: http://ant.apache.org HTH, Robert On 9/13/06, SEOGCHAN OH <[EMAIL PROTECTED]> wrote: Dear. Questions regarding Code Generator Tool, in particualr, Ant task According to manual, Ant task is bundled with Axis2 distribution. Which directory contains this information so that I can type 'ant' or 'ant main'? Thank you, SC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1132) ?WSDL returns IP address instead of hostname
[ http://issues.apache.org/jira/browse/AXIS2-1132?page=comments#action_12434417 ] Gary Woods commented on AXIS2-1132: --- Having analysed the code a little it seems that all of the caller of getEPRs get the requestIP, why not use this instead of recomputing it? > ?WSDL returns IP address instead of hostname > > > Key: AXIS2-1132 > URL: http://issues.apache.org/jira/browse/AXIS2-1132 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: core > Environment: Windows XP, AXIS2 (SNAPSHOT 09 Sept. 2006) >Reporter: Gary Woods > > This may be related to AXIS2-700 fix. The IP address is returned instead of > the hostname for URLs in the WSDL file. Deos this not makes the URLs less > robust on machines that have dyanmic IP addresses? -- 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-1146) ClassNotFoundException occured while testing the EchoBlockingClient
ClassNotFoundException occured while testing the EchoBlockingClient --- Key: AXIS2-1146 URL: http://issues.apache.org/jira/browse/AXIS2-1146 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Environment: Windows XP, Maven 1.0.2, jdk1.5.0_08 Reporter: Evanthika Amarasiri Priority: Critical I was trying out the examples given in the "Writing Web Services Using Axis2's Primary APIs" of the User's Guide. According to the steps given in the User's Guide, I created the MyService.aar file with the MyService.java file packaged along with the service.xml and it allowed me to do so. Then I deployed the MyService.aar file and the service was deployed successfully. After that I was trying to test the EchoBlockingClient example. For that, I tried to build the ant file which was given in the "Axis2Home/samples/userguide" directory and it threw the following exception testEchoBlockingClient: [java] Sep 13, 2006 3:28:56 PM org.apache.axis2.deployment.DeploymentEngine prepareRepository [java] INFO: no services directory found , new one created [java] Sep 13, 2006 3:28:56 PM org.apache.axis2.deployment.DeploymentEngine doDeploy [java] INFO: Deploying module : addressing [java] Sep 13, 2006 3:28:56 PM org.apache.axis2.engine.AxisEngine receiveFault [java] INFO: Received Error Message with id urn:uuid:A64DEA4609774E82E911581415366561 [java] org.apache.axis2.AxisFault: userguide.example1.MyService [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:298) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:539) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:473) [java] at userguide.clients.EchoBlockingClient.main(EchoBlockingClient.java:42) [java] Caused by: java.lang.Exception: org.apache.axis2.AxisFault: userguide.example1.MyService; nested exception is: [java] java.lang.ClassNotFoundException: userguide.example1.MyService [java] at org.apache.axis2.AxisFault.makeFault(AxisFault.java:318) [java] at org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:99) [java] at org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:131) [java] at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:73) [java] at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) [java] at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497) [java] at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:309) [java] at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:201) [java] at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) [java] at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) [java] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) [java] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) [java] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) [java] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) [java] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) [java] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) [java] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) [java] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) [java] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) [java] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) [java] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) [java] at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) [java] at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) [java] at java.lang.Thread.run(Unknown Source) [java] Caused by: java.lang.ClassNotFoundException: userguide.example1.MyService [java] at java.net.URLClassLoader$1.run(Unknown Source) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(Unknown Source) [java]
[jira] Commented: (AXIS2-749) Mixing compile time and runtime support in codegen jar
[ http://issues.apache.org/jira/browse/AXIS2-749?page=comments#action_12434406 ] Davanum Srinivas commented on AXIS2-749: Please go ahead. +1 from me. -- dims > Mixing compile time and runtime support in codegen jar > -- > > Key: AXIS2-749 > URL: http://issues.apache.org/jira/browse/AXIS2-749 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas > Assigned To: Deepal Jayasinghe > > org.apache.axis2.rpc.receivers.RPCMessageReceiver is currently in > axis2-codegen-SNAPSHOT.jar...why "codegen"? can we please have just the > compile/build time stuff in "codegen"? -- 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-1082) digest authentication is not working
[
http://issues.apache.org/jira/browse/AXIS2-1082?page=comments#action_12434404 ]
Saminda Wishwajith Abeyruwan commented on AXIS2-1082:
-
Commons-httpclient provides NTLM, Digest and Basic Authentication. Depending on
the server it does choose the Authentication Mechanism. Thus, in Axis2 there
exist only one bean for Authentication, its an inner class named Authenticator
in HttpTransportProperties. When writing the client, if it needs
authentication, client app should set the following property,
Options options = new Options();
...
HttpTransportProperties.Authenticator auth = new
HttpTransportProperties.Authenticator();
auth.setUsername("axis2");
auth,setPassword("axis2");
auth.set..
options.setProperty(HTTPConstants.AUTHENTICATE,auth);
...
Thus, above is the only thing a user has to set to enable authentication. Then,
depending on the server, commons-httpclient uses the auth starting from NTLM
then Digest finally Basic.
Please do check this out with your existing clients.
> digest authentication is not working
>
>
> Key: AXIS2-1082
> URL: http://issues.apache.org/jira/browse/AXIS2-1082
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: transports
> Environment: Windows XP, using Axis 2 nightly build
>Reporter: jeff ling
> Assigned To: Saminda Wishwajith Abeyruwan
>
> Digest Auth should work, httpclient supports it. It's a matter of how to use
> httpclient from axis2.
> Another problem is, currently client has to specify whether to use basic,
> ntlm, but that's not right. The ntlm, digest, basic should be tried in that
> sequence without client's specification.
--
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-993) org.apache.axis2.addressing.EndpointReference should explicitly save the WS-Addressing namespace
[ http://issues.apache.org/jira/browse/AXIS2-993?page=comments#action_12434392 ] Brian DePradine commented on AXIS2-993: --- Eran, I believe that option 2 is the preferrable option. I will submit a new patch that implements that option shortly. > org.apache.axis2.addressing.EndpointReference should explicitly save the > WS-Addressing namespace > > > Key: AXIS2-993 > URL: http://issues.apache.org/jira/browse/AXIS2-993 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: Addressing >Reporter: Brian DePradine >Priority: Blocker > Attachments: newerpatch.txt, newpatch.txt, patch.txt > > > Currently, the EndpointReference class always assumes that it is a > representation of endpoint references based on the WS-Addressing 2005/08 > (final) spec. However, this class is also used to represent endpoint > references based on the 2004/08 (submission) spec. The problem is that the > methods toOM() and fromOM() only work correctly in the former case. If the > EndpointReference class is modified to explicitly save the WS-Addressing > namespace then these methods can be made to work correctly for both specs. > Patch to follow. -- 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-1145) Eclipse WSDL2JAVA client not creating newInstance() on Factory class
[ http://issues.apache.org/jira/browse/AXIS2-1145?page=all ] robert.onslow updated AXIS2-1145: - Attachment: BusinessCalendarWSStub.java BusinessCalendarWS.wsdl > Eclipse WSDL2JAVA client not creating newInstance() on Factory class > > > Key: AXIS2-1145 > URL: http://issues.apache.org/jira/browse/AXIS2-1145 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: Tools >Affects Versions: 1.0 > Environment: Eclipse 3.2 > XP >Reporter: robert.onslow > Attachments: BusinessCalendarWS.wsdl, BusinessCalendarWSStub.java > > > As the subject says -- 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-1145) Eclipse WSDL2JAVA client not creating newInstance() on Factory class
Eclipse WSDL2JAVA client not creating newInstance() on Factory class Key: AXIS2-1145 URL: http://issues.apache.org/jira/browse/AXIS2-1145 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.0 Environment: Eclipse 3.2 XP Reporter: robert.onslow As the subject says -- 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-810) Axis2 1.0 server remove nillable attributes
[ http://issues.apache.org/jira/browse/AXIS2-810?page=comments#action_12434383 ] Sébastien Arod commented on AXIS2-810: -- The bug was on the XmlSchema side. (see http://issues.apache.org/jira/browse/WSCOMMONS-48?watch=true) Nothing changed on the Axis2 code. Seb > Axis2 1.0 server remove nillable attributes > --- > > Key: AXIS2-810 > URL: http://issues.apache.org/jira/browse/AXIS2-810 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: 1.0 > Environment: Widows XP > JDK 1.5.0_06 > apache-tomcat-5.5.12 > Axis2 1.0 webapp >Reporter: Sébastien Arod >Priority: Critical > Attachments: WSCity.wsdl, WSCity_modified.wsdl > > > When I deploy a web service with a specified WSDL in the Axis2 webapp the xsd > nillable attributes are removed from WSDL by Axis2. -- 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-746) Missing error explanations in AxisServlet
[
http://issues.apache.org/jira/browse/AXIS2-746?page=comments#action_12434381 ]
Ali Sadik Kumlali commented on AXIS2-746:
-
You seem right Deepal. After your comment, I made some trials with the logging
framework and came to a conclusion:
Code:
-
Exception ex = new Exception ();
log.debug(ex);
ex = new Exception ("Actual error message");
log.debug(ex);
ex = new Exception (new Exception());
log.debug(ex);
ex = new Exception (new Exception("Actual error message"));
log.debug(ex);
Output:
-
[DEBUG] logtest.TestLog4j - java.lang.Exception
[DEBUG] logtest.TestLog4j - java.lang.Exception: Actual error message
[DEBUG] logtest.TestLog4j - java.lang.Exception: java.lang.Exception
[DEBUG] logtest.TestLog4j - java.lang.Exception: java.lang.Exception: Actual
error message
Conclusion
---
- Creating exceptions without passing to them the actual message, causes lack
of information such as java.lang.Exception and org.apache.axis2.AxisFault.
- If an exception is created without passing it a message and this exception is
passed to constructor of another exception, the same thing happens.
- If I see a log that says "org.apache.axis2.AxisFault" only, there must be a
"new AxisFault()" or "new AxisFault(ex)" where ex must be created similar to
"new Exception()".
- I've searched all the code base and couldn't find "new AxisFault()"
- Therefore, some of the exceptions that is passed to constructor of AxisFault
*must* be created without passing them a message. In this case, Axis2 has
nothing to do.
> Missing error explanations in AxisServlet
> -
>
> Key: AXIS2-746
> URL: http://issues.apache.org/jira/browse/AXIS2-746
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: core
> Environment: Win2K Pro, JDK 1.4, Tomcat 5.5
>Reporter: Ali Sadik Kumlali
> Assigned To: Deepal Jayasinghe
>
> catch block found in doPost method doesn't print the actual error but prints
> "org.apache.axis2.AxisFault".
>
> In 405768 revision
> --
> } catch (AxisFault e) {
> log.debug(e);
> if (msgContext != null) {
> try {
>
> res.setStatus(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);
> handleFault(msgContext, out, e);
> } catch (AxisFault e2) {
> log.info(e2);
> }
> } else {
> throw new ServletException(e);
> }
> }
> Should be
> ---
> } catch (AxisFault e) {
> log.debug("bla bla", e); // or log.debug(e.getMessage());
> if (msgContext != null) {
> try {
>
> res.setStatus(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);
> handleFault(msgContext, out, e);
> } catch (AxisFault e2) {
> log.info("bla bla2",e2); // or log.info(e.getMessage());
> }
> } else {
> throw new ServletException(e);
> }
> }
--
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][Vote] Thilina as the release manager for Axis2 1.1
+1 On 13/09/06, Afkham Azeez <[EMAIL PROTECTED]> wrote: +1 On 9/12/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to nominate Thilina Gunarathne as our new release manager for > Axis2 1.1. I'm sure he will have the luxury of releasing the most stable > Axis2 version so far :). > > Here is my +1. > > Thanks, > Chinthaka > > > > -- Thanks Afkham Azeez -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
