WSCompile error
Hello,
I'm very new to webservices. I am using tomcat as the container and got jwsdp installed in it.
While trying to build one of the examples provided I am getting a build error. It seems that WSCompile isn't working fine. Find below the extracts of build output and some excerpts of build.xml file too.
build output
C:\tomcat50-jwsdp\xws-security\samples\simple>ant run-sample
Buildfile: build.xml
clean:
[delete] Deleting directory C:\tomcat50-jwsdp\xws-security\samples\simple\build
[delete] Deleting directory C:\tomcat50-jwsdp\xws-security\samples\simple\dist
as8-check:
ws-check:
tc-check:
[mkdir] Created dir: C:\tomcat50-jwsdp\xws-security\samples\simple\build\client\classes
[mkdir] Created dir: C:\tomcat50-jwsdp\xws-security\samples\simple\build\server\WEB-INF\classes
[mkdir] Created dir: C:\tomcat50-jwsdp\xws-security\samples\simple\dist
compile-handler-code:
[echo] Compiling the handler source code
[javac] Compiling 1 source file to C:\tomcat50-jwsdp\xws-security\samples\simple\build\server\WE
B-INF\classes
[javac] Compiling 1 source file to C:\tomcat50-jwsdp\xws-security\samples\simple\build\client\cl
asses
create-handler-jar:
[jar] Building jar: C:\tomcat50-jwsdp\xws-security\samples\simple\build\client\secenv-handler.
jar
prepare:
gen-server:
[echo] Running wscompile....
BUILD FAILED
file:C:/tomcat50-jwsdp/xws-security/samples/simple/build.xml:135: Could not create task or type of t
ype: wscompile.
Ant could not find the task or a class this task relies upon.
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
- You have misspelt 'wscompile'.
Fix: check your spelling.
- The task needs an external JAR file to execute
and this is not found at the right place in the classpath.
Fix: check the documentation for dependencies.
Fix: declare the task.
- The task is an Ant optional task and optional.jar is absent
Fix: look for optional.jar in ANT_HOME/lib, download if needed
- The task was not built into optional.jar as dependent
libraries were not found at build time.
Fix: look in the JAR to verify, then rebuild with the needed
libraries, or download a release version from apache.org
- The build file was written for a later version of Ant
Fix: upgrade to at least the latest release version of Ant
- The task is not an Ant core or optional task
and needs to be declared using <taskdef>.
Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath
Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.
Total time: 2 seconds
Excerpts from the build.xml
<!--
Copyright 2004 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
-->
<!DOCTYPE project [
<!ENTITY tomcat SYSTEM "file:../buildconfig/tomcat-config.xml">
<!ENTITY sjsas SYSTEM "file:../buildconfig/sjsas-config.xml">
<!ENTITY sjsws SYSTEM "file:../buildconfig/sjsws-config.xml">
]>
<project name="simple" default="usage" basedir=".">
<!-- Values in build.properties (if any) override the values in this file -->
<property file="build.properties"/>
<property file="../build.properties"/>
<property name="context-path" value="securesimple"/>
<property name="client-class" value="${ant.project.name}.TestClient"/>
<property name="url" value="http://${endpoint.host}:${endpoint.port}/manager/"/>
<property name="username" value="${username}"/>
<property name="password" value="${password}"/>
<property name="build.home" value="build"/>
<property name="dist.home" value="dist"/>
<property name="portable-war" value="${ant.project.name}-portable.war"/>
<property name="deployable-war" value="${context-path}.war"/>
<property name="war-path" value="${dist.home}/${deployable-war}"/>
<property name="config.rpcenc.file" value="${basedir}/etc/config.xml"/>
<property name="client.config.rpcenc.file" value="${basedir}/etc/client-config.xml"/>
<property name="model.rpcenc.file" value="model.xml.gz"/>
<property name="webapp.webxml" value="${basedir}/etc/web.xml"/>
<property name="jaxrpc.tool.verbose" value="true"/>
<target name="as8-check" if="sjsas.home">
<mkdir dir="${build.home}/client/classes"/>
<mkdir dir="${build.home}/server/WEB-INF/classes"/>
<mkdir dir="${dist.home}"/>
&sjsas;
</target>
<target name="ws-check" if="sjsws.home">
<mkdir dir="${build.home}/client/classes"/>
<mkdir dir="${build.home}/server/WEB-INF/classes"/>
<mkdir dir="${dist.home}"/>
&sjsws;
</target>
<target name="tc-check" if="tomcat.home">
<mkdir dir="${build.home}/client/classes"/>
<mkdir dir="${build.home}/server/WEB-INF/classes"/>
<mkdir dir="${dist.home}"/>
<!--&tomcat;--><!--Added by Sourabh: Its commented to fix compilation issues-->
</target>
<target name="prepare" depends="as8-check, ws-check, tc-check, compile-handler-code, create-handler-jar">
<mkdir dir="${build.home}"/>
<mkdir dir="${build.home}/server"/>
<mkdir dir="${build.home}/server/WEB-INF"/>
<mkdir dir="${build.home}/server/WEB-INF/classes"/>
<mkdir dir="${dist.home}"/>
</target>
<target name="compile-handler-code"
description="Compiles the handler">
<echo message="Compiling the handler source code "/>
<path id="app.classpath">
<!--Added by Sourabh:Start -->
<fileset dir="${build.home}/../../../../xws-security/lib">
<include name="**/*.jar"/>
</fileset>
<fileset dir="${build.home}/../../../../jwsdp-shared/lib">
<include name="**/*.jar"/>
</fileset>
<!--Added by Sourabh: End-->
</path>
<javac debug="true"
srcdir="src"
destdir="${build.home}/server/WEB-INF/classes"
includes="**/*.java">
<classpath>
<path refid="app.classpath"/>
</classpath>
</javac>
<javac debug="true"
srcdir="src"
destdir="${build.home}/client/classes"
includes="**/*.java">
<classpath>
<path refid="app.classpath"/>
</classpath>
</javac>
</target>
<target name="create-handler-jar"
description="Creating jar file">
<jar jarfile="${build.home}/client/secenv-handler.jar">
<fileset dir="${build.home}/client/classes">
<include name="**/*.class"/>
</fileset>
</jar>
</target>
<target name="compile-server" depends="gen-server"
description="Compiles the server-side source code">
<echo message="Compiling the server-side source code...."/>
<javac debug="true"
srcdir="server/src"
destdir="${build.home}/server/WEB-INF/classes"
includes="**/*.java">
<classpath>
<path refid="app.classpath"/>
</classpath>
</javac>
</target>
<target name="gen-server" depends="prepare"
description="Runs wscompile to generate server artifacts">
<echo message="Running wscompile...."/>
<wscompile verbose="${jaxrpc.tool.verbose}"
xPrintStackTrace="true"
jvmargs="-Djava.endorsed.dirs=${java.endorsed.dir}"
keep="true" fork="true"
security="${server.security.config}"
import="true"
model="${build.home}/server/WEB-INF/${model.rpcenc.file}"
base="${build.home}/server/WEB-INF/classes"
classpath="${app.classpath}"
config="${config.rpcenc.file}">
<classpath>
<pathelement location="${build.home}/server/WEB-INF/classes"/>
<path refid="app.classpath"/>
</classpath>
</wscompile>
</target>
<target name="setup-web-inf" depends="prepare">
<echo message="Setting up ${build.home}/server/WEB-INF..."/>
<copy file="./etc/web.xml" todir="${build.home}/server/WEB-INF"/>
<copy file="./etc/jaxrpc-ri.xml" todir="${build.home}/server/WEB-INF"/>
<copy file="./etc/PingService.wsdl" todir="${build.home}/server/WEB-INF"/>
</target>
<target name="raw-war" depends="setup-web-inf"
description="Creates a 'raw' WAR file">
<echo message="Packaging to ${dist.home}/${portable-war}...."/>
<delete file="${dist.home}/${portable-war}" />
<jar jarfile="${dist.home}/${portable-war}">
<fileset dir="${build.home}/server">
<include name="WEB-INF/**"/>
<include name="index.html"/>
</fileset>
</jar>
</target>
<target name="process-war" depends="raw-war"
description="Runs wsdeploy to create a deployable or 'cooked' WAR file">
<echo message="Running wsdeploy..."/>
<delete file="${dist.home}/${deployable-war}"/>
<wsdeploy fork="true" verbose="${jaxrpc-tool-verbose}" keep="true"
jvmargs="-Djava.endorsed.dirs=${java.endorsed.dir}"
tmpdir="${build.home}/server"
outwarfile="${dist.home}/${deployable-war}"
inwarfile="${dist.home}/${portable-war}">
<classpath>
<path refid="app.classpath"/>
</classpath>
</wsdeploy>
</target>
<target name="build-server"
depends="compile-server, gen-server, raw-war, process-war">
</target>
<!-- Appserver -->
<target name="check-if-deployed-as" if="sjsas.home">
<echo message="Checking for deployed webapp at context path /${context-path}"/>
<condition property="as.webapp.deployed">
<http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
</condition>
</target>
<target name="deploy-sjsas"
depends="prepare, check-if-deployed-as, undeploy-sjsas"
if="sjsas.home">
<echo message="Deploying war for ${ant.project.name} to sjsas"/>
<appserv-deploy file="${war-path}" password="${password}" sunonehome="${sjsas.home}" />
</target>
<target name="undeploy-sjsas" if="as.webapp.deployed">
<echo message="Undeploying existing webapp at ${context-path}"/>
<echo message="appclasspath ${app.classpath}"/>
<appserv-undeploy name="${context-path}" password="${password}" sunonehome="${sjsas.home}" />
</target>
<!-- end of Appserver -->
<!-- Webserver -->
<target name="check-if-deployed-ws" if="sjsws.home">
<echo message="Checking for deployed webapp at context path /${context-path}"/>
<condition property="ws.webapp.deployed">
<http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
</condition>
</target>
<target name="deploy-ws">
<echo message="deploying ${war-path} at ${context-path}" />
<exec executable="${SJSWS_DEPLOY}" vmlauncher="false">
<arg value="deploy" />
<arg value="-u" />
<arg value="/${context-path}" />
<arg value="-i" />
<arg value="${VS.DIR}" />
<arg value="-v" />
<arg value="${VS.DIR}" />
<arg value="${war-path}" />
</exec>
</target>
<target name="undeploy-ws" >
<echo message="undeploying ${context-path}" />
<exec executable="${SJSWS_DEPLOY}" vmlauncher="false">
<arg value="delete" />
<arg value="deploy" />
<arg value="-u" />
<arg value="/${context-path}" />
<arg value="-i" />
<arg value="${VS.DIR}" />
<arg value="-v" />
<arg value="${VS.DIR}" />
<arg value="hard" />
</exec>
</target>
<target name="deploy-sjsws"
depends="prepare, check-if-deployed-ws, undeploy-sjsws"
if="sjsws.home" >
<echo message="Deploying war for ${ant.project.name} to sjsws"/>
<antcall target="deploy-ws" />
</target>
<target name="undeploy-sjsws" if="ws.webapp.deployed">
<echo message="Undeploying existing webapp at ${context-path}"/>
<echo message="appclasspath ${app.classpath}"/>
<antcall target="undeploy-ws" />
</target>
<!--End of Webserver -->
<!--Tomcat -->
<target name="check-if-deployed-tom" if="tomcat.home">
<echo message="Checking for deployed webapp at context path /${context-path}"/>
<condition property="tom.webapp.deployed">
<http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
</condition>
</target>
<target name="deploy-tomcat"
depends="prepare, check-if-deployed-tom, undeploy-tomcat"
if="tomcat.home" >
<echo message="Deploying war for ${ant.project.name} to tomcat"/>
<deploy-catalina url="${url}" username="${username}" password="${password}"
path="/${context-path}" war="file:${war-path}"/>
</target>
<target name="undeploy-tomcat-proper" if="webapp.deployed">
<echo message="Undeploying existing webapp at ${context-path}"/>
<undeploy-catalina url="${url}" username="${username}" password="${password}" path="/${context-path}"/>
</target>
<target name="undeploy-tomcat-war-present" if="war.present">
<echo message="Undeploying existing webapp at ${context-path}"/>
<undeploy-catalina url="${url}" username="${username}" password="${password}" path="/${context-path}"/>
</target>
<target name="undeploy-tomcat" if="tomcat.home">
<echo message="Undeploying existing webapp at ${context-path}"/>
<condition property="war.present">
<available file="${tomcat.home}/webapps/${deployable-war}" />
</condition>
<antcall target="undeploy-tomcat-war-present" />
<condition property="webapp.deployed">
<http url="http://${endpoint.host}:${endpoint.port}/${context-path}/"/>
</condition>
<antcall target="undeploy-tomcat-proper" />
</target>
<!--End of Tomcat -->
<target name="deploy-forced" depends= "deploy-sjsas, deploy-sjsws, deploy-tomcat"/>
<target name="internal-undeploy" depends= "undeploy-sjsas, undeploy-sjsws, undeploy-tomcat"/>
<target name="redeploy" depends="prepare"
description="Undeploys and deploys a Web aplication">
<antcall target="undeploy" />
<antcall target="deploy" />
</target>
<target name="gen-client" depends="prepare"
description="Runs wscompile to generate client side artifacts">
<echo message="Running wscompile...."/>
<wscompile fork="true" verbose="${jaxrpc.tool.verbose}" keep="true"
jvmargs="-Djava.endorsed.dirs=${java.endorsed.dir}"
client="true"
security="${client.security.config}"
base="${build.home}/client"
features=""
config="${client.config.rpcenc.file}">
<classpath>
<fileset dir="${build.home}/client">
<include name="secenv-handler.jar"/>
</fileset>
<path refid="app.classpath"/>
</classpath>
</wscompile>
</target>
<target name="compile-client" depends="prepare"
description="Compiles the client-side source code">
<echo message="Compiling the client source code...."/>
<javac srcdir="client/src"
debug="true"
destdir="${build.home}/client"
includes="**/*.java">
<classpath>
<path refid="app.classpath"/>
<fileset dir="${build.home}/client">
<include name="secenv-handler.jar"/>
</fileset>
</classpath>
</javac>
</target>
<target name="build-client" depends="gen-client, compile-client"
description="Executes the targets needed to build a stub client.">
</target>
<target name="run-sample"
depends="clean, prepare, build-server, deploy-forced, build-client"
description="Runs the example client">
<echo message="Running the ${client-class} program...."/>
<java fork="on" classname="${client-class}">
<sysproperty key="java.endorsed.dirs" value="${java.endorsed.dir}"/>
<sysproperty key="endpoint.host" value="${endpoint.host}"/>
<sysproperty key="endpoint.port" value="${endpoint.port}"/>
<sysproperty key="service.url" value="${service.url}"/>
<sysproperty key="jwsdp.home" value="${jwsdp.home}"/>
<classpath>
<pathelement location="${build.home}/client"/>
<fileset dir="${build.home}/client">
<include name="secenv-handler.jar"/>
</fileset>
<path refid="app.classpath"/>
</classpath>
</java>
</target>
<target name="run-remote-sample"
depends="clean, prepare, build-client"
description="Runs the example client">
<echo message="Running the ${client-class} program...."/>
<java fork="on" classname="${client-class}">
<sysproperty key="java.endorsed.dirs" value="${java.endorsed.dir}"/>
<sysproperty key="http.proxyHost" value="${http.proxyHost}"/>
<sysproperty key="http.proxyPort" value="${http.proxyPort}"/>
<sysproperty key="endpoint.host" value="${endpoint.host}"/>
<sysproperty key="endpoint.port" value="${endpoint.port}"/>
<sysproperty key="service.url" value="${service.url}"/>
<sysproperty key="jwsdp.home" value="${jwsdp.home}"/>
<classpath>
<pathelement location="${build.home}/client"/>
<fileset dir="${build.home}/client">
<include name="secenv-handler.jar"/>
</fileset>
<path refid="app.classpath"/>
</classpath>
</java>
</target>
<target name="clean-server"
description="Removes server side build directories">
<delete dir="${build.home}/server"/>
</target>
<target name="clean-client"
description="Removes client side build directories">
<delete dir="${build.home}/client"/>
</target>
<target name="clean"
description="Removes all build and dist directories">
<delete dir="${build.home}"/>
<delete dir="${dist.home}"/>
</target>
<target name="usage" depends="prepare">
<echo message="Please see README.txt for more info."/>
<echo message="Useful targets:"/>
<echo message=" clean = remove both server and client objects"/>
<echo message=" clean-server = remove only server objects"/>
<echo message=" clean-client = remove only client objects"/>
<echo message=" build-server = build server side code"/>
<echo message=" deploy-forced = force deploy built server code to Container"/>
<echo message=" build-client = build client app code"/>
<echo message=" run-sample = run the sample"/>
<echo message=" run-remote-sample = run the sample against a remote server containing the deployed endpoint"/>
</target>
<target name="help" depends="usage"/>
</project>any help would be highly appreciated.
regards,
Sourav
407 Proxy Authentication Required
The compiler is trying to reference a document on the web, but can't use your proxy because it doesn't have the proxy id and password to use.
If it isn't possible to pas the proxy info to the compiler, download the doc to a local server and reference it there.
Similar Messages
-
Hi all,
I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
Cheers,
--Tim West
Full output (from wscompile Ant task) - added linebreaks for readability
Buildfile: C:\common\eclipse-projects\thp\build.xml
wscompile-init:
ANEW-generate-server-binding:
[wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
-features:documentliteral,wsi -g -gen:server -keep -verbose \
C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
[wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
[wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
[wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: userDefinedBody]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdHeader]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdRequestAckHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdGrantHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyGrantHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdDenialHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyDenialHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdModifyResponseChoiceHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdCancellationRequestHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdCancellationResponseHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusQueryHdr]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: statusStructure]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusResponseBody]
[wscompile] [LiteralObjectSerializerGenerator: writing serializer/deserializer for: holdStatusResponseHdr]
[wscompile] error: generator error: internal error (should not happen): tie.generator.002
BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
Total time: 2 secondsHi again,
The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
Thanks again,
-Tim West
<?xml version="1.0" encoding="UTF-8"?>
<definitions
name="TentativeHold"
targetNamespace="http://www.w3.org/2001/08/thp/definitions"
xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
targetNamespace="http://www.w3.org/2001/08/thp/schemas">
<!-- =================================================================== -->
<!-- Item - holdHeader -->
<!-- Note - This information is required in all the Tentative Hold Protocol
communications. -->
<!-- Fields- holdID - UUID. -->
<!-- customerID - account number or other identifier -->
<!-- replyTo - could be a unique locator such as a URI or an
email address depending on the communication protocol
to be used. -->
<!-- comment - space for trading partner defined info. -->
<!-- =================================================================== -->
<complexType name="holdHeader">
<sequence>
<element name="holdID" type="int"/>
<element name="customerID" type="string"/>
<element name="replyTo" type="string"/>
<element name="comment" type="string"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - userDefinedBody -->
<!-- Note - This will carry any domain-specific information (e.g., product
ID and quantity). An implementation shall probably have many
different userDefinedBody's (one for holdRequest, holdRequestAck,
...). This body is used in all messages. -->
<!-- Fields - Trading partner to trading partner specific or an agreed
- standard (e.g., RosettaNet PIP). -->
<!-- =================================================================== -->
<!-- TIM: Just junk here for now, must fix later -->
<complexType name="userDefinedBody">
<sequence>
<element name="someRequestField" type="string"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdRequestHdr -->
<!-- Note - Specifies the Tentative Hold Protocol header for messages
- requesting a tentative hold. -->
<!-- Fields - Same as holdHeader -->
<!-- =================================================================== -->
<complexType name="holdRequestHdr">
<sequence>
<element name="baseHeader" type="holdSchema:holdHeader"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdRequestAckHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + timeUntilResponse - a indication of the time it
- will take the resource provider to process the request. -->
<!-- =================================================================== -->
<complexType name="holdRequestAckHdr">
<sequence>
<element name="baseHeader" type="holdSchema:holdHeader"/>
<element name="timeUntilResponse" type="duration"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdGrantHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
- on the resource requested. -->
<!-- =================================================================== -->
<complexType name="holdGrantHdr">
<sequence>
<element name="baseHeader" type="holdSchema:holdHeader"/>
<element name="holdDuration" type="duration"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdDenialHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + reason - a description of the reason for the
- denial. The implementation may choose to use reason codes or just
- textual descriptions. -->
<!-- =================================================================== -->
<complexType name="holdDenialHdr">
<sequence>
<element name="baseHeader" type="holdSchema:holdHeader"/>
<element name="reason" type="string"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdModifyRequestHdr -->
<!-- Note - -->
<!-- Fields - holdHeader -->
<!-- =================================================================== -->
<complexType name="holdModifyRequestHdr">
<sequence>
<element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdModifyGrantHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
- on the resource requested. -->
<!-- =================================================================== -->
<complexType name="holdModifyGrantHdr">
<sequence>
<element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdModifyDenialHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + reason - a description of the reason for the denial.
- The implementation may choose to use reason codes or just textual
- descriptions.-->
<!-- =================================================================== -->
<complexType name="holdModifyDenialHdr">
<sequence>
<element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdModifyResponseChoiceHdr -->
<!-- Note - The use of a single type for this response was to facilitate a
- synchronous request/response for the modify request without preventing
- asynchronous.-->
<!-- Fields - Either holdModifyGrantHdr or holdModifyDenialHdr -->
<!-- =================================================================== -->
<!-- TIM: JWSDP does not support xsd:choice, so I'm turning this into a sequence.
- The implementor is now responsible for ensuring exactly one of these
is present.
-->
<complexType name="holdModifyResponseChoiceHdr">
<sequence>
<element name="grant" type="holdSchema:holdModifyGrantHdr"/>
<element name="deny" type="holdSchema:holdModifyDenialHdr"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdCancellationRequestHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + customerReason - a description of or a code for
- the reason why the hold is being cancelled. -->
<!-- =================================================================== -->
<complexType name="holdCancellationRequestHdr">
<sequence>
<element name="customerHold" type="holdSchema:holdHeader"/>
<element name="customerReason" type="string"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdCancellationResponseHdr -->
<!-- Note - -->
<!-- Fields - holdHeader -->
<!-- =================================================================== -->
<complexType name="holdCancellationResponseHdr">
<sequence>
<element name="customerHold" type="holdSchema:holdHeader"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdCancellationNotificationHdr -->
<!-- Note - -->
<!-- Fields - holdHeader + cancellationReason - a description of or a code
-for the reason the vendor is cancelling the hold. -->
<!-- =================================================================== -->
<complexType name="holdCancellationNotificationHdr">
<sequence>
<element name="customerHold" type="holdSchema:holdHeader"/>
<element name="cancellationReason" type="string"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdStatusQueryHdr -->
<!-- Note - -->
<!-- Fields - holdHeader -->
<!-- =================================================================== -->
<complexType name="holdStatusQueryHdr">
<sequence>
<element name="customerHold" type="holdSchema:holdHeader"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdStatusResponseHdr -->
<!-- Note - -->
<!-- Fields - holdHeader -->
<!-- =================================================================== -->
<complexType name="holdStatusResponseHdr">
<sequence>
<element name="baseHeader" type="holdSchema:holdHeader"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - statusStructure -->
<!-- Note - -->
<!-- Fields - holdHeader + holdState - a description of the state of the hold.
- Possible values currently defined are: responding, in process, active,
- and inactive. The definition is left open (not restricted) for future or
- user refinement of the useful values. -->
<!-- =================================================================== -->
<complexType name="statusStructure">
<sequence>
<element name="itemHeader" type="holdSchema:holdHeader"/>
<element name="holdState" type="string"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdStatusResponseBody -->
<!-- Note - -->
<!-- Fields - holdItemsCount - the number of holds matching the holdStatusQuery. -->
<!-- itemList - The header and state of the holds that match the query. -->
<!-- =================================================================== -->
<complexType name="holdStatusResponseBody">
<sequence>
<element name="holdItemsCount" type="int"/>
<element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
<!-- =================================================================== -->
<!-- Item - holdErrorHdr -->
<!-- Note - -->
<!-- Fields - holdHeader -->
<!-- =================================================================== -->
<!-- TIM: Combined old "holdErrorHdr" and "holdErrorBody" as a fault must
- have only a single part (see WSDL sec 3.6).
-->
<complexType name="holdError">
<sequence>
<element name="baseHeader" type="holdSchema:holdHeader"/>
<element name="holdErrorType" type="int"/>
<element name="holdErrorDesc" type="string"/>
</sequence>
</complexType>
<!-- TIM: To use doc/lit, we need <element> tags here to reference from WSDL -->
<element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
<element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
<element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
<element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
<element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
<element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
<element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
<element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
<element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
<element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
<element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
<element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
<element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
<element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
<element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
<element name="holdError" type="holdSchema:holdError"/>
</schema>
</types>
<message name="HoldRequest">
<part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
<part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldRequestAck">
<part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
<part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldGrantResponse">
<part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
<part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldDenialResponse">
<part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
<part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldModifyRequest">
<part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
<part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldModifyResponse">
<part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
<part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationRequest">
<part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
<part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationResponse">
<part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
<part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldCancellationNotification">
<part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
<part name="body" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldStatusQueryRequest">
<part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
<part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
</message>
<message name="HoldStatusResponse">
<part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
<part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
</message>
<message name="HoldErrorResponse">
<!-- TIM: altered to be consistent with updated schema - the
- fault body must have only one part
-->
<part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
</message>
<portType name="TentativeHoldServicePortType">
<operation name="InitiateHold">
<input message="tns:HoldRequest"/>
<output message="tns:HoldRequestAck"/>
<!--
<fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
-->
</operation>
<operation name="InitiateHoldModify">
<input message="tns:HoldModifyRequest"/>
<output message="tns:HoldModifyResponse"/>
<!--
<fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
-->
</operation>
<operation name="InitiateHoldCancellation">
<input message="tns:HoldCancellationRequest"/>
<output message="tns:HoldCancellationResponse"/>
<!--
<fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
-->
</operation>
<operation name="InitiateStatusQuery">
<input message="tns:HoldStatusQueryRequest"/>
<output message="tns:HoldStatusResponse"/>
<!--
<fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
-->
</operation>
</portType>
<portType name="TentativeHoldNotificationServicePortType">
<operation name="NotifyHoldGranted">
<output message="tns:HoldGrantResponse"/>
</operation>
<operation name="NotifyHoldDenied">
<output message="tns:HoldDenialResponse"/>
</operation>
<operation name="NotifyServerHoldCancellation">
<output message="tns:HoldCancellationNotification"/>
</operation>
</portType>
<binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="InitiateHold">
<soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
<!--
<fault name="HoldErrorResponse">
<soap:fault name="HoldErrorResponse" use="literal"/>
</fault>
-->
</operation>
<operation name="InitiateHoldModify">
<soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
<!--
<fault name="HoldErrorResponse">
<soap:fault name="HoldErrorResponse" use="literal"/>
</fault>
-->
</operation>
<operation name="InitiateHoldCancellation">
<soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
<!--
<fault name="HoldErrorResponse">
<soap:fault name="HoldErrorResponse" use="literal"/>
</fault>
-->
</operation>
<operation name="InitiateStatusQuery">
<soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
<!--
<fault name="HoldErrorResponse">
<soap:fault name="HoldErrorResponse" use="literal"/>
</fault>
-->
</operation>
</binding>
<service name="TentativeHoldService">
<documentation> Mythical Tentative Hold Web service</documentation>
<port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
<soap:address location="http://xyz.com/tentativeHold/"/>
</port>
</service>
<service name="TentativeHoldNotificationService">
<port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
<soap:address location="http://xyz.com/tentativeHoldNotification"/>
</port>
</service>
</definitions> -
[wscompile] error: invalid remote interface
I have an interface I want to publish as a web service. This interface extends java.rmi.Remote and each of its methods throws a RemoteException. But when I run wscompile (via ant) against this interface in order to have the wsdl file generated it gives me:
error: invalid remote interface; class manplan.j2ee.service.project.ProjectManager is not an interfacee
I have searched the forum and the internet yet could not find an answer. Any hints are most welcome. Below you will find excerpts from the relevant files.
Cheers,
Olaf
[interface]
public interface ProjectManager extends java.rmi.Remote
void createProject(final Project project) throws DuplicateProjectException,
ProjectManagementRuntimeException, RemoteException;
[ant]
<wscompile
keep="true"
define="true"
base="${ws.build.classes.dir}"
xPrintStackTrace="true"
verbose="true"
model="${ws.build.dir}/${ws.model.rpcenc.file}"
config="${ws.conf.rpcenc.file}">
<classpath>
<path refid="ws.class.path"/>
</classpath>
</wscompile>
[interface-config.xml]
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service
name="ProjectManagementService"
targetNamespace="urn:manplan:Services"
typeNamespace="urn:manplan:Types"
packageName="manplan.j2ee.webservice">
<interface name="manplan.j2ee.service.project.ProjectManager"/>
</service>
</configuration>OK. Found it: unlike Axis' java2wsdl does wscompile not support JavaBeans and so it gets confused by all those Project params and return types. So I guess wscompile is not the right tool for me in this situation?
Cheers,
Olaf -
Hey,
did anybody ever face this problem? I am working on it since hours, but cannot find any solution. my wsdl was generated from websphere studio
application developer 5.1.2. and now I run wscompile and get these error
messages.
when I compile my wsdl to get the client side artifacts like stub, etc and I get the following error message:
error: in message "SystemSupportException", part "fault" must specify a "element" attribute
the whole stack looks like this:
in message "SystemSupportException", part "fault" must specify a "element" attri
bute
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.handleLiteralS
OAPFault(WSDLModelerBase.java:1893)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOpe
rationRPCLiteralStyle(WSDLModelerBase.java:1764)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOpe
ration(WSDLModelerBase.java:663)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processPort(WS
DLModelerBase.java:548)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processService
(WSDLModelerBase.java:385)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.internalBuildM
odel(WSDLModelerBase.java:238)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSD
LModelerBase.java:146)
at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:
85)
at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:61)
at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:571)
at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22)
error: in message "SystemSupportException", part "fault" must specify a "element
" attribute
my wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://core.rbac.csap2" xmlns:impl="http://core.rbac.csap2" xmlns:intf="http://core.rbac.csap2" xmlns:tns2="http://exceptions.csap2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema targetNamespace="http://core.rbac.csap2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:impl="http://core.rbac.csap2" xmlns:intf="http://core.rbac.csap2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<element name="sessionId" nillable="true" type="xsd:string"/>
<element name="name" nillable="true" type="xsd:string"/>
<element name="password" nillable="true" type="xsd:string"/>
<element name="loginAndCreateSessionReturn" nillable="true" type="xsd:string"/>
</schema>
<schema targetNamespace="http://exceptions.csap2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:impl="http://core.rbac.csap2" xmlns:intf="http://core.rbac.csap2" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<complexType name="SystemSupportException">
<complexContent>
<extension base="tns2:CSAP2Exception">
<sequence/>
</extension>
</complexContent>
</complexType>
<complexType name="CSAP2Exception">
<sequence>
<element name="message" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
<element name="SystemSupportException" nillable="true" type="tns2:SystemSupportException"/>
</schema>
</wsdl:types>
<wsdl:message name="SystemSupportException">
<wsdl:part name="fault" type="tns2:SystemSupportException"/>
</wsdl:message>
<wsdl:message name="logoutResponse">
</wsdl:message>
<wsdl:message name="logoutRequest">
<wsdl:part name="sessionId" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="loginAndCreateSessionResponse">
<wsdl:part name="loginAndCreateSessionReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="loginAndCreateSessionRequest">
<wsdl:part name="name" type="xsd:string"/>
<wsdl:part name="password" type="xsd:string"/>
</wsdl:message>
<wsdl:portType name="SystemSupport">
<wsdl:operation name="logout" parameterOrder="sessionId">
<wsdl:input message="intf:logoutRequest" name="logoutRequest"/>
<wsdl:output message="intf:logoutResponse" name="logoutResponse"/>
<wsdl:fault message="intf:SystemSupportException" name="SystemSupportException"/>
</wsdl:operation>
<wsdl:operation name="loginAndCreateSession" parameterOrder="name password">
<wsdl:input message="intf:loginAndCreateSessionRequest" name="loginAndCreateSessionRequest"/>
<wsdl:output message="intf:loginAndCreateSessionResponse" name="loginAndCreateSessionResponse"/>
<wsdl:fault message="intf:SystemSupportException" name="SystemSupportException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SystemSupportSoapBinding" type="intf:SystemSupport">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="logout">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="logoutRequest">
<wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
</wsdl:input>
<wsdl:output name="logoutResponse">
<wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
</wsdl:output>
<wsdl:fault name="SystemSupportException">
<wsdlsoap:fault name="SystemSupportException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="loginAndCreateSession">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loginAndCreateSessionRequest">
<wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
</wsdl:input>
<wsdl:output name="loginAndCreateSessionResponse">
<wsdlsoap:body namespace="http://core.rbac.csap2" use="literal"/>
</wsdl:output>
<wsdl:fault name="SystemSupportException">
<wsdlsoap:fault name="SystemSupportException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SystemSupportService">
<wsdl:port binding="intf:SystemSupportSoapBinding" name="SystemSupport">
<wsdlsoap:address location="http://localhost:9080/CSAP2SysSupRouter/services/SystemSupport"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>I would be glad to get a response to this topic. I am really on my personal limits!
thanks and regards,
simonhi,
first of all your service user : SID_PIRWBUSR
has a wrong name it sould be PIRWBUSR
so check where did you define this SID_PIRWBUSR
Regards,
michal -
Wscompile, error: the following naming conflicts...
Hi,
I am stuck with a naming conflict in some wsdl that I cannot change.
The issue is apparently related to the names of types that differ
only by the case of the first letter, one is upper, the other is lower.
wscompile apparently tries to fix that with the generation of a Xxxx_Type
but fails.
I have investigated the <typeMappingRegistry> thing in the config.xml
for xml but there are very little info about that and so far, no success.
Any clue ? Thanks.Nota: The error occurs in wsi mode, i.e. document/literal mode.
One of the involved types, the simple one, is actually generated
from the operation name, this may be relevant.
Cheers.
JeanHuguesRobert -
Wscompile error : duplicate
environment: JAX-RPC Standard Implementation (1.1.2_01, build R40)
Server: Sun Application Server 8.0
Problem Statement:
We have two schemas suppose abc.xsd and cde.xsd which refer to one another i.e. abc.xsd imports cde.xsd and vice-versa (circular referencing).
There is a WSDL that imports in the type definition another schema say A.xsd which in turn imports abc.xsd. config-wsdl.xml refers to this WSDL.
On running the following command to generate server side artifacts:
wscompile -gen:server -d build -classpath build -mapping mapping.xml config-wsdl.xml
we get the following error:
error: modeler error: duplicate "element" entity
Is there any mechanism (like setting a flag/using some option )by which wscompile should include definitions of the schemas only once or some other solution to overcome this duplicate element entity error. Since there is no control over xsd's, we cannot modify the schema.
Thanks in advance
Regards
anjaliHi,
I have a duplicate error of another reason. I try to generate client stubs on a WSDL which has many identical type names but in different namespaces.
- Is there any way to tell wscompile to map the different namspaces automatically to different packagenames?
There will be more and more such webservices with identical types in different namespaces in it. I have to use them and I wan't have the possibility to write for each single webservice explicit namspace / packagename mappings in the config files.
- Does somebody know a solution? -
Wscompile error : exclusive attributes: "type", "substitutionGroup"
Hi All,
I'm trying to use wscompile with a WSDL file and a set of XSDs. It keeps failing with the following error
error: modeler error: model error: exclusive attributes: "type", "substitutionGroup"
all the XSDs are standard files available in "http://www.starstandards.org/STAR"
wscompile version is "JAX-RPC Standard Implementation (1.1.3, build R1)" and I am able to deploy services/access them using our own XSDs and the same approach.
Appreciate if anyone could help me figure out a solution for this.
Thanks,
NilanthaI'm getting the exact same problem when I compile my wsdl - hopefully someone will come up with a solution or at least a lead!!
Russ -
Wscompile error with PayPalSvc.wsdl
Hi,
I am trying to use wscompile to generate the client artifacts for the PaypalSvc.wsdl file.
The error is: error: modeler error: duplicate "complexType" entity: "AmountType"
The link to the wsdl file is: http://www.sandbox.paypal.com/wsdl/PayPalSvc.wsdl
My version of wscompile is: JAX-RPC Standard Implementation (1.1.2_04, build R45)
Thanks,
JimWe are having the same problem with the case changes in WSDL generation, preventing us from upgrading, too. Haven't heard a peep from Adobe on it.
- http://forums.adobe.com/message/1053957
Wish I could help more.
Fred -
Dear all,
searching the web for documentation about the wscompile tool results in (roughly) the same information as displayed when typing "wscompile -help" on the command line.
Does there happen to be any documentation about the meaning and (possible) cause of the various error message thrown from wscompile?
Thanks in advance.
Regards,
Jonatan SamoochaHi!
Is there any solution for this problem?
Thanks in advance
Eddy -
Wscompile: compilation error
Hi all,
I am using wscompile to create a web service client from a wsdl file. I get an error during compilation caused by some strange symbols in the generated code.
Has anyone an idea what may be wrong ? Or is it a bug in wscompile ?
Kind regards
Adrian
This is the output of wscompile:
ant -f STOCK-ProductTypesClient.xml
Buildfile: STOCK-ProductTypesClient.xml
init:
runWscompile:
[wscompile] command line: wscompile -d /home/azbaof/workspace/OrderManagementSystem/webServices/build "-features:searchschema, strict, noencodedtypes, serializeinterfaces, jaxbenumtype, nomultirefs, wsi, explicitcontext" -gen:client -keep -s /home/azbaof/workspace/OrderManagementSystem/webServices/src -verbose -Xprintstacktrace /home/azbaof/workspace/OrderManagementSystem/webServices/STOCK-ProductTypesClientConfig.xml -classpath /home/azbaof/jwsdp-1.4/jaxrpc/lib/jaxrpc-spi.jar:/home/azbaof/jwsdp-1.4/jaxrpc/lib/jaxrpc-impl.jar:/home/azbaof/jwsdp-1.4/jaxrpc/lib/jaxrpc-api.jar:/home/azbaof/jwsdp-1.4/jwsdp-shared/lib/activation.jar:/home/azbaof/jwsdp-1.4/jwsdp-shared/lib/jax-qname.jar:/home/azbaof/jwsdp-1.4/jwsdp-shared/lib/mail.jar:/home/azbaof/jwsdp-1.4/saaj/lib/saaj-api.jar:/home/azbaof/jwsdp-1.4/saaj/lib/saaj-impl.jar:/home/azbaof/jwsdp-1.4/jaxp/lib/endorsed/dom.jar:/home/azbaof/jwsdp-1.4/jaxp/lib/endorsed/sax.jar:/home/azbaof/jwsdp-1.4/jaxp/lib/endorsed/xercesImpl.jar:/home/azbaof/jwsdp-1.4/jaxp/lib/endorsed/xalan.jar:/home/azbaof/jwsdp-1.4/jaxp/lib/jaxp-api.jar
[wscompile] warning: Processing WS-I non conforming operation "WS_PTYPE" with RPC-Style and SOAP-encoded
[wscompile] [ServiceInterfaceGenerator: creating service interface: test.webServices.WS_PTYPE]
[wscompile] [ServiceGenerator: creating service: test.webServices.WS_PTYPE_Impl]
[wscompile] [CustomClassGenerator: generating JavaClass for: WS_PTYPE]
[wscompile] [CustomClassGenerator: generating JavaClass for: WS_PTYPEResponse]
[wscompile] [CustomClassGenerator: generating JavaClass for: PTYPES]
[wscompile] [CustomClassGenerator: generating JavaClass for: PRODUCT_TYPE]
[wscompile] [SOAPObjectSerializerGenerator: writing serializer/deserializer for: {urn:com-softwareag-entirex-rpc:STOCK}WS_PTYPE]
[wscompile] [SOAPObjectSerializerGenerator: writing serializer/deserializer for: {urn:com-softwareag-entirex-rpc:STOCK}WS_PTYPEResponse]
[wscompile] [SOAPObjectSerializerGenerator: writing serializer/deserializer for: {http://namespace.softwareag.com/entirex/xml/mapping}PTYPES]
[wscompile] [SOAPObjectSerializerGenerator: writing serializer/deserializer for: {http://namespace.softwareag.com/entirex/xml/mapping}PRODUCT_TYPE]
[wscompile] [SOAPObjectBuilderGenerator: writing object builder for: WS_PTYPEResponse]
[wscompile] [SOAPObjectBuilderGenerator: writing object builder for: PTYPES]
[wscompile] [SOAPObjectBuilderGenerator: writing object builder for: PRODUCT_TYPE]
[wscompile] [SerializerRegistryGenerator: creating serializer registry: test.webServices.WS_PTYPE_SerializerRegistry]
[wscompile] /home/azbaof/workspace/OrderManagementSystem/webServices/src/test/webServices/WS_PTYPE_SerializerRegistry.java:35: illegal start of expression
[wscompile] elemName, elemType, test.webServices.PRODUCT_TYPE.class, 1, [I@ba4211, SOAPVersion.SOAP_11);
[wscompile] ^
[wscompile] /home/azbaof/workspace/OrderManagementSystem/webServices/src/test/webServices/WS_PTYPE_SerializerRegistry.java:35: illegal character: \64
[wscompile] elemName, elemType, test.webServices.PRODUCT_TYPE.class, 1, [I@ba4211, SOAPVersion.SOAP_11);
[wscompile] ^
[wscompile] /home/azbaof/workspace/OrderManagementSystem/webServices/src/test/webServices/WS_PTYPE_SerializerRegistry.java:35: ')' expected
[wscompile] elemName, elemType, test.webServices.PRODUCT_TYPE.class, 1, [I@ba4211, SOAPVersion.SOAP_11);
[wscompile] ^
[wscompile] 3 errors
[wscompile] error: compilation failed, errors should have been reported
BUILD FAILEDAnd here is my wsdl file:
<?xml version='1.0' encoding='utf-8'?>
<!-- Generated Nov 8, 2004 4:05:54 PM by Software AG SOAP Toolkit Wizard, Version 7.1.1.60 -->
<definitions name='STOCK' targetNamespace='http://namespace.softwareag.com/entirex/xml/mapping'
xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/' xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:tns='http://namespace.softwareag.com/entirex/xml/mapping'
>
<types>
<schema targetNamespace='http://namespace.softwareag.com/entirex/xml/mapping' xmlns='http://www.w3.org/2001/XMLSchema'>
<xsd:complexType name='PTYPES'>
<xsd:sequence>
<xsd:element name='ArrayOfPRODUCT_TYPE' type='tns:ArrayOfPRODUCT_TYPE'/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name='ArrayOfPRODUCT_TYPE'>
<complexContent>
<restriction base='SOAP-ENC:Array'>
<attribute ref='SOAP-ENC:arrayType' wsdl:arrayType='tns:PRODUCT_TYPE[100]'/>
</restriction>
</complexContent>
</xsd:complexType>
<xsd:complexType name='PRODUCT_TYPE'>
<xsd:sequence>
<xsd:element name='NAME' type='xsd:string'/>
<xsd:element name='PTYPE-ID' type='xsd:decimal'/>
<xsd:element name='DESCRIPTION' type='xsd:string'/>
<xsd:element name='WEIGHT' type='xsd:decimal'/>
<xsd:element name='BULK-PIECE' type='xsd:decimal'/>
<xsd:element name='PRICE' type='xsd:decimal'/>
<xsd:element name='ID-VENDOR' type='xsd:decimal'/>
<xsd:element name='DELIVERY-TIME' type='xsd:decimal'/>
<xsd:element name='AMOUNT-IN-STOCK' type='xsd:decimal'/>
</xsd:sequence>
</xsd:complexType>
</schema>
</types>
<message name='WS_PTYPE'>
<part name='START-ISN' type='xsd:int'/>
</message>
<message name='WS_PTYPEResponse'>
<part name='START-ISN1' type='xsd:int'/>
<part name='PTYPES' type='tns:PTYPES'/>
</message>
<portType name='STOCKPort'>
<operation name='WS_PTYPE'>
<input message='tns:WS_PTYPE'/>
<output message='tns:WS_PTYPEResponse'/>
</operation>
</portType>
<binding name='STOCKSoapBinding' type='tns:STOCKPort'>
<soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='WS_PTYPE'>
<soap:operation soapAction='WS_PTYPE'/>
<input>
<soap:body use='encoded' encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
namespace='urn:com-softwareag-entirex-rpc:STOCK'
/>
</input>
<output>
<soap:body use='encoded' encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
namespace='urn:com-softwareag-entirex-rpc:STOCK'
/>
</output>
</operation>
</binding>
<service name='WS_PTYPE'>
<port name='STOCKPort' binding='tns:STOCKSoapBinding'>
<soap:address location='http://myHost:8080/entirex/xmlrt'/>
</port>
</service>
</definitions>Axis can create wsdl aotumatilly for each request.I don`t want to create wsdl, because I have already a wsdl file for an existing web service.
With Axis I have generated the client - classes, that means the stub, helper classes and
holders. I compiled the classes, and it works !
It depends on how to write client code. If your client
know your interface and endpoint, he doesn't need wsdl
at all. If the client don't know that, then he need
the wsdl and parse the wsdl(write lot of code) to get
the information like endpoint, method name,
parameters.....This is not the way I want it, as I said, the server exists. I want to generate a client
that corresponds to the wsdl-file, which describes the already running web service.
Once again: Is it possible for anybody to create a client via JWSDP 1.4 wscompile with
my wsdl file without the errors mentioned in my first posting ? If this is not possible, it
seems to be a bug in wscompile.
Thanks
Adrian -
Compilation error- xws-security sample aplication for signing
hi
I tried to run the sample application (xws-security) in JWSDP 1.6 but i am getting the following error.
[echo] Running wscompile....
[wscompile] C:\Sun\jwsdp-2.0\xws-security\samples\simple\build\server\WEB-INF\c
asses\simple\PingService.java:10: cannot access java.lang.Object
[wscompile] bad class file: C:\Sun\AppServer\jdk\jre\lib\rt.jar(java/lang/Objec
.class)
[wscompile] class file has wrong version 49.0, should be 48.0
[wscompile] Please remove or make sure it appears in the correct subdirectory o
the classpath.
[wscompile] public interface PingService extends javax.xml.rpc.Service {
[wscompile] ^
[wscompile] 1 error
[wscompile] error: compilation failed, errors should have been reportedit worked ....thank you ghstark
-
I�m trying to compile the HelloWorld Service example using ant tools, but i have this problem:
generate-server:
edit-config:
[wscompile] modeler error: failed to parse document at "C:\jwsdp-1.3\jaxrpc\samp
les\HelloWorld/C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl": j
ava.io.FileNotFoundException: C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\C:\jwsdp-1.
3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl (El nombre de archivo, direct
orio o etiqueta del volumen no es v�lido)
[wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildM
odel(WSDLModelerBase.java:179)
[wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelIn
fo.java:85)
[wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java
:61)
[wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.j
ava:564)
[wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
[wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:68
6)
[wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
[wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
[wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
[wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
[wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
[wscompile] CAUSE:
[wscompile] failed to parse document at "C:\jwsdp-1.3\jaxrpc\samples\HelloWorld/
C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl": java.io.FileNotF
oundException: C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\C:\jwsdp-1.3\jaxrpc\sample
s\HelloWorld\HelloWorldService.wsdl (El nombre de archivo, directorio o etiqueta
del volumen no es v�lido)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitionsNoImpo
rt(WSDLParser.java:252)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitions(WSDLP
arser.java:170)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parse(WSDLParser.java:
162)
[wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildM
odel(WSDLModelerBase.java:126)
[wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelIn
fo.java:85)
[wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java
:61)
[wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.j
ava:564)
[wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
[wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:68
6)
[wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
[wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
[wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
[wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
[wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
[wscompile] CAUSE:
[wscompile] java.io.FileNotFoundException: C:\jwsdp-1.3\jaxrpc\samples\HelloWorl
d\C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl (El nombre de ar
chivo, directorio o etiqueta del volumen no es v�lido)
[wscompile] at java.io.FileInputStream.open(Native Method)
[wscompile] at java.io.FileInputStream.<init>(FileInputStream.java:103)
[wscompile] at java.io.FileInputStream.<init>(FileInputStream.java:66)
[wscompile] at sun.net.www.protocol.file.FileURLConnection.connect(FileURLCo
nnection.java:69)
[wscompile] at sun.net.www.protocol.file.FileURLConnection.getInputStream(Fi
leURLConnection.java:156)
[wscompile] at java.net.URL.openStream(URL.java:960)
[wscompile] at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(XM
LEntityManager.java:947)
[wscompile] at org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntity
Manager.java:893)
[wscompile] at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(X
MLEntityManager.java:846)
[wscompile] at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(
XMLDocumentScannerImpl.java:264)
[wscompile] at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfigura
tion.java:513)
[wscompile] at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfigura
tion.java:595)
[wscompile] at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
[wscompile] at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:253)
[wscompile] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuil
derImpl.java:206)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitionsNoImpo
rt(WSDLParser.java:248)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parseDefinitions(WSDLP
arser.java:170)
[wscompile] at com.sun.xml.rpc.wsdl.parser.WSDLParser.parse(WSDLParser.java:
162)
[wscompile] at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildM
odel(WSDLModelerBase.java:126)
[wscompile] at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelIn
fo.java:85)
[wscompile] at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java
:61)
[wscompile] at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.j
ava:564)
[wscompile] at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:40)
[wscompile] at com.sun.xml.rpc.tools.ant.Wscompile.execute(Wscompile.java:68
6)
[wscompile] at org.apache.tools.ant.Task.perform(Task.java:341)
[wscompile] at org.apache.tools.ant.Target.execute(Target.java:309)
[wscompile] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[wscompile] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[wscompile] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
[wscompile] at org.apache.tools.ant.Main.runBuild(Main.java:609)
[wscompile] at org.apache.tools.ant.Main.start(Main.java:196)
[wscompile] at org.apache.tools.ant.Main.main(Main.java:235)
[wscompile] error: modeler error: failed to parse document at "C:\jwsdp-1.3\jaxr
pc\samples\HelloWorld/C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.w
sdl": java.io.FileNotFoundException: C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\C:\j
wsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl (El nombre de archivo,
directorio o etiqueta del volumen no es v�lido)
[wscompile] Command invoked: wscompile -d C:\jwsdp-1.3\jaxrpc\build\samples\Hell
oWorld\classes\server -import -keep -model C:\jwsdp-1.3\jaxrpc\build\samples\Hel
loWorld\model-wsdl-rpcenc.xml.gz -Xprintstacktrace C:\jwsdp-1.3\jaxrpc\samples\H
elloWorld\etc\config.xml -classpath C:\jwsdp-1.3\jwsdp-shared\lib\mail.jar;C:\jw
sdp-1.3\jwsdp-shared\lib\activation.jar;C:\jwsdp-1.3\jaxp\lib\jaxp-api.jar;C:\jw
sdp-1.3\jaxp\lib\endorsed\dom.jar;C:\jwsdp-1.3\jaxp\lib\endorsed\sax.jar;C:\jwsd
p-1.3\jaxp\lib\endorsed\xalan.jar;C:\jwsdp-1.3\jaxp\lib\endorsed\xercesImpl.jar;
C:\jwsdp-1.3\jaxrpc\lib\jaxrpc-api.jar;C:\jwsdp-1.3\jaxrpc\lib\jaxrpc-spi.jar;C:
\jwsdp-1.3\jaxrpc\lib\jaxrpc-impl.jar;C:\jwsdp-1.3\saaj\lib\saaj-api.jar;C:\jwsd
p-1.3\saaj\lib\saaj-impl.jar;C:\jwsdp-1.3\jwsdp-shared\lib\relaxngDatatype.jar;C
:\jwsdp-1.3\jwsdp-shared\lib\xsdlib.jar;C:\jwsdp-1.3\jwsdp-shared\lib\jax-qname.
jar;C:\jwsdp-1.3\apache-ant\lib\ant.jar;C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\$
{compile.classpath}
BUILD FAILED
file:C:/jwsdp-1.3/jaxrpc/samples/HelloWorld/build.xml:98: wscompile failed
Total time: 1 second
Anybody knows how I can solve it?
Thanks!!The generator cannot find the correct path to the WSDL file. The ant script failed because it cannot find the file located at:
C:\jwsdp-1.3\jaxrpc\samp
les\HelloWorld/C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl
obviouisly, this is an incorrect filepath. You need to fix that so it should read:
C:\jwsdp-1.3\jaxrpc\samples\HelloWorld\HelloWorldService.wsdl -
Wscompile: -mapping is an invalid option or argument
Hi,
I am using the wscompile to generate my ports and mappings for a webservice from a given wsdl. I am using the following ant-task:
<wscompile
import="true"
nonClassDir="${webservice.ports}"
features="nodatabinding,documentliteral,wsi"
mapping="${webservice.ports}/${mapping.file}"
config="${resources.main.dir}/${config.file}"
base="${webservice.ports.classes}"
sourceBase="${webservice.ports.src}"
>
<classpath refid="project.classpath"/>
</wscompile>which gives me the following error:
[wscompile] error: -mapping is an invalid option or argument
[wscompile] Command invoked: wscompile -d /workspace/WebserviceDefinitions/target/ports/classes
-features:nodatabinding,documentliteral,wsi
-import
-keep
-mapping /workspace/WebserviceDefinitions/target/ports/signupservices-mapping.xml
-nd /workspace/WebserviceDefinitions/target/ports
-s /workspace/WebserviceDefinitions/target/ports/src /workspace/WebserviceDefinitions/src/main/resources/signupservices-config.xml -classpath /workspace/WebserviceDefinitions/bin:/workspace/libraries/xmlbeans/jsr173_api.jar:/workspace/libraries/xmlbeans/resolver.jar:/workspace/libraries/xmlbeans/xbean_xpath.jar:/workspace/libraries/xmlbeans/xbean.jar:/workspace/libraries/xmlbeans/xmlpublic.jar:/workspace/libraries/jaxrpc/jaxrpc-api.jar:/workspace/libraries/jaxrpc/jaxrpc-impl.jar:/workspace/libraries/jaxrpc/jaxrpc-spi.jar:/workspace/libraries/wsdl2java/wsdl4j.jar:/workspace/libraries/rpc/jaxrpc.jar:/workspace/libraries/rpc/saaj.jarDoes anybody have an idea what's going wrong here?!
cheers
stfApparently the mapping problem is a known error. To get around it, use the fork option in your wscompile task. For example:
<!-- This target compiles the server components using an existing WSDL as the driving document.
The configuration file must use the <wsdl> element giving the location (local file system
or URL) of the WSDL document.
Note: the fork argument is needed to over come a bug when using the mapping argument. See
http://forum.java.sun.com/thread.jspa?threadID=592994&tstart=0
-->
<target name="generate-server-from-WSDL" depends="init">
<wscompile fork="yes"
keep="true"
base="${basedir}/WebContent/WEB-INF/classes"
import="true"
features="wsi"
xPrintStackTrace="true"
verbose="true"
mapping="${basedir}/WebContent/WEB-INF/jaxrpc-mapping.xml"
sourcebase="${basedir}/src"
config="${config.server.doclit.file}">
<classpath>
<path refid="compile.classpath" />
</classpath>
</wscompile>
</target> -
JSE webservice deployment problem
Hi when i try to deploy a helloworld jse i am getting an wscompile error. wscompile-init:
G:\javap\servlet\src\HelloWorldWS\nbproject\build-impl.xml:226: taskdef class com.sun.xml.rpc.tools.ant.Wscompile cannot be found
BUILD FAILED (total time: 3 seconds).
Can anyone help me in thisSome more info:
http://www.davemeikle.co.uk/cgi-bin/blog.py
sun java studio enterprise 8 and jboss web services
If anyone has tried to deploy a Web Service to JBoss 4.x from Java Studio Enterprise 8 they may have came across this problem:
taskdef class com.sun.xml.rpc.tools.ant.Wscompile cannot be found
The reasons for this are that a) you do not have the jaxrpc-impl.jar in your class path, and b) you are required to change your wscompile.classpath setting in the projects project.properties file.
Once this is done you can happily develop and deploy Web Services on JBoss.
http://www.codecomments.com/message667170.html
I'm trying to make a web service in NB5 beta. It seemed to work easily enough until I tried to build the application. Then it died with this error:
taskdef class com.sun.xml.rpc.tools.ant.Wscompile cannot be found...
...I just added the JAXRPC library to my project from the pre-existing list and it's working
http://blog.gmane.org/gmane.comp.java.ide.netbeans.user/month=20050501
Take a look at Axis ( http://ws.apache.org/axis/ ), it certainly works great with Tomcat ... -
Make a servlet as a web service
hi, is there a way to make a servlet, which display some data on browser as a
web service and consume this by a client (oder servlet)? Normaly web services has a method which operate inside
the web service class and do something. In case of my servlet i try to declare
doGet as a serice method and i think it is not possible to do it. When i try to
create a service like this i get wscompile error.
Please take a look also on my topic here, which show the
error message and some more detail about my problem:
http://forum.java.sun.com/thread.jspa?threadID=694666&tstart=0
thanks at advanceHi,
I'm not familiar with ejb and if you are asking, am i able to create
java normal classes and compile dem, yes it is still possible and
i can create services and consume them (but as i wrote
not servlet class as service).
I dont know still, whether it is possible to make a servlet class as
service or i should change somewhat to be able
to proide service! I didnt find tutorial or samples for this case .
regards
Maybe you are looking for
-
How do I sync 3 phones on one computer?
My daughters have new iphone 5's. We need to connect them to my computer to get their music but I do not want my contacts to dump onto their iphones. How do I prevent this?
-
I have a laserjet P3015 that randomly stops printing documents from client machines. The only way to resume printing is to log into the printer sever and send a test page. This allows all clients to resume printing. Unfortunatey problem returns some
-
after updating to ios 6.1.3 seems my factory unlocked 3gs is not working, i cant even restore..the message displayed is "itunes software update server cannot be contacted" 'm using latest itunes with winows xp system...........please please help me
-
Component Palette --- "User Defined Extension Functions" not visible
I added a User-Defined XPath Extension Function in JDeveloper 11.1.1.3.0 --> Tools > Preferences > SOA As given here http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_appx_functs.htm#BEIHEBIJ But I am not able see "User Defined
-
Export data to flat file with no delimiter
Hi I've 3 columns in a view that i want to export to a flat file. I don't want the flat file to contain any delimiter such as commas , tabs etc.. I am using fixed width with the following setting Header row delimiter {CR}-{LF} Advance Options : Inpu