Re: Get wsdl url for service description
Does this http://mail-archives.apache.org/mod_mbox/portals-wsrp4j-user/200506.mbox/[EMAIL PROTECTED] fixed? Thanks, Alexey. On Wed, Dec 10, 2008 at 12:48 AM, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > Hello, > > I use Axis1 1.4 with my service. I have an application with multiport > service producer use org.apache.axis.transport.http.AxisServlet > > How can I get a wsdl service description? > > Regards, > Alexey. >
Get wsdl url for service description
Hello, I use Axis1 1.4 with my service. I have an application with multiport service producer use org.apache.axis.transport.http.AxisServlet How can I get a wsdl service description? Regards, Alexey.
Re: Lightweight servlet container to test web services
Thank you for reply. I am developer of java web services based on Axis1. For regular testing I have to start/stop servlet container to deploy/undeploy test WAR application. This process should be embedded into maven2 regular test process. Is there documentation how can we start and deploy sample test application with maven2 test phase on SimpleAxisServer? PS, we found Cargo project, but don't sure is it well for such kind of task. Thanks and regards, Alexey On Thu, Jul 3, 2008 at 3:47 PM, Andrew Clegg <[EMAIL PROTECTED]> wrote: > For production use, what are the advantages of deploying Axis2 within > a full-on application server? > > We don't use any other Java web applications -- indeed, we don't use > any other Java applications at the moment -- but we are migrating some > webservices from Perl/SOAP::Lite to Java/Axis2. > > Given that the rest of our web infrastructure is based on Apache, > mod_perl and legacy CGI scripts, and is likely to remain that way for > quite some time, is there any actual point in the additional overhead > of using a servlet container like Tomcat? Is it somehow more secure or > robust than Axis2's built-in http server? > > Thanks, > > Andrew. > > 2008/7/3 Paul Fremantle <[EMAIL PROTECTED]>: > > Axis and Axis2 also offer a lightweight built-in server runtime for > > testing. Just look in the bin\ directory. > > > > Paul > > > > On Thu, Jul 3, 2008 at 12:12 PM, Alexey Zavizionov > > <[EMAIL PROTECTED]> wrote: > >> Is there anybody who use maven2 and any servlet container to test web > >> services? > >> Probably, servlet container runs as maven plugin. > >> > >> Regards, > >> Alexey > >> > > > > > > > > -- > > Paul Fremantle > > Co-Founder and CTO, WSO2 > > Apache Synapse PMC Chair > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > - > > 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: Lightweight servlet container to test web services
I see SimpleAxis2Server in the bin dir for Axis2, but nothing in the axis1distribution. My service is based on Axis1. On Thu, Jul 3, 2008 at 3:26 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote: > Axis and Axis2 also offer a lightweight built-in server runtime for > testing. Just look in the bin\ directory. > > Paul > > On Thu, Jul 3, 2008 at 12:12 PM, Alexey Zavizionov > <[EMAIL PROTECTED]> wrote: > > Is there anybody who use maven2 and any servlet container to test web > > services? > > Probably, servlet container runs as maven plugin. > > > > Regards, > > Alexey > > > > > > -- > Paul Fremantle > Co-Founder and CTO, WSO2 > Apache Synapse PMC Chair > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Lightweight servlet container to test web services
Is there anybody who use maven2 and any servlet container to test web services? Probably, servlet container runs as maven plugin. Regards, Alexey
Re: Axis and websphere
Thanks for your reply. I fixed problems. On Thu, Jun 19, 2008 at 5:38 PM, ab <[EMAIL PROTECTED]> wrote: > Yes. I've done that and its been working in production for about 6months or > so. Are you running into some issues? > > -ab > > > - Original Message > From: Alexey Zavizionov <[EMAIL PROTECTED]> > To: axis-user@ws.apache.org > Sent: Thursday, June 19, 2008 10:07:20 AM > Subject: Axis and websphere > > Hello, > > Does anybody work with axis on websphere application server? > > Regards, > Alexey > >
Axis and websphere
Hello, Does anybody work with axis on websphere application server? Regards, Alexey
Re: DeserializationContext SOAPFaultBuilder on client.
Application server has thrown a strange exc Please, help. java.lang.RuntimeException: SRV.8.2: RequestWrapper objects must extend ServletRequestWrapper or HttpServletRequestWrapper at com.ibm.wsspi.webcontainer.util.ServletUtil.unwrapRequest(ServletUtil.java:78) at com.ibm.wsspi.webcontainer.util.ServletUtil.unwrapRequest(ServletUtil.java:56) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:534) ... ... ... at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:410) at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186) at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:332) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454) at org.apache.axis.server.AxisServer.invokeService(AxisServer.java:234) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:375) at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) AxisFilter.doFilter(AxisFilter.java:86) ... On Fri, May 16, 2008 at 7:53 PM, Alexey Zavizionov < [EMAIL PROTECTED]> wrote: > I have just understood that is the server issue.. > sorry for disturb. > > Regards, > Alexey > > > On Fri, May 16, 2008 at 1:39 PM, Alexey Zavizionov < > [EMAIL PROTECTED]> wrote: > >> Hello list, >> >> I am a subscriber of the list more than a year.. :) >> You have helped many people. >> >> I have an exc with my web service which based on axis1 1.4 and deployed on >> WAS 6.1: >> >> java.lang.RuntimeException: SRV.8.2: RequestWrapper objects must extend >> ServletRequestWrapper or HttpServletRequestWrapper >> at >> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:223) >> at >> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:130) >> at >> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) >> at >> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) >> at >> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1772) >> at >> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2923) >> at >> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) >> at >> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) >> at >> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) >> at >> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) >> at >> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) >> at >> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) >> at >> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) >> at >> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) >> at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) >> at >> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) >> at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:695) >> at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) >> at >> org.apache.axis.wsa.WSAHandler.processClientRespo
Re: WSDL2Java on WSRP WSDL fails
Hi Nicolas,
Will search eXo wsrp project, this service is based on Axis1 1.4
Look for sources how to generate WSDL2Java.
HTH,
Alexey
On Tue, Oct 16, 2007 at 1:34 PM, Nicolas Vahlas <[EMAIL PROTECTED]> wrote:
> Axis: Axis-1_3 or Axis-1_4
> Java: JDK 1.6 or JDK 1.4
> Ant: Apache Ant 1.6.5
>
> When running the WSDL2Java ant task on the WSDL of the WSRP (Web
> Services for Remote Protlets) retrieved from OASIS along with all the
> files imported by this WSDL file, I get the following error:
>
> [axis-wsdl2java] java.lang.ClassCastException: java.util.ArrayList
> [axis-wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:724)
> [axis-wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543)
> [axis-wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518)
> [axis-wsdl2java] at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
> [axis-wsdl2java] at
> org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
> [axis-wsdl2java] at java.lang.Thread.run(Thread.java:595)
>
> My build.xml file contains the following call to the WSDL2Java ant task:
>
>
> verbose="true"
>url="${wsdl.url}"
>debug="true"
>wrapArrays="true">
>
>
>
> I have searched around the Internet and the mailing lists in order to
> find out what may be wrong with no success. Can anyone help me on that ?
>
> Thanks,
> Nicolas
>
> --
> VAHLAS Nicolas
> Technical Architect
>
> Quality & Reliability
> Address: Konitsis 11B,
> 151 25 Marousi
> Tel.:(+ 30) 210 80 29 409 (270)
> Mobile: (+ 30) 694 58 76 506
> Mail:[EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Re: DeserializationContext SOAPFaultBuilder on client.
I have just understood that is the server issue.. sorry for disturb. Regards, Alexey On Fri, May 16, 2008 at 1:39 PM, Alexey Zavizionov < [EMAIL PROTECTED]> wrote: > Hello list, > > I am a subscriber of the list more than a year.. :) > You have helped many people. > > I have an exc with my web service which based on axis1 1.4 and deployed on > WAS 6.1: > > java.lang.RuntimeException: SRV.8.2: RequestWrapper objects must extend > ServletRequestWrapper or HttpServletRequestWrapper > at > org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:223) > at > org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:130) > at > org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1772) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2923) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) > at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) > at > com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) > at > org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) > at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:695) > at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) > at > org.apache.axis.wsa.WSAHandler.processClientResponse(WSAHandler.java:82) > at org.apache.axis.wsa.WSAHandler.invoke(WSAHandler.java:41) > at > org.apache.axis.client.AxisClient.invokeTransport(AxisClient.java:154) > at org.apache.axis.client.AxisClient.invoke(AxisClient.java:289) > at org.apache.axis.client.Call.invokeEngine(Call.java:2838) > at org.apache.axis.client.Call.invoke(Call.java:2824) > at org.apache.axis.client.Call.invoke(Call.java:2501) > at org.apache.axis.client.Call.invoke(Call.java:2424) > at org.apache.axis.client.Call.invoke(Call.java:1835) > > Regards, > Alexey >
DeserializationContext SOAPFaultBuilder on client.
Hello list, I am a subscriber of the list more than a year.. :) You have helped many people. I have an exc with my web service which based on axis1 1.4 and deployed on WAS 6.1: java.lang.RuntimeException: SRV.8.2: RequestWrapper objects must extend ServletRequestWrapper or HttpServletRequestWrapper at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:223) at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:130) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1772) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2923) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:508) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:695) at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at org.apache.axis.wsa.WSAHandler.processClientResponse(WSAHandler.java:82) at org.apache.axis.wsa.WSAHandler.invoke(WSAHandler.java:41) at org.apache.axis.client.AxisClient.invokeTransport(AxisClient.java:154) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:289) at org.apache.axis.client.Call.invokeEngine(Call.java:2838) at org.apache.axis.client.Call.invoke(Call.java:2824) at org.apache.axis.client.Call.invoke(Call.java:2501) at org.apache.axis.client.Call.invoke(Call.java:2424) at org.apache.axis.client.Call.invoke(Call.java:1835) Regards, Alexey
Re: VerifyError: javax/xml/parsers/DocumentBuilder.parse
I have just fixed with shared libs. Thanks, and sorry for disturb. Regards, Alexey On Thu, May 15, 2008 at 10:54 AM, Alexey Zavizionov < [EMAIL PROTECTED]> wrote: > Hello , > > I have a question regarding DocumentBuilder on Websphere application server > 6.1 (WAS). > > > I have an exception while deploy axis service, which I couldn't resolve. Do > you know something about it? > > Stack Dump = java.lang.VerifyError: > javax/xml/parsers/DocumentBuilder.parse(Lorg/xml/sax/InputSource;)Lorg/w3c/dom/Document; > at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369) > at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:388) > at > org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:180) > at org.apache.axis.AxisEngine.init(AxisEngine.java:172) > at org.apache.axis.AxisEngine.(AxisEngine.java:156) > at org.apache.axis.server.AxisServer.(AxisServer.java:96) > at > org.apache.axis.server.DefaultAxisServerFactory.createServer(DefaultAxisServerFactory.java:109) > at > org.apache.axis.server.DefaultAxisServerFactory.getServer(DefaultAxisServerFactory.java:73) > at org.apache.axis.server.AxisServer.getServer(AxisServer.java:81) > at > org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:185) > 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:256) > at > com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:192) > > PS: On tomcat with sun jdk it works. > > Regards, > Alexey > >
VerifyError: javax/xml/parsers/DocumentBuilder.parse
Hello , I have a question regarding DocumentBuilder on Websphere application server 6.1 (WAS). I have an exception while deploy axis service, which I couldn't resolve. Do you know something about it? Stack Dump = java.lang.VerifyError: javax/xml/parsers/DocumentBuilder.parse(Lorg/xml/sax/InputSource;)Lorg/w3c/dom/Document; at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369) at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:388) at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:180) at org.apache.axis.AxisEngine.init(AxisEngine.java:172) at org.apache.axis.AxisEngine.(AxisEngine.java:156) at org.apache.axis.server.AxisServer.(AxisServer.java:96) at org.apache.axis.server.DefaultAxisServerFactory.createServer(DefaultAxisServerFactory.java:109) at org.apache.axis.server.DefaultAxisServerFactory.getServer(DefaultAxisServerFactory.java:73) at org.apache.axis.server.AxisServer.getServer(AxisServer.java:81) at org.apache.axis.transport.http.AxisServletBase.getEngine(AxisServletBase.java:185) 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:256) at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:192) PS: On tomcat with sun jdk it works. Regards, Alexey
Re: Axis 1.4 WSDL4J wrong arguments sequence in generated classes
Thanks, it works!!!
On Jan 28, 2008 10:52 PM, Alick Buckley <[EMAIL PROTECTED]> wrote:
>
>
>
>
> wsdl2java mix up order of elements and arrays in super constructor call
>
> http://issues.apache.org/jira/browse/AXIS-2545
>
>
> Use the Axis 1.4 nightly build.
>
> I am using Nov 19 build and this was fixed.
>
> http://people.apache.org/dist/axis/nightly/axis-bin-1_4.zip
>
>
> =====
>
>
>
> -Original Message-
> From: Alexey Zavizionov [mailto:[EMAIL PROTECTED]
> Sent: Friday, 25 January 2008 11:08 PM
> To: axis-user@ws.apache.org
> Cc: Roman Pedchenko; Gennady Azarenkov
> Subject: Re: Axis 1.4 WSDL4J wrong arguments sequence in generated
> classes
>
>
> Hi,
>
> WSDL2Java generates uncompilable code.
>
> Classes that inherite from some parent classes have the constructor
> parameters in the wrong order.
>
> Example:
>
> I have the exeption
> /home/alexey/java/eXoProjects/portlet-container/trunk/component/plugins/wsrp2/target/generated/org/exoplatform/services/wsrp2/type/MarkupContext.java:[31,8]
>
> cannot find symbol
> symbol : constructor MimeResponse(java.lang.String,java.lang.Boolean)
> location: class org.exoplatform.services.wsrp2.type.MimeResponse
>
> Parent:
>
>
>
>default="false" minOccurs="0"/>
>
> use="optional"/>
>
>
>
> public class MimeResponse implements java.io.Serializable {
>
> public MimeResponse(
>java.lang.Boolean useCachedItem,
>java.lang.String ccppProfileWarning) {
>this.useCachedItem = useCachedItem;
>this.ccppProfileWarning = ccppProfileWarning;
> }
>
> Child:
>
>
>
>
>
> minOccurs="0"/>
>
>
>
>
>
>
> public class MarkupContext extends
> org.exoplatform.services.wsrp2.type.MimeResponse implements
> java.io.Serializable {
>
> public MarkupContext(
>java.lang.String ccppProfileWarning,
>java.lang.Boolean useCachedItem,
>java.lang.String preferredTitle) {
> super(
> ccppProfileWarning,
> useCachedItem);
> this.preferredTitle = preferredTitle;
> }
>
> Alexey.
>
> On Jan 24, 2008 6:27 PM, Alexey Zavizionov <[EMAIL PROTECTED]>
> wrote:
> > Hi,
> >
> > Please take a look at the issue.
> > That blocks my work!
> >
> > Thaks,
> > Alexey
> >
> > On Jul 10, 2007 10:05 AM, Alexey Zavizionov
> >
> > <[EMAIL PROTECTED]> wrote:
> > > Looks like a bug in axis1 1.4
> > >
> > > The class MimeResponse generated correctly with attribute
> > > "ccppProfileWarning" as last parameter in constructor, but
> > > MarkupContext generated wrong, IMHO, because MarkupContext call super
> > > constructor with first (should be last) parameter "ccppProfileWarning"
> > >
> > > Any approvement from axis team?
> > >
> > > Regards,
> > > Alexey
> > >
> > >
> > > On 7/9/07, Max Shaposhnik <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Hello,
> > > > trying to use Axis 1.4 for implementing some web service, but
> > > > got compile error as follows:
> > > >
> > > > part of wsdl schema:
> > > > ~~
> > > >
> > > >
> > > >> > > default="false" minOccurs="0"/>
> > > >> > > minOccurs="0"/>
> > > >> > > minOccurs="0"/>
> > > >> > > minOccurs="0"/>
> > > >> > > minOccurs="0"/>
> > > >> > > default="false" minOccurs="0"/>
> > > >> > > minOccurs="0"/>
> > > >> > > minOccurs="0" maxOccurs="unbounded"/>
> > > >
> > > > > > > use="optional"/>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >> > > minOccurs="0"/>
> > > >
> > > >
> > > >
> > > >
> > &
Re: Axis 1.4 WSDL4J wrong arguments sequence in generated classes
Hi,
WSDL2Java generates uncompilable code.
Classes that inherite from some parent classes have the constructor
parameters in the wrong order.
Example:
I have the exeption
/home/alexey/java/eXoProjects/portlet-container/trunk/component/plugins/wsrp2/target/generated/org/exoplatform/services/wsrp2/type/MarkupContext.java:[31,8]
cannot find symbol
symbol : constructor MimeResponse(java.lang.String,java.lang.Boolean)
location: class org.exoplatform.services.wsrp2.type.MimeResponse
Parent:
public class MimeResponse implements java.io.Serializable {
public MimeResponse(
java.lang.Boolean useCachedItem,
java.lang.String ccppProfileWarning) {
this.useCachedItem = useCachedItem;
this.ccppProfileWarning = ccppProfileWarning;
}
Child:
public class MarkupContext extends
org.exoplatform.services.wsrp2.type.MimeResponse implements
java.io.Serializable {
public MarkupContext(
java.lang.String ccppProfileWarning,
java.lang.Boolean useCachedItem,
java.lang.String preferredTitle) {
super(
ccppProfileWarning,
useCachedItem);
this.preferredTitle = preferredTitle;
}
Alexey.
On Jan 24, 2008 6:27 PM, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Please take a look at the issue.
> That blocks my work!
>
> Thaks,
> Alexey
>
> On Jul 10, 2007 10:05 AM, Alexey Zavizionov
>
> <[EMAIL PROTECTED]> wrote:
> > Looks like a bug in axis1 1.4
> >
> > The class MimeResponse generated correctly with attribute
> > "ccppProfileWarning" as last parameter in constructor, but
> > MarkupContext generated wrong, IMHO, because MarkupContext call super
> > constructor with first (should be last) parameter "ccppProfileWarning"
> >
> > Any approvement from axis team?
> >
> > Regards,
> > Alexey
> >
> >
> > On 7/9/07, Max Shaposhnik <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello,
> > > trying to use Axis 1.4 for implementing some web service, but
> > > got compile error as follows:
> > >
> > > part of wsdl schema:
> > > ~~
> > >
> > >
> > >> > default="false" minOccurs="0"/>
> > >> > minOccurs="0"/>
> > >> > minOccurs="0"/>
> > >> > minOccurs="0"/>
> > >> > minOccurs="0"/>
> > >> > default="false" minOccurs="0"/>
> > >> > minOccurs="0"/>
> > >> > minOccurs="0" maxOccurs="unbounded"/>
> > >
> > > > > use="optional"/>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> > minOccurs="0"/>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Output code ( look for super() constructor ):
> > >
> > >
> > > public class MarkupContext extends
> > > org.mycompany.services.wsrp.type.MimeResponse implements
> > > java.io.Serializable {
> > > private java.lang.String preferredTitle;
> > >
> > > public MarkupContext() {
> > > }
> > >
> > > public MarkupContext(
> > >java.lang.String ccppProfileWarning,
> > >java.lang.Boolean useCachedItem,
> > >java.lang.String mimeType,
> > >java.lang.String itemString,
> > >byte[] itemBinary,
> > >java.lang.String locale,
> > >java.lang.Boolean requiresRewriting,
> > >org.exoplatform.services.wsrp.type.CacheControl cacheControl,
> > >org.exoplatform.services.wsrp.type.Extension[] extensions,
> > >java.lang.String preferredTitle) {
> > > super(
> > > ccppProfileWarning,
> > > useCachedItem,
> > > mimeType,
> > > itemString,
> > > itemBinary,
> > > locale,
> > > requiresRewriting,
> > > cacheControl,
> > > extension
Re: Axis 1.4 WSDL4J wrong arguments sequence in generated classes
Hi,
Please take a look at the issue.
That blocks my work!
Thaks,
Alexey
On Jul 10, 2007 10:05 AM, Alexey Zavizionov
<[EMAIL PROTECTED]> wrote:
> Looks like a bug in axis1 1.4
>
> The class MimeResponse generated correctly with attribute
> "ccppProfileWarning" as last parameter in constructor, but
> MarkupContext generated wrong, IMHO, because MarkupContext call super
> constructor with first (should be last) parameter "ccppProfileWarning"
>
> Any approvement from axis team?
>
> Regards,
> Alexey
>
>
> On 7/9/07, Max Shaposhnik <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> > trying to use Axis 1.4 for implementing some web service, but
> > got compile error as follows:
> >
> > part of wsdl schema:
> > ~~
> >
> >
> >> default="false" minOccurs="0"/>
> >> minOccurs="0"/>
> >> minOccurs="0"/>
> >> minOccurs="0"/>
> >> minOccurs="0"/>
> >> default="false" minOccurs="0"/>
> >> minOccurs="0"/>
> >> minOccurs="0" maxOccurs="unbounded"/>
> >
> > > use="optional"/>
> >
> >
> >
> >
> >
> >
> >
> >> minOccurs="0"/>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Output code ( look for super() constructor ):
> >
> >
> > public class MarkupContext extends
> > org.mycompany.services.wsrp.type.MimeResponse implements
> > java.io.Serializable {
> > private java.lang.String preferredTitle;
> >
> > public MarkupContext() {
> > }
> >
> > public MarkupContext(
> >java.lang.String ccppProfileWarning,
> >java.lang.Boolean useCachedItem,
> >java.lang.String mimeType,
> >java.lang.String itemString,
> >byte[] itemBinary,
> >java.lang.String locale,
> >java.lang.Boolean requiresRewriting,
> >org.exoplatform.services.wsrp.type.CacheControl cacheControl,
> >org.exoplatform.services.wsrp.type.Extension[] extensions,
> >java.lang.String preferredTitle) {
> > super(
> > ccppProfileWarning,
> > useCachedItem,
> > mimeType,
> > itemString,
> > itemBinary,
> > locale,
> > requiresRewriting,
> > cacheControl,
> > extensions);
> > this.preferredTitle = preferredTitle;
> > }
> >
> >
> >
> > and here is MimeResponse constructor:
> >
> > public MimeResponse(
> >java.lang.Boolean useCachedItem,
> >java.lang.String mimeType,
> >java.lang.String itemString,
> >byte[] itemBinary,
> >java.lang.String locale,
> >java.lang.Boolean requiresRewriting,
> >org.exoplatform.services.wsrp.type.CacheControl cacheControl,
> >org.exoplatform.services.wsrp.type.Extension[] extensions,
> >java.lang.String ccppProfileWarning) {
> >this.useCachedItem = useCachedItem;
> >this.mimeType = mimeType;
> >this.itemString = itemString;
> >this.itemBinary = itemBinary;
> >this.locale = locale;
> >this.requiresRewriting = requiresRewriting;
> >this.cacheControl = cacheControl;
> >this.extensions = extensions;
> >this.ccppProfileWarning = ccppProfileWarning;
> > }
> >
> >
> >
> > As you can see, the sequence of arguments is not match. Is it inheritance
> > problem?
> > Tnx for any suggestions.
> >
> >
> > --
> > View this message in context:
> > http://www.nabble.com/Axis-1.4-WSDL4J-wrong-arguments-sequence-in-generated-classes-tf4049803.html#a11503152
> > Sent from the Axis - User mailing list archive at Nabble.com.
> >
> >
> > -
> > 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: How to debug the axis web service
Use code debugger on client (or server) with htto sniffer. Regards, Alexey On Jan 11, 2008 10:54 AM, tce tce <[EMAIL PROTECTED]> wrote: > Hi All, > > Is there any way to debug the axis web service when a dot.net client make a > request? > > Regards, > Thamizh P > > > > Chat on a cool, new interface. No download required. Click here. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: un-subscribe
Try to do reply to [EMAIL PROTECTED] . You may do that without subject and content. On 11/7/07, John McCosker <[EMAIL PROTECTED]> wrote: > > I can't seem to unsubscribe! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [wsrp-dev] AXIS1 Problem with generated sources: Params were mixed up within super constructor.
For now I see two solutions of this problem. One is to delete attributes in all conflicted superclasses. Another one is to remove inheritance (remove " ... ... ... ... == I think it is axis1 generation bug, isn't it? Can anyone provide solution for axis1? Thanks, Alexey On 10/24/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > Thanks for the quick reply. > > Just those which involving a field carried as an attribute. > > Regards, > Alexey > > On 10/23/07, Rich Thompson <[EMAIL PROTECTED]> wrote: > > Does this happen for all classes where we leveraged extends or just those > > also involving a field carried as an attribute? > > > > Rich Thompson > > OASIS WSRP TC Chair > > IBM T.J. Watson Research Center / Hawthorne, NY > > > > > > > > > > From: > > "Alexey Zavizionov" <[EMAIL PROTECTED]> > > To: > > axis-user@ws.apache.org, [EMAIL PROTECTED], "Roman Pedchenko" > > <[EMAIL PROTECTED]> > > Date: > > 10/23/2007 11:29 AM > > Subject: > > [wsrp-dev] AXIS1 Problem with generated sources: Params were mixed up > > within super constructor. > > > > > > > > Hello, > > > > I have a troble while building the sources generated by Axis1 1.4. > > There's a problem with super constructor, it looks like params were > > mixed up within. > > > > For example, there are two classes: one is MarkupContext which extends > > MimeResponse. > > > > Constructor of MimeResponse is generated in such a way that described > > attribute is at the end. > > But, constructor of MarkupContext invokes super with the attribute > > placed as a first param. > > > > == > > > > > >> default="false" minOccurs="0"/> > >> minOccurs="0"/> > >> minOccurs="0"/> > >> minOccurs="0"/> > >> minOccurs="0"/> > >> default="false" minOccurs="0"/> > >> minOccurs="0"/> > >> minOccurs="0"/> > >> minOccurs="0" maxOccurs="unbounded"/> > > > > > use="optional"/> > > > > > > > > > > > > > > > >> minOccurs="0"/> > >>minOccurs="0" maxOccurs="unbounded"/> > > > > > > > > > > > > == > > > > Regards, > > Alexey. > > > > - > > 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: [wsrp-dev] AXIS1 Problem with generated sources: Params were mixed up within super constructor.
Thanks for the quick reply. Just those which involving a field carried as an attribute. Regards, Alexey On 10/23/07, Rich Thompson <[EMAIL PROTECTED]> wrote: > Does this happen for all classes where we leveraged extends or just those > also involving a field carried as an attribute? > > Rich Thompson > OASIS WSRP TC Chair > IBM T.J. Watson Research Center / Hawthorne, NY > > > > > From: > "Alexey Zavizionov" <[EMAIL PROTECTED]> > To: > axis-user@ws.apache.org, [EMAIL PROTECTED], "Roman Pedchenko" > <[EMAIL PROTECTED]> > Date: > 10/23/2007 11:29 AM > Subject: > [wsrp-dev] AXIS1 Problem with generated sources: Params were mixed up > within super constructor. > > > > Hello, > > I have a troble while building the sources generated by Axis1 1.4. > There's a problem with super constructor, it looks like params were > mixed up within. > > For example, there are two classes: one is MarkupContext which extends > MimeResponse. > > Constructor of MimeResponse is generated in such a way that described > attribute is at the end. > But, constructor of MarkupContext invokes super with the attribute > placed as a first param. > > == > > >default="false" minOccurs="0"/> >minOccurs="0"/> >minOccurs="0"/> >minOccurs="0"/> >minOccurs="0"/> >default="false" minOccurs="0"/> >minOccurs="0"/> >minOccurs="0"/> >minOccurs="0" maxOccurs="unbounded"/> > > use="optional"/> > > > > > > > > minOccurs="0"/> > minOccurs="0" maxOccurs="unbounded"/> > > > > > > == > > Regards, > Alexey. > > - > 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]
AXIS1 Problem with generated sources: Params were mixed up within super constructor.
Hello, I have a troble while building the sources generated by Axis1 1.4. There's a problem with super constructor, it looks like params were mixed up within. For example, there are two classes: one is MarkupContext which extends MimeResponse. Constructor of MimeResponse is generated in such a way that described attribute is at the end. But, constructor of MarkupContext invokes super with the attribute placed as a first param. == == Regards, Alexey. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No serializer found for class in registry TypeMappingDelegate
Hello, Jeff Sorry for the late reply. I was impressed with your long and understandable answer to my incomprehensible question . By now I have solved the problem. --- Need to serialize (marshal) event Object to Document and then create MessageElement with it. On the other side deserialize (unmarshal) it direct to MessageElement. --- Thanks and regards, Alexey. On 10/10/07, Walker, Jeff <[EMAIL PROTECTED]> wrote: > Alexey, > Let's step back for a minute. I'm confused as to your system setup. > Let's go over the basics of Axis1-1.4 first. > > Assuming you started with a wsdl file first (Top-Down approach) and also > assuming you are creating a Document/Literal based wsdl, you must create > XML Schema for every Java class that you intend to send over the > service. Therefore, the MyEventPub class (which I take it you are trying > to send over the wire) must have equivalent XML Schema created for it, > or at least imported from an external xsd file into your wsdl file. > Therefore, to send it over the wire, you need to know the structure of > this class in advance (so that you can write schema for it). > > The WSDL2Java generator will read the schema in the wsdl and essentially > create two classes for each element/complexType it finds. One is to > serialize the class (put it into xml) the other is to deserialize it > (take it from xml and back into a Java object). This is a simplified > view of the process, but it is essentially correct. > > Also generated for you, is a deploy.wsdd file. In the deploy.wsdd file, > there are some namespace declarations. And then a section that describes > the service, such as what methods are exposed publicly, the port name > (which is the name of the web service), the name of your skeleton class > (which is used by Axis to make sure the correct operation is called on > your interface), and so on. Further down in deploy.wsdd there are type > mappings. This is where Axis learns about the classes that can be > serialized/deserialized. Each type mapping essentially holds a qualified > namespace, the type of object your transferring (that is, the package > and name of your class), and the names of the serializer and > deserializer classes that will do the work for that type. > > Now, your original post hinted that a type mapping was missing from the > wsdd file, for the MyEventPub class. There maybe some strange situations > where a type mapping may not be created by the generator, even though > the MyEventPub class has an schema equivalent in the wsdl file. But I > suspected (in my first reply) that the problem was that you did not > create any schema for MyEventPub in the first place and so Axis had no > way of knowing how to serialize/deserialize it. Hence, the type mapping > exception. > > Now, your following question asks where can you 'store' MyEventPub > within MessageElement. The problem here, is that your hinting at trying > to construct the soap parse tree yourself, and then presumably serialize > that tree (with the MyEventPub fields in it somewhere). I strongly > recommend that you do not approach your web service from this angle. I > cannot help you further with this direction. (Perhaps you have previous > experience with RPC-encoded services and serializing graphs of objects? > If not, then this approach will be a difficult task indeed). > > I recommend you define MyEventPub in schema (in the wsdl) and let Axis > do 95% of the work for you. I also recommend that you adopt the > Document/Literal-Wrapped wsdl format (go here to learn about it: > http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/), > and abandon any attempt at an RPC service. You will get virtually no > help from this mailing list if you choose to continue with an RPC-based > wsdl. (That is because a wsdl based on RPC is essentially deprecated as > a web service design, and nobody does web services like that anymore. > Why not?Because RPC-Encoded is not WSI compliant. There is no standard > way to interpret the serialize object graph across every platform that > could conceivably call your service). > > In Document Literal-Wrapped, the methods on your interface take a single > object and return a single object. Those two objects can obviously have > multiple objects within them. Each object is based on schema in your > wsdl. This is the approach everybody else takes with web services these > days. > > One more thing. There are only a few of us left still using Axis1.4 on > our projects. Nearly all subscribers of the Axis mailing list are using > Axis2. You cannot use Axis2 to do an RPC Encoded service. > Does any of this help? > -jeff > > > > -Original Message- > From: Alexey Zavizionov [mailto:[EMAIL PROTECTED] >
Re: axis1 Runtime object creation on server
[SOLVED] Need to serialize (marshal) it to Document and then create MessageElement with it. On the other side deserialize (unmarshal) it direct to MessageElement. Regards, Alexey On 10/6/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > Hello list! > > I wont to know what shold I do to be able server store within > "org.apache.axis.message.MessageElement" any runtime generated object > for client? > > Any changes on client? > > Thanks, > Alexey > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No serializer found for class in registry TypeMappingDelegate
Thanks for reply! This MyEventPub is the sample user's class fired as event on server at runtime, therefore I don't know about before. How can I marshal this with JAXB for MessageElement ? I mean this MyEventPub is well annotated class and well marshalled to StringWriter(). Where can I store it within MessageElement? Please, advise me. Alexey. On 10/5/07, Walker, Jeff <[EMAIL PROTECTED]> wrote: > I think your missing a type mapping in the wsdd file. > You need something like this inserted. (deploy.wsdd file:) > ... > xmlns:ns="http://www.company.com/project"; > qname="ns:MyEventPub" > > type="java:org.exoplatform.services.portletcontainer.test.portlet2.MyEve > ntPub" > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" > > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" > encodingStyle="" > /> > ... > > The real question is, why do you not have it? > If you ran your wsdl file through the generator, the stubs and skeleton > code gets created for you. This command also generates the deploy.wsdd > file and should add in all of the type mappings you need for your > classes. > > %>java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy > true WebServiceName.wsdl > > -jeff > > > > -Original Message- > From: Alexey Zavizionov [mailto:[EMAIL PROTECTED] > Sent: Friday, October 05, 2007 12:31 PM > To: axis-user@ws.apache.org > Subject: No serializer found for class in registry TypeMappingDelegate > > Hello list! > > I have an exc on server of my service: > [ERROR] BeanSerializer - Exception: serializer found for class > org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in > registry > [EMAIL PROTECTED]>java.io.IOException: > No serializer found for class > org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in > registry [EMAIL PROTECTED] > at > org.apache.axis.encoding.SerializationContext.serializeActual(Serializat > ionContext.java:1507) > ... > > What could this be? > > PS: I use Axis1-1.4 > > Thanks, > Alexey > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis1 Runtime object creation on server
Hello list! I wont to know what shold I do to be able server store within "org.apache.axis.message.MessageElement" any runtime generated object for client? Any changes on client? Thanks, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No serializer found for class in registry TypeMappingDelegate
I use wsdl file form wsrp v2 spec. http://docs.oasis-open.org/wsrp/v2/wsrp-service.wsdl That class MyEventPub is sample user's class which should be getting by client from server. deploy.wsdd genegates by axis, for this step I don't know what is the class on server user will be stored for client within event mechanism. How can I fix it? Thanks for quikly response, Alexey On 10/5/07, Walker, Jeff <[EMAIL PROTECTED]> wrote: > I think your missing a type mapping in the wsdd file. > You need something like this inserted. (deploy.wsdd file:) > ... > xmlns:ns="http://www.company.com/project"; > qname="ns:MyEventPub" > > type="java:org.exoplatform.services.portletcontainer.test.portlet2.MyEve > ntPub" > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" > > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" > encodingStyle="" > /> > ... > > The real question is, why do you not have it? > If you ran your wsdl file through the generator, the stubs and skeleton > code gets created for you. This command also generates the deploy.wsdd > file and should add in all of the type mappings you need for your > classes. > > %>java org.apache.axis.wsdl.WSDL2Java --server-side --skeletonDeploy > true WebServiceName.wsdl > > -jeff > > > > -Original Message- > From: Alexey Zavizionov [mailto:[EMAIL PROTECTED] > Sent: Friday, October 05, 2007 12:31 PM > To: axis-user@ws.apache.org > Subject: No serializer found for class in registry TypeMappingDelegate > > Hello list! > > I have an exc on server of my service: > [ERROR] BeanSerializer - Exception: serializer found for class > org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in > registry > [EMAIL PROTECTED]>java.io.IOException: > No serializer found for class > org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in > registry [EMAIL PROTECTED] > at > org.apache.axis.encoding.SerializationContext.serializeActual(Serializat > ionContext.java:1507) > ... > > What could this be? > > PS: I use Axis1-1.4 > > Thanks, > Alexey > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
No serializer found for class in registry TypeMappingDelegate
Hello list! I have an exc on server of my service: [ERROR] BeanSerializer - Exception: java.io.IOException: No serializer found for class org.exoplatform.services.portletcontainer.test.portlet2.MyEventPub in registry [EMAIL PROTECTED] at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1507) ... What could this be? PS: I use Axis1-1.4 Thanks, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.4 WSDL4J wrong arguments sequence in generated classes
Looks like a bug in axis1 1.4
The class MimeResponse generated correctly with attribute
"ccppProfileWarning" as last parameter in constructor, but
MarkupContext generated wrong, IMHO, because MarkupContext call super
constructor with first (should be last) parameter "ccppProfileWarning"
Any approvement from axis team?
Regards,
Alexey
On 7/9/07, Max Shaposhnik <[EMAIL PROTECTED]> wrote:
Hello,
trying to use Axis 1.4 for implementing some web service, but
got compile error as follows:
part of wsdl schema:
~~
Output code ( look for super() constructor ):
public class MarkupContext extends
org.mycompany.services.wsrp.type.MimeResponse implements
java.io.Serializable {
private java.lang.String preferredTitle;
public MarkupContext() {
}
public MarkupContext(
java.lang.String ccppProfileWarning,
java.lang.Boolean useCachedItem,
java.lang.String mimeType,
java.lang.String itemString,
byte[] itemBinary,
java.lang.String locale,
java.lang.Boolean requiresRewriting,
org.exoplatform.services.wsrp.type.CacheControl cacheControl,
org.exoplatform.services.wsrp.type.Extension[] extensions,
java.lang.String preferredTitle) {
super(
ccppProfileWarning,
useCachedItem,
mimeType,
itemString,
itemBinary,
locale,
requiresRewriting,
cacheControl,
extensions);
this.preferredTitle = preferredTitle;
}
and here is MimeResponse constructor:
public MimeResponse(
java.lang.Boolean useCachedItem,
java.lang.String mimeType,
java.lang.String itemString,
byte[] itemBinary,
java.lang.String locale,
java.lang.Boolean requiresRewriting,
org.exoplatform.services.wsrp.type.CacheControl cacheControl,
org.exoplatform.services.wsrp.type.Extension[] extensions,
java.lang.String ccppProfileWarning) {
this.useCachedItem = useCachedItem;
this.mimeType = mimeType;
this.itemString = itemString;
this.itemBinary = itemBinary;
this.locale = locale;
this.requiresRewriting = requiresRewriting;
this.cacheControl = cacheControl;
this.extensions = extensions;
this.ccppProfileWarning = ccppProfileWarning;
}
As you can see, the sequence of arguments is not match. Is it inheritance
problem?
Tnx for any suggestions.
--
View this message in context:
http://www.nabble.com/Axis-1.4-WSDL4J-wrong-arguments-sequence-in-generated-classes-tf4049803.html#a11503152
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.2 release notes
I have just found it on web at http://svn.apache.org/viewvc/webservices/axis2/tags/java/v1.2/release-notes.html?view=markup Regards, Alexey On 7/6/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: Hi, Where I can found out release notes? I want to see all features that axis2 1.2 has. Thank, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 1.2 release notes
Hi, Where I can found out release notes? I want to see all features that axis2 1.2 has. Thank, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NullPointerException with axis1 1.4
Thanks for all responses, I solved this problem, it is my code problem:) Thanks again, Alexey On 7/3/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: Thanks for your reply, I am researching it now. btw, I don't use .NET Regards, Alexey On 7/3/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > I Googled "wsrp axis null pointer exception getServiceDescription" and found > a reference to a problem with sending a null to .NET. What happens if you > send a value (as opposed to nil="true") in the > element? > > Anne > > > On 7/2/07, Alexey Zavizionov > <[EMAIL PROTECTED]> wrote: > > > > Thanks for your response! > > > > We implemented WSRP service on axis1 1.2-RC1, but now we start to > > using axis1 1.4. > > > > WSRP service has the wsdl file from oasis ( "wsrp_service.wsdl" > > from > http://www.oasis-open.org/committees/wsrp/specifications/version1/ > > ) > > > > > http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl > > ---WSDL--- > > > > targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl" > > > xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind" > > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/ " > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> > >> location="wsrp_v1_bindings.wsdl"/> > > > > > name="WSRPBaseService"> > >location="http://my.service:8080/WSRPService"/> > > > > binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP" > > name="WSRPServiceDescriptionService"> > >location="http://my.service:8080/WSRPService"/> > > > > binding="bind:WSRP_v1_Registration_Binding_SOAP" > > name="WSRPRegistrationService"> > >location="http://my.service:8080/WSRPService"/> > > > > binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" > > name="WSRPPortletManagementService"> > >location="http://my.service:8080/WSRPService"/> > > > > > > > > -- > > > > Do you know where cause of this problem? > > > > Alexey > > > > > > > > On 6/27/07, Martin Gainty <[EMAIL PROTECTED] > wrote: > > > Alexey > > > > > > please post the wsdl > > > > > > Thanks > > > M-- > > > This email message and any files transmitted with it contain > confidential > > > information intended only for the person(s) to whom this email message > is > > > addressed. If you have received this email message in error, please > notify > > > the sender immediately by telephone or email and destroy the original > > > message without making a copy. Thank you. > > > > > > - Original Message - > > > From: "Alexey Zavizionov" > <[EMAIL PROTECTED]> > > > To: < axis-user@ws.apache.org> > > > Sent: Wednesday, June 27, 2007 11:10 AM > > > Subject: Re: NullPointerException with axis1 1.4 > > > > > > > > > >I catch the soap message: > > > > > > > > POST /portal/services/WSRPServiceDescriptionService > HTTP/1.0 > > > > Content-Type: text/xml; charset=utf-8 > > > > Accept: application/soap+xml, application/dime, multipart/related, > text/* > > > > User-Agent: Axis/1.4 > > > > Host: localhost:8080 > > > > Cache-Control: no-cache > > > > Pragma: no-cache > > > > SOAPAction: > "urn:oasis:names:tc:wsrp:v1:getServiceDescription" > > > > Content-Length: 421 > > > > > > > > > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > > xmlns:xsd=" http://www.w3.org/2001/XMLSchema"; > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > xmlns="urn:oasis:names:tc:wsrp:v1:types"> > > > > > > > > en > > > > > > > > > > > > > > > > > > > > HTTP/1.1 500 Internal Server Error > > > > Server: Apache-Coyote/1.1 > > > > Set-Cookie: > JSESSIONID=D8D788AB8D4D347C7C65F5C3B3
Re: Which databinding axis1 has?
Thanks for your response! Alexey On 7/3/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: Axis uses it's own internal databinding system (referred to as de/serialization) that's based on SAX. It is not a pluggable option. (Perhaps you've seen messages such as "no deserialized found for [qname]). Axis provides built-in de/serializers for beans and arrays, and you can provide custom de/serializers for other types. You specify the de/serializers to use, and the mapping between qnames and types in the WSDD using the beanMapping and typeMapping options. If you want to use a third-party databinding system, then you must use the low-level message provider (provider="MSG"), which deserializes the message into DOM, which you can then bind to your object model. Anne On 7/3/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: > I think it has xmlbeans support. > > Thanks > Deepal > > Alexey Zavizionov wrote: > > Hello, > > > > I googled, read docs and searched in sources, but found nothing about > > what databinding for WSDL2Java axis1 uses? > > > > Alexey > > > > > > - > 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: NullPointerException with axis1 1.4
Thanks for your reply, I am researching it now. btw, I don't use .NET Regards, Alexey On 7/3/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: I Googled "wsrp axis null pointer exception getServiceDescription" and found a reference to a problem with sending a null to .NET. What happens if you send a value (as opposed to nil="true") in the element? Anne On 7/2/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > > Thanks for your response! > > We implemented WSRP service on axis1 1.2-RC1, but now we start to > using axis1 1.4. > > WSRP service has the wsdl file from oasis ( "wsrp_service.wsdl" > from http://www.oasis-open.org/committees/wsrp/specifications/version1/ > ) > > http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl > ---WSDL--- > > xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind" > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/ " > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";> > location="wsrp_v1_bindings.wsdl"/> > > name="WSRPBaseService"> > http://my.service:8080/WSRPService"/> > > name="WSRPServiceDescriptionService"> > http://my.service:8080/WSRPService"/> > > name="WSRPRegistrationService"> > http://my.service:8080/WSRPService"/> > > name="WSRPPortletManagementService"> > http://my.service:8080/WSRPService"/> > > > > -- > > Do you know where cause of this problem? > > Alexey > > > > On 6/27/07, Martin Gainty <[EMAIL PROTECTED] > wrote: > > Alexey > > > > please post the wsdl > > > > Thanks > > M-- > > This email message and any files transmitted with it contain confidential > > information intended only for the person(s) to whom this email message is > > addressed. If you have received this email message in error, please notify > > the sender immediately by telephone or email and destroy the original > > message without making a copy. Thank you. > > > > - Original Message - > > From: "Alexey Zavizionov" <[EMAIL PROTECTED]> > > To: < axis-user@ws.apache.org> > > Sent: Wednesday, June 27, 2007 11:10 AM > > Subject: Re: NullPointerException with axis1 1.4 > > > > > > >I catch the soap message: > > > > > > POST /portal/services/WSRPServiceDescriptionService HTTP/1.0 > > > Content-Type: text/xml; charset=utf-8 > > > Accept: application/soap+xml, application/dime, multipart/related, text/* > > > User-Agent: Axis/1.4 > > > Host: localhost:8080 > > > Cache-Control: no-cache > > > Pragma: no-cache > > > SOAPAction: "urn:oasis:names:tc:wsrp:v1:getServiceDescription" > > > Content-Length: 421 > > > > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd=" http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > > > en > > > > > > > > > > > > > > > HTTP/1.1 500 Internal Server Error > > > Server: Apache-Coyote/1.1 > > > Set-Cookie: JSESSIONID=D8D788AB8D4D347C7C65F5C3B3FAE75D; Path=/portal > > > Content-Type: text/xml;charset=utf-8 > > > Date: Wed, 27 Jun 2007 15:05:28 GMT > > > Connection: close > > > > > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > > xmlns:xsd=" http://www.w3.org/2001/XMLSchema"; > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > soapenv:Server.userException > > > java.lang.NullPointerException > > > > > > > > xmlns:ns1="http://xml.apache.org/axis/";>Alex > > > > > > > > > > > > > > > > > > > > > Any idea are appreciable! > > > > > > Regards, > > > Alexey > > > > > > > > > On 6/27/07, Alexey Zavizionov < [EMAIL PROTECTED]> > > > wrote: > > >> Hello, > > >> I am using axis1 version 1.4 for wsrp service. > > >> > > >> I have an exc: > &
Re: [jira] Commented: (AXIS2-1435) Can't generate code for more than one interface using wsdl2java
Hi,
I cannot reopen issue and cannot vote on resolved issues. I hear
nothing from owner of the jira bug. I really want to use axis2, but
some bugs really blocked my future work with it.
Thats simplier task to generate code takes much more times than I thought.
Thanks,
Alexey
On 7/3/07, Jess Fisher <[EMAIL PROTECTED]> wrote:
Yes, you need to manually change name. I know this is not pretty at all. But
this Axis bug for Axis2 is still not yet fixed. I see you added a note in
the jira to re-open the bug. Any response from the owner of the jira bug? We
are not the only one experiencing this problem. The Axis2 user group have a
few people who have encountered this problem
Alexey Zavizionov <[EMAIL PROTECTED]>
wrote:
Hello, Jess
Thanks for your response
For me, manually run wsdl2java multiple times looks unfriendly,
because I should manually change name of port interface for geregated
service (reason: for all ports it's same name).
Why wsdl2java can't generate sources for all ports by default?
Regards,
Alexey
On 7/2/07, Jess Fisher wrote:
> Yeah, I tried the Axis2 1.2 version nightly and it's still not fixed.
> I had to manually run wsdl2java multiple times - for each port to get all
> the stubs and skeletons created. This was not a problem in Axis1.4
>
> "Alexey Zavizionov (JIRA)" wrote:
>
> [
>
https://issues.apache.org/jira/browse/AXIS2-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507176
> ]
>
> Alexey Zavizionov commented on AXIS2-1435:
> --
>
> I use command line
>
> -s -ss -sd -ssi -g -d none -t -o ${src.gen.dir} -ns2p
>
urn:oasis:names:tc:wsrp:v1:intf=org.exoplatform.services.wsrp.intf,urn:oasis:names:tc:wsrp:v1:types=org.exoplatform.services.wsrp.type,urn:oasis:names:tc:wsrp:v1:bind=org.exoplatform.services.wsrp.bind,urn:oasis:names:tc:wsrp:v1:wsdl=org.exoplatform.services.wsrp.wsdl
> -p org.exoplatform.services.wsrp.wsdl -uri
> wsrp_service.wsdl
>
> > Can't generate code for more than one interface using wsdl2java
> >
>
---
> >
> > Key: AXIS2-1435
> > URL: https://issues.apache.org/jira/browse/AXIS2-1435
> > Project: Axis 2.0 (Axis2)
> > Issue Type: Bug
> > Components: codegen
> > Affects Versions: 1.1
> > Environment: Sun JDK 1.5, WinXP
> > Reporter: yogen
> > Assignee: Amila Chinthaka Suriarachchi
> >
> > I am using wsdl2java to generate code for WSRP WSDL, find WSDL at this
> location:
> >
>
https://svn.apache.org/repos/asf/portals/wsrp4j/trunk/wsdl
> > Ideally, command
> > >wsdl2java -d xmlbeans -p com.sample -ss -sd -g -uri wsrp_service.wsdl
> > should generate code for all the interfaces in WSDL but wsdl2java
randomly
> picks up anyone interface and generates the code for it.
> > When its run subsequently to generate code for other interfaces, it says
> "INFO: File .\src\com\sample\WSRPServiceStub.java will
not
> be overwritten."
> > C:\work\WSRP>wsdl2java -d adb -p com.sample -ss -sd -g -uri
> wsrp_service.wsdl -pn WSRPServiceDescriptionService
> > Using AXIS2_HOME: C:\software\axis2-rc1
> > Using JAVA_HOME: //ms/dist/msjava/PROJ/sunjdk/1.5.0_04
> > Retrieving document at 'wsrp_v1_bindings.wsdl', relative to
> 'file:/C:/work/WSRP/'.
> > Retrieving document at 'wsrp_v1_interfaces.wsdl', relative to
> 'file:/C:/work/WSRP/wsrp_v1_bindings.wsdl'.
> > Retrieving schema at 'wsrp_v1_types.xsd', relative to
> 'file:/C:/work/WSRP/wsrp_v1_interfaces.wsdl'.
> > Retrieving schema at 'xml.xsd', relative to
> 'file:/C:/work/WSRP/wsrp_v1_types.xsd'.
> > Oct 17, 2006 2:42:06 PM
> org.apache.axis2.wsdl.codegen.writer.ClassWriter
> createOutFile
> > INFO: File .\src\com\sample\WSRPServiceSkeleton.java
will
> not be overwritten.
> > Oct 17, 2006 2:42:06 PM
> org.apache.axis2.wsdl.codegen.writer.ClassWriter
> createOutFile
> > INFO: File
> .\src\com\sample\WSRPServiceMessageReceiverInOut.java
will
> not be overwritten.
> > Oct 17, 2006 2:42:06 PM
> org.apache.axis2.wsdl.codegen.writer.ClassWriter
> createOutFile
> > INFO: File
> .\src\com\sample\InvalidRegistrationException.java will
not
> be overwritten.
> > Oct 17, 2006 2:42:06 PM
> org.apache.axis2.wsdl.codegen.writer.ClassWriter
> createOutFile
> > INFO: File
.\src\com\sample\OperationFailedException.java
> will not be overwritten.
> > Oct 17, 2006 2:42:06 PM
> org.apache.axis2.wsdl.codegen.writer.ClassWriter
> createOutFile
> > INFO: File
> .\src\com\sample\WSRPServiceCallbackHandler.java will not
> be overwritten.
Which databinding axis1 has?
Hello, I googled, read docs and searched in sources, but found nothing about what databinding for WSDL2Java axis1 uses? Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NullPointerException with axis1 1.4
Thanks for your response!
We implemented WSRP service on axis1 1.2-RC1, but now we start to
using axis1 1.4.
WSRP service has the wsdl file from oasis ( "wsrp_service.wsdl"
from http://www.oasis-open.org/committees/wsrp/specifications/version1/
)
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
---WSDL---
http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
http://my.service:8080/WSRPService"/>
http://my.service:8080/WSRPService"/>
http://my.service:8080/WSRPService"/>
http://my.service:8080/WSRPService"/>
--
Do you know where cause of this problem?
Alexey
On 6/27/07, Martin Gainty <[EMAIL PROTECTED]> wrote:
Alexey
please post the wsdl
Thanks
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: "Alexey Zavizionov" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, June 27, 2007 11:10 AM
Subject: Re: NullPointerException with axis1 1.4
>I catch the soap message:
>
> POST /portal/services/WSRPServiceDescriptionService HTTP/1.0
> Content-Type: text/xml; charset=utf-8
> Accept: application/soap+xml, application/dime, multipart/related, text/*
> User-Agent: Axis/1.4
> Host: localhost:8080
> Cache-Control: no-cache
> Pragma: no-cache
> SOAPAction: "urn:oasis:names:tc:wsrp:v1:getServiceDescription"
> Content-Length: 421
>
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
>
> en
>
>
>
>
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Set-Cookie: JSESSIONID=D8D788AB8D4D347C7C65F5C3B3FAE75D; Path=/portal
> Content-Type: text/xml;charset=utf-8
> Date: Wed, 27 Jun 2007 15:05:28 GMT
> Connection: close
>
>
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>
>
> soapenv:Server.userException
> java.lang.NullPointerException
>
> xmlns:ns1="http://xml.apache.org/axis/";>Alex
>
>
>
>
>
>
> Any idea are appreciable!
>
> Regards,
> Alexey
>
>
> On 6/27/07, Alexey Zavizionov <[EMAIL PROTECTED]>
> wrote:
>> Hello,
>> I am using axis1 version 1.4 for wsrp service.
>>
>> I have an exc:
>>
>> AxisFault
>> faultCode:
>> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>> faultSubcode:
>> faultString: java.lang.NullPointerException
>> faultActor:
>> faultNode:
>> faultDetail:
>> {http://xml.apache.org/axis/}hostname:Alex
>>
>> java.lang.NullPointerException
>> at
>>
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>> at
>>
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>> at
>>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
>> Source)
>> at
>>
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>> Source)
>> at
>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>> Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>> Source)
>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>> Source)
>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
>> Source)
>> at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
>> at
>>
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>> at org.apache.axis.
Re: WSDL2java default stub generation.
Hello, I think that by default should be generated all ports for all services. And with option you may choose which ports for wich services will be generated. Thanks, Alexey On 6/28/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: hi all, currently wsdl2java generate stubs for all the ports in all the services unless user has restricted to generate the code for a particular service or a particular port. As a result of this generated stub names are long and it seems a lot of people don't happy with this. For this problem paul has suggested a solution in [1]. For an example lets say we have two services like this, for this currently we have Service1Port1Stub.java Service1Port2Stub.java Service2Port1Stub.java Service2Port2Stub.java And the new proposal suggest to generate only Service1Stub.java --> for Port1 in Service1 Service2Stub.java --> for Port1 in Service2 (here I assume it is reasonable to generate a Stub for each service although it is not explicitly specified in the proposal) the priority order for pick a port within the service is depends on the ports binding type. the order is Soap12, Soap11 and http. And give a seperate -all option to generate code as in now if user requried. Please comment on this. If someone dose not oppose I'll go ahead and do this change. thanks, Amila. [1] https://issues.apache.org/jira/browse/AXIS2-2831 -- Amila Suriarachchi, WSO2 Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: NullPointerException with axis1 1.4
org.apache.axis.wsdl.fromJava.Emitter.writeResponseMessage(Emitter.java:1752) at org.apache.axis.wsdl.fromJava.Emitter.writeMessages(Emitter.java:1121) at org.apache.axis.wsdl.fromJava.Emitter.writePortType(Emitter.java:1075) at org.apache.axis.wsdl.fromJava.Emitter.getWSDL(Emitter.java:484) at org.apache.axis.wsdl.fromJava.Emitter.emit(Emitter.java:331) at org.apache.axis.providers.BasicProvider.generateWSDL(BasicProvider.java:242) at org.apache.axis.strategies.WSDLGenStrategy.visit(WSDLGenStrategy.java:33) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.generateWSDL(SimpleChain.java:104) at org.apache.axis.handlers.soap.SOAPService.generateWSDL(SOAPService.java:320) at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:482) at org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.java:1226) at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:249) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.exoplatform.filter.AxisFilter.doFilter(AxisFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Thanks for any help Alexey On 6/27/07, Martin Gainty <[EMAIL PROTECTED]> wrote: Alexey please post the wsdl Thanks M-- This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: "Alexey Zavizionov" <[EMAIL PROTECTED]> To: Sent: Wednesday, June 27, 2007 11:10 AM Subject: Re: NullPointerException with axis1 1.4 >I catch the soap message: > > POST /portal/services/WSRPServiceDescriptionService HTTP/1.0 > Content-Type: text/xml; charset=utf-8 > Accept: application/soap+xml, application/dime, multipart/related, text/* > User-Agent: Axis/1.4 > Host: localhost:8080 > Cache-Control: no-cache > Pragma: no-cache > SOAPAction: "urn:oasis:names:tc:wsrp:v1:getServiceDescription" > Content-Length: 421 > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > en > > > > > HTTP/1.1 500 Internal Server Error > Server: Apache-Coyote/1.1 > Set-Cookie: JSESSIONID=D8D788AB8D4D347C7C65F5C3B3FAE75D; Path=/portal > Content-Type: text/xml;charset=utf-8 > Date: Wed, 27 Jun 2007 15:05:28 GMT > Connection: close > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >
Re: NullPointerException with axis1 1.4
I catch the soap message:
POST /portal/services/WSRPServiceDescriptionService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: localhost:8080
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "urn:oasis:names:tc:wsrp:v1:getServiceDescription"
Content-Length: 421
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
en
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=D8D788AB8D4D347C7C65F5C3B3FAE75D; Path=/portal
Content-Type: text/xml;charset=utf-8
Date: Wed, 27 Jun 2007 15:05:28 GMT
Connection: close
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
soapenv:Server.userException
java.lang.NullPointerException
http://xml.apache.org/axis/";>Alex
Any idea are appreciable!
Regards,
Alexey
On 6/27/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
Hello,
I am using axis1 version 1.4 for wsrp service.
I have an exc:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NullPointerException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:Alex
java.lang.NullPointerException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
org.exoplatform.services.wsrp.bind.WSRP_v1_ServiceDescription_Binding_SOAPStub.getServiceDescription(WSRP_v1_ServiceDescription_Binding_SOA
PStub.java:728)
at
org.exoplatform.services.wsrp.consumer.impl.ProducerImpl.updateServiceDescription(ProducerImpl.java:170)
at
org.exoplatform.services.wsrp.consumer.impl.ProducerImpl.isRegistrationRequired(ProducerImpl.java:257)
at
org.exoplatform.services.wsrp.consumer.portlets.WSRPAdminPortlet.processAction(WSRPAdminPortlet.java:246)
at
org.exoplatform.services.wsrp.consumer.WSRPConsumerPlugin.processAction(WSRPConsumerPlugin.java:329)
at
org.exoplatform.services.portletcontainer.impl.PortletContainerServiceImpl.processAction(PortletContainerServiceImpl.java:169)
at
org.exoplatform.frameworks.portletcontainer.portalframework.PortalFramework.processAction(PortalFramework.java:439)
at
org.exoplatform.services.portletcontainer.test.filters.PortletFilter.doFilter(PortletFilter.java:196)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.c
NullPointerException with axis1 1.4
Hello,
I am using axis1 version 1.4 for wsrp service.
I have an exc:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.NullPointerException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:Alex
java.lang.NullPointerException
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
org.exoplatform.services.wsrp.bind.WSRP_v1_ServiceDescription_Binding_SOAPStub.getServiceDescription(WSRP_v1_ServiceDescription_Binding_SOA
PStub.java:728)
at
org.exoplatform.services.wsrp.consumer.impl.ProducerImpl.updateServiceDescription(ProducerImpl.java:170)
at
org.exoplatform.services.wsrp.consumer.impl.ProducerImpl.isRegistrationRequired(ProducerImpl.java:257)
at
org.exoplatform.services.wsrp.consumer.portlets.WSRPAdminPortlet.processAction(WSRPAdminPortlet.java:246)
at
org.exoplatform.services.wsrp.consumer.WSRPConsumerPlugin.processAction(WSRPConsumerPlugin.java:329)
at
org.exoplatform.services.portletcontainer.impl.PortletContainerServiceImpl.processAction(PortletContainerServiceImpl.java:169)
at
org.exoplatform.frameworks.portletcontainer.portalframework.PortalFramework.processAction(PortalFramework.java:439)
at
org.exoplatform.services.portletcontainer.test.filters.PortletFilter.doFilter(PortletFilter.java:196)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
-
Could you help me why it hapens?
Thanks in advance,
Alexey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] StAX error when using WSDL2Java?
Hi, I think cause of it maybe wrong deps. Which virsion of axis do you use? Regards, Alexey On 6/26/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Is this from the command line wsdl2java bat/sh? thanks, dims On 6/26/07, Robert Whitehead <[EMAIL PROTECTED]> wrote: > Hi Axis2 users. > > I've been developing with Axis2 for a while. I've been creating services > with WSDL2Java for some WSDLs given to me some time ago and I had no > problems at all. Right now I'm using again WSDL2Java with a self made WSDL > which Eclipse validates but this time I can't get a compilation and I get an > error like this: > > Exception in thread main: java.lang.NoSuchMethodError: > javax.xml.stream.XMLOutputFactory.newInstance(Ljava/lang/String;Ljava/lang/ClassLoader;)Ljavax/xml/stream/XMLOutputFactory; > at org.apache.axiom.om.util.StAXUtils.getXMLOutputFactory > (StAXUtils.java:97) > at > org.apache.axiom.om.util.StAXUtils.createXMLStreamWriter(StAXUtils.java:111) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:381) > at org.apache.axis2.description.AxisService.getWSDL > (AxisService.java:732) > > etc... > > Any ideas? Thanks in advance. > > Robert. > -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for
Thanks, I can invoke the codegen multiple times to generate the code for all ports, but the name of each interfaces will be similar like "WSRPServiceSkeletonInterface". Regards, Alexey On 6/24/07, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi, From a glance at the WSDL I feel that you can use the code generator to generate multiple stubs for the different porttypes and still use it. I believe even if the codegen had the ability to handle multiple ports, it would have done the same thing, the difference in this case is that you have to invoke the codegen multiple times to generate the code for all ports. Ajith On 6/23/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > Hi, > I really haven't time in my wsrp implementation and this impossibility > for multiple porttypes blocked my project. This leads me to seek other > soap implementations... :( > > Will be fix it soon? > When will be the next release? > > Regards, > Alexey > > On 6/22/07, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > > Hi, > > You can use -pn, -sn options to specify the different port/service > > combinations. As for the point raised by Kim, yes it is a problem > > since now each port will yield a different service. Really this > > becomes a issue when you have multiple bindings and multiple > > porttypes. > > > > Ajith > > > > On 6/22/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > > > How can I do "generate code for each port with separate WSDL2Java > > > calls" if I can't modify wsdl file, because it was given by wsrp > > > specification http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl > > > ? > > > > > > Regards, > > > Alexey > > > > > > > > > On 6/22/07, Sagnwoo Kim <[EMAIL PROTECTED]> wrote: > > > > Ajith suggested multiple wsdl files for the solution of multiple ports. I > > > > have a question for that. When you want to create client from the wsdl > > > > files. with WSDL2Java and if you have multiple wsdl files for one service. > > > > Then you have to create multiple clients as well for every ports? Even > > > > though they are all under the same service? > > > > > > > > Thanks > > > > Sangwoo Kim > > > > > > > > > > > > On 6/22/07, Bo Xie <[EMAIL PROTECTED]> wrote: > > > > > Hi Ajith, > > > > > > > > > > Thanks for the comments. Look forward to your explanation. Like to know > > > > the difference between the workaround and the expected. > > > > > > > > > > Thanks, > > > > > -Bo > > > > > > > > > > > > > > > On 6/13/07, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > We will definitely look at the possibility of supporting this during > > > > > > the hackathon. I will perhaps explain in a separate mail what is the > > > > > > thinking behind starting from the port but it seems that we need to > > > > > > rethink this when it comes to skeletons. > > > > > > > > > > > > What I can suggest as a workaround is to generate code for each port > > > > > > with separate WSDL2Java calls (which will yield multiple skeletons). > > > > > > You can make this easy if you use the ant task > > > > > > > > > > > > Ajith > > > > > > > > > > > > On 6/13/07, Bo Xie <[EMAIL PROTECTED]> wrote: > > > > > > > Hi Amila and all, > > > > > > > > > > > > > > In case this is not working yet, can you suggest any alternative? I > > > > have a > > > > > > > few services that shared a lot of common data among them. I have to > > > > move all > > > > > > > the methods in all services into one mega service and change method > > > > name if > > > > > > > necessary to avoid conflicts. Mixing methods of different purpose into > > > > one > > > > > > > service looks messy. > > > > > > > > > > > > > >Appreciate any advice. > > > > > > > > > > > > > > -Bo > > > > > > > > > > > > > > > > > > > > > On 5/24/07, Jess Fisher < [EMAIL PROTECTED]> wrote: > > > > > > >
Re: axis2 and axiom DocumentBuilderFactory
Hi, I use axis2 1.2 with axiom 1.2.4 http://ws.apache.org/axis2/1_0/OMTutorial.html HTH, Alexey On 6/25/07, Johan Roch <[EMAIL PROTECTED]> wrote: We use axiom 1.2 and axis2 1.1. Any idea ? >From: "Davanum Srinivas" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: axis-user@ws.apache.org >Subject: Re: axis2 and axiom DocumentBuilderFactory >Date: Fri, 22 Jun 2007 14:39:16 -0400 > >Johan, > >Which version of Axis2? Axiom? > >thanks, >dims > >On 6/22/07, Johan Roch <[EMAIL PROTECTED]> wrote: >> >>Hi all, >> >>We have a webapp with some Axis2 clients. Axis2 uses Axiom to handle xml. >>The problem is that other parts of the application must parse some XML >>documents. As long as the Xerces DocumentBuilderFactory is used, we have >>no >>problem. But from a given time, our webapp starts to use the Axiom >>DocumentBuilderFactory everywhere and we get some NullPointerException >>each >>time: >> >>Example with JasperReport: >> >> StackTrace on java.lang.NullPointerException >> >>org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73) >> >>net.sf.jasperreports.engine.util.JRStyledTextParser.(JRStyledTextParser.java:115) >> >>net.sf.jasperreports.engine.fill.JRBaseFiller.(JRBaseFiller.java:157) >> >>net.sf.jasperreports.engine.fill.JRVerticalFiller.(JRVerticalFiller.java:92) >> >>net.sf.jasperreports.engine.fill.JRVerticalFiller.(JRVerticalFiller.java:74) >> >>... another one: >> >> Caused by: java.lang.NullPointerException >> at >>org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:73) >> at >>com.notary.util.signature.impl.AbstractVerifierImpl.getDocBuilder(AbstractVerifierImpl.java:116) >> at >>com.notary.util.signature.impl.iaik.XadesVerifierImpl.verifySignature(XadesVerifierImpl.java:119) >> ... 55 more >> >> >> >>I had a look at the Javadoc about DocumentBuilderFactory >>http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/DocumentBuilderFactory.html#newInstance(). >> >>and Xerces has a >>META-INF/services/javax.xml.parsers.DocumentBuilderFactory >>file in the jar while Axiom not. >> >>=> the question is: How does Axis2 get the Axiom's DocumentBuilderFactory >>? >>Does it set the System property ? >> >>About the NullPointerException itself, I guess I should post it in axiom's >>mailing list... >> >>Thx, >>Johan. >> >>_ >>Grand passioné ? Rassemblez tout ce qui vous intéresse en un seul >>endroit >>! http://get.live.com/live/features >> >> >>- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > >-- >Davanum Srinivas :: http://davanum.wordpress.com > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > _ A la recherche d'un ami d'enfance ? Peut-être est-il dans la liste d'amis de vos amis ! http://spaces.live.com/default.aspx?page=Ed01&ss=True - 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]
axis2 command -em
Hello, I'm looking for option "em" all over axis2 site and have no results. Does anybody know something about external mapping file or where I can find out? Is it xml file or not? -em : Specify an external mapping file Thanks, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 command ns2p
Thanks! I think if option, like in the first axis --fileNStoPkg, was in Axis2 would be more convenient. Thanks, Alexey On 6/24/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just had a quick glance over the supported constants inside WSDL2Code and I couldn't find an option like that. The only way you can do that is to pass that in the command like using -ns2p option. Alexey Zavizionov wrote: > In axis1 it was: >-N, --NStoPkg = >mapping of namespace to package >(now: -ns2p in axis2) >-f, --fileNStoPkg >file of NStoPkg mappings (default NStoPkg.properties) > (now: none in axis2) > Does axis2 have set the mapping file? > > Regards, > Alexey > > On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: >> Hello >> >> Does axis2 have option like -ns2p with arg file, file which contains >> ns1=pkg1,ns2=pkg2? >> In axis1 it was NStoPkg.properties >> >> Thanks, >> Alexey >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGffUrjON2uBzUhh8RAthUAKCVHmmlH0DPRdve8jEL63yPbCX3/gCgjHZ6 Q86ALh6d4U/FnTjSo/9nPRA= =x/KO -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for
Hi, I really haven't time in my wsrp implementation and this impossibility for multiple porttypes blocked my project. This leads me to seek other soap implementations... :( Will be fix it soon? When will be the next release? Regards, Alexey On 6/22/07, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi, You can use -pn, -sn options to specify the different port/service combinations. As for the point raised by Kim, yes it is a problem since now each port will yield a different service. Really this becomes a issue when you have multiple bindings and multiple porttypes. Ajith On 6/22/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > How can I do "generate code for each port with separate WSDL2Java > calls" if I can't modify wsdl file, because it was given by wsrp > specification http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl > ? > > Regards, > Alexey > > > On 6/22/07, Sagnwoo Kim <[EMAIL PROTECTED]> wrote: > > Ajith suggested multiple wsdl files for the solution of multiple ports. I > > have a question for that. When you want to create client from the wsdl > > files. with WSDL2Java and if you have multiple wsdl files for one service. > > Then you have to create multiple clients as well for every ports? Even > > though they are all under the same service? > > > > Thanks > > Sangwoo Kim > > > > > > On 6/22/07, Bo Xie <[EMAIL PROTECTED]> wrote: > > > Hi Ajith, > > > > > > Thanks for the comments. Look forward to your explanation. Like to know > > the difference between the workaround and the expected. > > > > > > Thanks, > > > -Bo > > > > > > > > > On 6/13/07, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > We will definitely look at the possibility of supporting this during > > > > the hackathon. I will perhaps explain in a separate mail what is the > > > > thinking behind starting from the port but it seems that we need to > > > > rethink this when it comes to skeletons. > > > > > > > > What I can suggest as a workaround is to generate code for each port > > > > with separate WSDL2Java calls (which will yield multiple skeletons). > > > > You can make this easy if you use the ant task > > > > > > > > Ajith > > > > > > > > On 6/13/07, Bo Xie <[EMAIL PROTECTED]> wrote: > > > > > Hi Amila and all, > > > > > > > > > > In case this is not working yet, can you suggest any alternative? I > > have a > > > > > few services that shared a lot of common data among them. I have to > > move all > > > > > the methods in all services into one mega service and change method > > name if > > > > > necessary to avoid conflicts. Mixing methods of different purpose into > > one > > > > > service looks messy. > > > > > > > > > >Appreciate any advice. > > > > > > > > > > -Bo > > > > > > > > > > > > > > > On 5/24/07, Jess Fisher < [EMAIL PROTECTED]> wrote: > > > > > > I still cannot get all the portTypes generated even with Axis 1.2. > > Any > > > > > plans on fixing this ? > > > > > > > > > > > > > > > > > > Bo Xie < [EMAIL PROTECTED]> wrote: > > > > > > Sorry to bother you again. Just want to know if this is a bug or I > > did not > > > > > set the parameter correctly. Any advice on how to make this work. > > > > > > > > > > > > Thanks, > > > > > > -Bo > > > > > > > > > > > > > > > > > > On 5/20/07, Bo Xie < [EMAIL PROTECTED]> wrote: > > > > > > > I attached the wsdls from the original email. > > > > > > > > > > > > > > Thanks, > > > > > > > -Bo > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 5/20/07, Amila Suriarachchi < [EMAIL PROTECTED] > > > wrote: > > > > > > > > Can you send your wsdl? do you have ports for each bining? > > > > > > > > Actually code is generated per port. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 5/20/07, Bo Xie < [EMAIL
Re: WSDL2Java pn option issue
Do you use Axis2 version 1.2? I ahve faced with same problem. Try to use Axis2 version 1.1, seems it works. Regards, Alexey On 6/22/07, Sagnwoo Kim <[EMAIL PROTECTED]> wrote: Hi all, I am newbie at Axis2 and having some issue here Now Im trying to generate skeleton files using WSDL2Java out of my wsdl file. My wsdl file has currently 3 ports. If I just go thru the WSDL2Java with the wsdl file it only generates skeleton file which has only one port. This is something intended by the Axis2 developer team as far as I know. So for the solution of that I can use "-pn" option which port I will chose. But it doesn't work for me. When I generate the skeleton file I use "java org.apache.axis2.wsdl.WSDL2Java -uri my_service.wsdl -p myservice -d adb -s -wv 1.2 -ss -sd -pn urn:my_service:I_Port". But this gives me skeleton file which contains only methods defined under "S_Port". The S_Port is the default port generated when I don't use "-pn" option. It seems like "-pn" doesn't work. Can anyone address me how to solve this issue? The following is the my_service.wsdl file I have. http://schemas.xmlsoap.org/wsdl/ " xmlns:api_binding="urn:api _binding" xmlns:soap=" http://schemas.xmlsoap.org/wsdl/soap/"; targetNamespace="urn:my_service"> http://localhost/axis2/services/urn:api:i"; /> http://localhost/axis2/services/urn:api:s"; /> http://localhost/axis2/services/urn:api:p"; /> Thank you Sangwoo Kim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 1.1.1 WSDL2JAVA - Not generating java classes for
How can I do "generate code for each port with separate WSDL2Java calls" if I can't modify wsdl file, because it was given by wsrp specification http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl ? Regards, Alexey On 6/22/07, Sagnwoo Kim <[EMAIL PROTECTED]> wrote: Ajith suggested multiple wsdl files for the solution of multiple ports. I have a question for that. When you want to create client from the wsdl files. with WSDL2Java and if you have multiple wsdl files for one service. Then you have to create multiple clients as well for every ports? Even though they are all under the same service? Thanks Sangwoo Kim On 6/22/07, Bo Xie <[EMAIL PROTECTED]> wrote: > Hi Ajith, > > Thanks for the comments. Look forward to your explanation. Like to know the difference between the workaround and the expected. > > Thanks, > -Bo > > > On 6/13/07, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > > Hi, > > We will definitely look at the possibility of supporting this during > > the hackathon. I will perhaps explain in a separate mail what is the > > thinking behind starting from the port but it seems that we need to > > rethink this when it comes to skeletons. > > > > What I can suggest as a workaround is to generate code for each port > > with separate WSDL2Java calls (which will yield multiple skeletons). > > You can make this easy if you use the ant task > > > > Ajith > > > > On 6/13/07, Bo Xie <[EMAIL PROTECTED]> wrote: > > > Hi Amila and all, > > > > > > In case this is not working yet, can you suggest any alternative? I have a > > > few services that shared a lot of common data among them. I have to move all > > > the methods in all services into one mega service and change method name if > > > necessary to avoid conflicts. Mixing methods of different purpose into one > > > service looks messy. > > > > > >Appreciate any advice. > > > > > > -Bo > > > > > > > > > On 5/24/07, Jess Fisher < [EMAIL PROTECTED]> wrote: > > > > I still cannot get all the portTypes generated even with Axis 1.2. Any > > > plans on fixing this ? > > > > > > > > > > > > Bo Xie < [EMAIL PROTECTED]> wrote: > > > > Sorry to bother you again. Just want to know if this is a bug or I did not > > > set the parameter correctly. Any advice on how to make this work. > > > > > > > > Thanks, > > > > -Bo > > > > > > > > > > > > On 5/20/07, Bo Xie < [EMAIL PROTECTED]> wrote: > > > > > I attached the wsdls from the original email. > > > > > > > > > > Thanks, > > > > > -Bo > > > > > > > > > > > > > > > > > > > > On 5/20/07, Amila Suriarachchi < [EMAIL PROTECTED] > wrote: > > > > > > Can you send your wsdl? do you have ports for each bining? > > > > > > Actually code is generated per port. > > > > > > > > > > > > > > > > > > > > > > > > On 5/20/07, Bo Xie < [EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > > > > > > > > Just wondering if this is still an issue in Axis2 1.2 or I did not > > > put the parameters properly. > > > > > > > > > > > > > > Thanks, > > > > > > > -Bo > > > > > > > > > > > > > > On 5/17/07, Bo Xie < [EMAIL PROTECTED]> wrote: > > > > > > > > Thanks, Amila. I tried your advice using no -pn and -sn. It still > > > only generated last one binding out of the 4. I used asix2 1.2 release. > > > > > > > > > > > > > > > > Here is the command line. Anything I did not do right? Attached is > > > the output files and wsdl files. Sorry for the 500k size. > > > > > > > > > > > > > > > > C:\programs\work>wsdl2java -o output -p com.xyz.nbi -t -ss -sd -g > > > -S src -R src -uri wsrp_service.wsdl > > > > > > > > Using AXIS2_HOME: C:\programs\axis2- 1.2 > > > > > > > > Using JAVA_HOME:C:\programs\jdk1.5.0_09 > > > > > > > > Retrieving document at 'wsrp_v1_bindings.wsdl', relative to > > > 'file:/C:/programs/work/'. > > > > > > > > Retrieving document at 'wsrp_v1_interfaces.wsdl', relative to > > > 'file:/C:/programs/work/wsrp_v1_bindings.wsdl'. > > > > > > > > Retrieving schema at 'wsrp_v1_types.xsd', relative to > > > 'file:/C:/programs/work/wsrp_v1_interfaces.wsdl'. > > > > > > > > Retrieving schema at ' http://www.w3.org/2001/xml.xsd', relative > > > to 'file:/C:/programs/work/wsrp_v1_types.xsd'. > > > > > > > > Retrieving document at 'wsrp_v1_bindings.wsdl', relative to > > > 'file:/C:/programs/work/'. > > > > > > > > Retrieving document at 'wsrp_v1_interfaces.wsdl', relative to > > > 'file:/C:/programs/work/wsrp_v1_bindings.wsdl'. > > > > > > > > Retrieving schema at 'wsrp_v1_types.xsd', relative to > > > 'file:/C:/programs/work/wsrp_v1_interfaces.wsdl'. > > > > > > > > Retrieving schema at ' http://www.w3.org/2001/xml.xsd', relative > > > to 'file:/C:/programs/work/wsrp_v1_types.xsd'. > > > > > > > > May 17, 2007 11:55:31 AM > > > org.apache.axis2.wsdl.codegen.writer.ClassWriter > > > createOutFile > > > > > > > > INFO: The > > > output\src\com\xyz\nbi\InvalidHandleException.java file > > > cannot be overwritten. > > > > > > > > May 17, 2007 11:55:31 AM > > > org.apache.axis2.wsdl.codegen.wr
Re: Axis2 migrating from Axis1 for WSRP
I found
https://issues.apache.org/jira/browse/AXIS2-1435
that fix doesn't approved
-pn option only works with axis2 1.1,
with axis2 1.2 doesn't work, why?
On 6/21/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
I don't know if it's a bug or a feature but for multi-port services it
seems to generate only the first port. If you are using Axis2 1.2 try
to put one service per port and then generate the code. You should get
some other skeleton classes to fill.
On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> Thanks,
>
> I have seen that migration manifest before send mail.
> I tried to use xmlbeans databinding. It generates lots of files, and
> same as I send
> in "wsdl"
> WSRPServiceMessageReceiverInOut.java
> WSRPServiceSkeleton.java
> WSRPServiceSkeletonInterface.java
> WSRPServiceStub.java
> :(
>
> BTW, WSRPServiceSkeleton class has only methods which described in
> WSRP_v1_PortletManagement_PortType. Looks like he generates one of
> four intefaces. Does it a bug?
>
> Regards,
> Alexey
>
> On 6/21/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
> > Do not use ADB to implement WS-* specifications since they usually use
> > very complex schemas and ADB doesn't have good support for complex
> > schemas. Consider using XmlBeans while ADB matures.
> > Axis2 uses a completely different service implementation schema. In
> > that case, you have to implement your service completing the
> > WSRPServiceSkeleton.java class that must have one operation per
> > service operation provided in the WSDL.
> >
> > Read this for details about migration from Axis1 to Axis2:
> >
> > http://ws.apache.org/axis2/1_2/migration.html
> >
> > On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> > > I'm new to axis2
> > >
> > > We are migrating from Axis1 to Axis2.
> > >
> > > I have problems with generation WSDL2Code for wsdl file
> > >
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
> > > which import bindings from
> > >
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
> > > which import interfaces from
> > >
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
> > >
> > > Command line arguments " -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
> > > wsrp_service.wsdl
> > > -o ${src.gen.dir}
> > > -ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
> > > urn:oasis:names:tc:wsrp:v1:types=org.type,
> > > urn:oasis:names:tc:wsrp:v1:bind=org.bind,
> > > urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl"
> > >
> > > While using axis1 we have got files:
> > > in the generated dir "bind"
> > > WSRP_v1_Markup_Binding_SOAPStub.java
> > > WSRP_v1_PortletManagement_Binding_SOAPStub.java
> > > WSRP_v1_Registration_Binding_SOAPStub.java
> > > WSRP_v1_ServiceDescription_Binding_SOAPStub.java
> > >
> > > in the generated dir "intf"
> > > WSRP_v1_Markup_PortType.java
> > > WSRP_v1_PortletManagement_PortType.java
> > > WSRP_v1_Registration_PortType.java
> > > WSRP_v1_ServiceDescription_PortType.java
> > >
> > > But, now we have
> > > in "intf"
> > > ExtensionMapper.java
> > > in "wsdl"
> > > WSRPServiceMessageReceiverInOut.java
> > > WSRPServiceSkeleton.java
> > > WSRPServiceSkeletonInterface.java
> > > WSRPServiceStub.java
> > >
> > > Does axis2 correct generate source?
> > >
> > > I'm really want to use axis2 for wsrp
> > >
> > > Thanks in advance
> > > Alexey
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Saludos.
> > José Antonio Sánchez
> >
> > -
> > 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]
>
>
--
Saludos.
José Antonio Sánchez
-
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: WSDL2Java Multiple port names to be code generated.
Even if I chose port name by -pn, it doesn't make affect. Does it bug? On 6/22/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: Hello, Lest look at http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html to see: -pn --port-name Specifies the port name to be code generated. If the port name is not specified, then the first port (of the selected service) will be picked. Does this mean I CAN'T generate sources for all ports at the same time? For generation I use wsdl file http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl Regards, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDL2Java Multiple port names to be code generated.
Hello, Lest look at http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html to see: -pn--port-name Specifies the port name to be code generated. If the port name is not specified, then the first port (of the selected service) will be picked. Does this mean I CAN'T generate sources for all ports at the same time? For generation I use wsdl file http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl Regards, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 command ns2p
In axis1 it was: -N, --NStoPkg = mapping of namespace to package (now: -ns2p in axis2) -f, --fileNStoPkg file of NStoPkg mappings (default NStoPkg.properties) (now: none in axis2) Does axis2 have set the mapping file? Regards, Alexey On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: Hello Does axis2 have option like -ns2p with arg file, file which contains ns1=pkg1,ns2=pkg2? In axis1 it was NStoPkg.properties Thanks, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soap viewer or sniffer
Does Wireshark can show soap body as here on the picture http://bp0.blogger.com/_aEfX-L_3RIQ/RcwbginwePI/AAs/X42ssmlnP5s/s1600-h/httplook_screen.JPG ? I have noticed many snifers, if it will be useful for you look at http://zavizionov.blogspot.com/2007/02/http-sniffers.html Regards, Alexey On 6/21/07, Thomas Jaehnig <[EMAIL PROTECTED]> wrote: No. I didn't know HTTPLook before. I use Wireshark for many things. Not only for watching HTTP sessions. It's very adjustable using filters. And it runs on many plattforms :D Maybe, HTTPLook is better for analyzing HTTP sessions. I will give it a try. Thomas On Thu, 2007-06-21 at 18:01 +0300, Alexey Zavizionov wrote: > Look like HTTPLook better than Wireshark. > Did you use HTTPLook? > > Alexey > > On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > > Hi, Thomas > > > > Thanks, I'll try it! > > I use the "HTTPLook", but it's some times doesn't work. > > > > Regards, > > Alexey > > > > On 6/21/07, Thomas Jaehnig <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > i prefer wireshark. This tool has a nice function called "Follow TCP > > > Stream". Using this you can see the whole conversation between the > > > parties. > > > > > > regard > > > > > > Thomas > > > > > > On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote: > > > > Hello, > > > > > > > > Which tools are you using for debugging web services and viewing soap messages? > > > > Does anybody use http sniffer for it? > > > > > > > > Thanks in advance, > > > > Alexey > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - 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: Soap viewer or sniffer
Look like HTTPLook better than Wireshark. Did you use HTTPLook? Alexey On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: Hi, Thomas Thanks, I'll try it! I use the "HTTPLook", but it's some times doesn't work. Regards, Alexey On 6/21/07, Thomas Jaehnig <[EMAIL PROTECTED]> wrote: > Hi, > > i prefer wireshark. This tool has a nice function called "Follow TCP > Stream". Using this you can see the whole conversation between the > parties. > > regard > > Thomas > > On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote: > > Hello, > > > > Which tools are you using for debugging web services and viewing soap messages? > > Does anybody use http sniffer for it? > > > > Thanks in advance, > > Alexey > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Soap viewer or sniffer
Hi, Thomas Thanks, I'll try it! I use the "HTTPLook", but it's some times doesn't work. Regards, Alexey On 6/21/07, Thomas Jaehnig <[EMAIL PROTECTED]> wrote: Hi, i prefer wireshark. This tool has a nice function called "Follow TCP Stream". Using this you can see the whole conversation between the parties. regard Thomas On Thu, 2007-06-21 at 16:23 +0300, Alexey Zavizionov wrote: > Hello, > > Which tools are you using for debugging web services and viewing soap messages? > Does anybody use http sniffer for it? > > Thanks in advance, > Alexey > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Soap viewer or sniffer
Hello, Which tools are you using for debugging web services and viewing soap messages? Does anybody use http sniffer for it? Thanks in advance, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 migrating from Axis1 for WSRP
I got wsdl files from oasis specification, there are 4 ports for one
service. I shouldn't change it.
Does any more know this issue?
Does axis2 useful for implements wsrp services?
Спасибо за помощь,
Alexey
On 6/21/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
I don't know if it's a bug or a feature but for multi-port services it
seems to generate only the first port. If you are using Axis2 1.2 try
to put one service per port and then generate the code. You should get
some other skeleton classes to fill.
On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> Thanks,
>
> I have seen that migration manifest before send mail.
> I tried to use xmlbeans databinding. It generates lots of files, and
> same as I send
> in "wsdl"
> WSRPServiceMessageReceiverInOut.java
> WSRPServiceSkeleton.java
> WSRPServiceSkeletonInterface.java
> WSRPServiceStub.java
> :(
>
> BTW, WSRPServiceSkeleton class has only methods which described in
> WSRP_v1_PortletManagement_PortType. Looks like he generates one of
> four intefaces. Does it a bug?
>
> Regards,
> Alexey
>
> On 6/21/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
> > Do not use ADB to implement WS-* specifications since they usually use
> > very complex schemas and ADB doesn't have good support for complex
> > schemas. Consider using XmlBeans while ADB matures.
> > Axis2 uses a completely different service implementation schema. In
> > that case, you have to implement your service completing the
> > WSRPServiceSkeleton.java class that must have one operation per
> > service operation provided in the WSDL.
> >
> > Read this for details about migration from Axis1 to Axis2:
> >
> > http://ws.apache.org/axis2/1_2/migration.html
> >
> > On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> > > I'm new to axis2
> > >
> > > We are migrating from Axis1 to Axis2.
> > >
> > > I have problems with generation WSDL2Code for wsdl file
> > >
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
> > > which import bindings from
> > >
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
> > > which import interfaces from
> > >
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
> > >
> > > Command line arguments " -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
> > > wsrp_service.wsdl
> > > -o ${src.gen.dir}
> > > -ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
> > > urn:oasis:names:tc:wsrp:v1:types=org.type,
> > > urn:oasis:names:tc:wsrp:v1:bind=org.bind,
> > > urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl"
> > >
> > > While using axis1 we have got files:
> > > in the generated dir "bind"
> > > WSRP_v1_Markup_Binding_SOAPStub.java
> > > WSRP_v1_PortletManagement_Binding_SOAPStub.java
> > > WSRP_v1_Registration_Binding_SOAPStub.java
> > > WSRP_v1_ServiceDescription_Binding_SOAPStub.java
> > >
> > > in the generated dir "intf"
> > > WSRP_v1_Markup_PortType.java
> > > WSRP_v1_PortletManagement_PortType.java
> > > WSRP_v1_Registration_PortType.java
> > > WSRP_v1_ServiceDescription_PortType.java
> > >
> > > But, now we have
> > > in "intf"
> > > ExtensionMapper.java
> > > in "wsdl"
> > > WSRPServiceMessageReceiverInOut.java
> > > WSRPServiceSkeleton.java
> > > WSRPServiceSkeletonInterface.java
> > > WSRPServiceStub.java
> > >
> > > Does axis2 correct generate source?
> > >
> > > I'm really want to use axis2 for wsrp
> > >
> > > Thanks in advance
> > > Alexey
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Saludos.
> > José Antonio Sánchez
> >
> > -
> > 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]
>
>
--
Saludos.
José Antonio Sánchez
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 migrating from Axis1 for WSRP
Thanks,
I have seen that migration manifest before send mail.
I tried to use xmlbeans databinding. It generates lots of files, and
same as I send
in "wsdl"
WSRPServiceMessageReceiverInOut.java
WSRPServiceSkeleton.java
WSRPServiceSkeletonInterface.java
WSRPServiceStub.java
:(
BTW, WSRPServiceSkeleton class has only methods which described in
WSRP_v1_PortletManagement_PortType. Looks like he generates one of
four intefaces. Does it a bug?
Regards,
Alexey
On 6/21/07, José Antonio Sánchez <[EMAIL PROTECTED]> wrote:
Do not use ADB to implement WS-* specifications since they usually use
very complex schemas and ADB doesn't have good support for complex
schemas. Consider using XmlBeans while ADB matures.
Axis2 uses a completely different service implementation schema. In
that case, you have to implement your service completing the
WSRPServiceSkeleton.java class that must have one operation per
service operation provided in the WSDL.
Read this for details about migration from Axis1 to Axis2:
http://ws.apache.org/axis2/1_2/migration.html
On 6/21/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote:
> I'm new to axis2
>
> We are migrating from Axis1 to Axis2.
>
> I have problems with generation WSDL2Code for wsdl file
>
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
> which import bindings from
>
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
> which import interfaces from
>
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
>
> Command line arguments " -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
> wsrp_service.wsdl
> -o ${src.gen.dir}
> -ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
> urn:oasis:names:tc:wsrp:v1:types=org.type,
> urn:oasis:names:tc:wsrp:v1:bind=org.bind,
> urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl"
>
> While using axis1 we have got files:
> in the generated dir "bind"
> WSRP_v1_Markup_Binding_SOAPStub.java
> WSRP_v1_PortletManagement_Binding_SOAPStub.java
> WSRP_v1_Registration_Binding_SOAPStub.java
> WSRP_v1_ServiceDescription_Binding_SOAPStub.java
>
> in the generated dir "intf"
> WSRP_v1_Markup_PortType.java
> WSRP_v1_PortletManagement_PortType.java
> WSRP_v1_Registration_PortType.java
> WSRP_v1_ServiceDescription_PortType.java
>
> But, now we have
> in "intf"
> ExtensionMapper.java
> in "wsdl"
> WSRPServiceMessageReceiverInOut.java
> WSRPServiceSkeleton.java
> WSRPServiceSkeletonInterface.java
> WSRPServiceStub.java
>
> Does axis2 correct generate source?
>
> I'm really want to use axis2 for wsrp
>
> Thanks in advance
> Alexey
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Saludos.
José Antonio Sánchez
-
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]
Axis2 migrating from Axis1 for WSRP
I'm new to axis2
We are migrating from Axis1 to Axis2.
I have problems with generation WSDL2Code for wsdl file
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_service.wsdl
which import bindings from
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl
which import interfaces from
http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_interfaces.wsdl
Command line arguments " -s -ss -sd -ssi -g -d adb -t -p org.wsdl -uri
wsrp_service.wsdl
-o ${src.gen.dir}
-ns2p urn:oasis:names:tc:wsrp:v1:intf=org.intf,
urn:oasis:names:tc:wsrp:v1:types=org.type,
urn:oasis:names:tc:wsrp:v1:bind=org.bind,
urn:oasis:names:tc:wsrp:v1:wsdl=org.wsdl"
While using axis1 we have got files:
in the generated dir "bind"
WSRP_v1_Markup_Binding_SOAPStub.java
WSRP_v1_PortletManagement_Binding_SOAPStub.java
WSRP_v1_Registration_Binding_SOAPStub.java
WSRP_v1_ServiceDescription_Binding_SOAPStub.java
in the generated dir "intf"
WSRP_v1_Markup_PortType.java
WSRP_v1_PortletManagement_PortType.java
WSRP_v1_Registration_PortType.java
WSRP_v1_ServiceDescription_PortType.java
But, now we have
in "intf"
ExtensionMapper.java
in "wsdl"
WSRPServiceMessageReceiverInOut.java
WSRPServiceSkeleton.java
WSRPServiceSkeletonInterface.java
WSRPServiceStub.java
Does axis2 correct generate source?
I'm really want to use axis2 for wsrp
Thanks in advance
Alexey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
axis2 command ns2p
Hello Does axis2 have option like -ns2p with arg file, file which contains ns1=pkg1,ns2=pkg2? In axis1 it was NStoPkg.properties Thanks, Alexey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploy simple service class
Thanks, I have read that. "You can deploy a service by simply taking this hierarchy of files and copying it to the webapps directory of your servlet engine. This is known as the "exploded" format. You can also compress your documents into an *.aar file, similar to a *.jar file, and place the *.aar file directly in the servlet engine's webapps directory." If I want to compile services as jar and put it into application_server_lib directory and within some war ( e.g. portal.war) just change web.inf to add axises' servlets, so how will be service deployed ? Alexey On 6/20/07, Chad DeBauch <[EMAIL PROTECTED]> wrote: Take a look at the quick start guide. http://ws.apache.org/axis2/1_2/quickstartguide.html Chad On 6/20/07, Alexey Zavizionov <[EMAIL PROTECTED]> wrote: > How can i do to deploy simple java class (within jar file) as axis2 service? > > - > 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]
Deploy simple service class
How can i do to deploy simple java class (within jar file) as axis2 service? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
