axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil D'Monte" <Sunil.Dmo...@tavant.com>
Subject RE: Deployment issues on OpenVMS
Date Tue, 18 Oct 2005 09:13:30 GMT
server-config.wsdd should be in the WEB-INF directory of your web
application...

Also when you say non-existent, what exactly do you mean - does it show up
in the list of services you get at /servlet/AxisServlet? Also do check the
logs in debug mode.

Regards,
Sunil D'Monte
Tavant Technologies
http://www.tavant.com
 

> -----Original Message-----
> From: Willem Grooters [mailto:willem.grooters@isc.politie.nl]
> Sent: Tuesday, October 18, 2005 14:35
> To: 'axis-user@ws.apache.org'
> Subject: RE: Deployment issues on OpenVMS
> 
> 
> It wasn't, so I did add it myself (assuming the right spot is 
> in tomcat's
> [.webapps.axis] directory. I also added the jar files that contain the
> server's classes, but it seems non-existant still. Even after 
> tomcat was
> restarted.
> 
> in [.webapps.axis.classes] I found that the samples are not 
> stored as .jar
> files but expanded. Would I need to expand the jar files, or 
> specify them in
> stead of the full path:
> 
> Currently, it is sepcified as:
> 
>   <service name="OrganisatieWebServiceSoap" provider="java:RPC"
> style="wrapped" use="literal">
>       <parameter name="wsdlTargetNamespace"
> value="http://politie.nl/webservices/xpol/organisatie"/>
>       <parameter name="wsdlServiceElement" 
> value="OrganisatieWebService"/>
>       <parameter name="wsdlServicePort" 
> value="OrganisatieWebServiceSoap"/>
>       <parameter name="className"
> value="nl.politie.webservices.xpol.organisatie.OrganisatieWebS
> erviceSoapSkel
> eton"/>
>       <parameter name="wsdlPortType" 
> value="OrganisatieWebServiceSoap"/>
>       <parameter name="allowedMethods" value="*"/>
> 
> The .jar files is named: OrganisatieWebService.jar, 
> containing the path
> nl/politie/webservices/xpol/organisatie. There are a number 
> of jars that
> hold calsses used in the application.
> 
> The current system does NOT carry the domain "politie.nl" - just the
> nodename. Does that matter?
> 
> Willem
> 
> -----Oorspronkelijk bericht-----
> Van: Sunil D'Monte [mailto:Sunil.Dmonte@tavant.com]
> Verzonden: dinsdag 18 oktober 2005 10:07
> Aan: 'axis-user@ws.apache.org'
> Onderwerp: RE: Deployment issues on OpenVMS
> 
> 
> Did it create an entry in your server-config.wsdd file? I 
> think that's all
> the admin client does; you could just as well copy and paste 
> the XML into
> server-config.wsdd yourself. It's worth trying this at least 
> to see if your
> service works.
> 
> Regards,
> Sunil D'Monte
> Tavant Technologies
> http://www.tavant.com
> 
> 
> > -----Original Message-----
> > From: Willem Grooters [mailto:willem.grooters@isc.politie.nl]
> > Sent: Tuesday, October 18, 2005 12:37
> > To: 'axis-user@ws.apache.org'
> > Subject: Deployment issues on OpenVMS
> > 
> > 
> > Hi,
> > I'm running Apache 1.3-1, Tomcat 4.1.24 and Axis 1.1 under 
> > Java 1.4.2-P2 on
> > OpenVMS 7.3-1.
> > These all have been installed as dowloaded from the HP 
> > website, without
> > extensive configuration, so rather "out-of-the-box". All the 
> > examples can be
> > run nicely. Collegues running in a .NET environment obtain 
> > the right answers
> > when they access these services using the same URL's as I do from my
> > browser.
> > These collegues have an application that communicates with a 
> > TRU64 machine
> > for getting data, and they want to use the same client 
> application to
> > retrieve similar data from the VMS box. However, I cannot use 
> > the TRU64 java
> > code because the data is completely different (storage, 
> > lyaout, codes). They
> > sent me the WSDL file from the Unix application, from which I 
> > could create
> > the java sources that would form the webservices, using 
> WSDL2Java. The
> > generation process also creates a deploy.wsdd and 
> > undeploy.wsdd. I have
> > added code where required and could compile all without errror.
> > However, when using these the services do not show up at all:
> > 
> > $ java "org.apache.axis.client.AdminClient" 
> "/amazone_src/deploy.wsdd"
> > 
> > (the quotes are required since VMS is non case-senistive if 
> > non-quoted).
> > It tells me it processes the file, no problems at all, but 
> the service
> > appears to be non-existing.
> > I had problems on this before:
> > 
> > $ set def amazone_ws:[000000] ! which is the root where the 
> > code started
> > (the web application path starts here)
> > $ java "org.apache.axis.client.AdminClient" "./<path>/deploy.wsdd"
> > 
> > says it cannot find the file to process, but
> > 
> > $ set def [.amazone.ws] ! which is the same location 
> > amazone-ws:[000000]
> > refers to!
> > $ java "org.apache.axis.client.AdminClient" "./<path>/deploy.wsdd"
> > 
> > succeeded - but with an error as above. However, this is 
> > considered a minor
> > issue.
> > 
> > Above is the same on a 7.3-2 system, so the OS version is not 
> > the problem.
> > 
> > Stopping and starting AXIS makes no difference, nor did stopping and
> > restarting Tomcat. Even worse: all of a sudden, even this failed:
> > 
> > $ java "org.apache.axis.client.AdminClient" 
> > "/amazone_src/deploy.wsdd" 
> > Processing file /amazone_src/deploy.wsdd 
> > Exception:: org.apache.axis.deployment.wsdd.WSDDException:
> > javax.xml.rpc.JAXRPCException: Null serializer factory specified.
> > javax.xml.rpc.JAXRPCException: Null serializer factory specified.
> >  at 
> > org.apache.axis.encoding.TypeMappingImpl.register(TypeMappingI
> > mpl.java)
> >  at 
> > org.apache.axis.deployment.wsdd.WSDDService.deployTypeMapping(
> > WSDDServic
> > >e.java)
> >  at 
> > 
> org.apache.axis.deployment.wsdd.WSDDService.initTMR(WSDDService.java)
> >  at 
> > org.apache.axis.deployment.wsdd.WSDDService.<init>(WSDDService.java)
> >  at
> > org.apache.axis.deployment.wsdd.WSDDDeployment.<init>(WSDDDepl
> > oyment.java)
> >  at 
> > 
> org.apache.axis.deployment.wsdd.WSDDDocument.<init>(WSDDDocument.java)
> >  at org.apache.axis.utils.Admin.processWSDD(Admin.java)
> >  at org.apache.axis.utils.Admin.process(Admin.java)
> >  at org.apache.axis.utils.Admin.AdminService(Admin.java)
> >  ... 
> > 
> > I'm not sure if stopping and starting of Tomcat has 
> > influenced this (is
> > shouldn't). Later, I stopped Axis, stopped Tomcat and started 
> > it again, and
> > found THIS problem was gone....
> > However, deployment of the service still is not possible.
> > 
> > One thing I noticed, just for completeness:
> > WSDL2Java creates a file
> > _GetConfigurationRequest_GetConfigurationResult.java - 
> > containing the code
> > of the same class. The filename is over 39 characters, so it will be
> > truncated to 39 - causing trouble in building the service. I 
> > changed the
> > name of the class and file to _getConfRequest_GetConfResult - 
> > and did the
> > same where referenced in both other (generated) java code to get it
> > compiled. I did change the reference to this class in 
> > deploy.wsdd but that
> > did not solve the problem - nor did it contribute to the last 
> > issue, since
> > restoring the original file did still trigger the 
> > WSDDExecption shown. So I
> > doubt that would be a cause of trouble.
> > 
> > All help is welcome - I'm rather new on this technique. 
> > 
> > WIllem
> > 
> > 
> > Disclaimer: 
> > The information contained in this E-mail and its attachments 
> > is confidential
> > and may be legally privileged. It is intended solely for the 
> > use of the
> > individual or entity to whom it is addressed and others 
> authorized to
> > receive it. If you are not the intended recipient you are 
> > hereby notified
> > that any disclosure, copying, distribution or taking any 
> > action in reliance
> > of the contents of this E-mail and any attachments is 
> > strictly prohibited
> > and may be unlawful. The CIP or ISC is neither liable for the 
> > proper and
> > complete transmission of the information contained in this 
> > E-mail and any
> > attachments nor for any delay in its receipt. If received in 
> > error, please
> > contact The CIP or ISC on +31(0)522 722222 quoting the name 
> > of the sender
> > and the addressee and then delete it from your system. Please 
> > note that  the
> > The CIP or ISC does not accept any responsibility for viruses 
> > and it is your
> > responsibility to scan the E-mail and attachments (if any). 
> > No contracts may
> > be concluded on behalf of The CIP or ISC by means of E-mail 
> > communications.
> > 
> > 
> 
> 
> Disclaimer: 
> The information contained in this E-mail and its attachments 
> is confidential
> and may be legally privileged. It is intended solely for the 
> use of the
> individual or entity to whom it is addressed and others authorized to
> receive it. If you are not the intended recipient you are 
> hereby notified
> that any disclosure, copying, distribution or taking any 
> action in reliance
> of the contents of this E-mail and any attachments is 
> strictly prohibited
> and may be unlawful. The CIP or ISC is neither liable for the 
> proper and
> complete transmission of the information contained in this 
> E-mail and any
> attachments nor for any delay in its receipt. If received in 
> error, please
> contact The CIP or ISC on +31(0)522 722222 quoting the name 
> of the sender
> and the addressee and then delete it from your system. Please 
> note that  the
> The CIP or ISC does not accept any responsibility for viruses 
> and it is your
> responsibility to scan the E-mail and attachments (if any). 
> No contracts may
> be concluded on behalf of The CIP or ISC by means of E-mail 
> communications.
> 
> 

Mime
View raw message