This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | [jaxws]Use local wsdl in archive at runtime | ||
---|---|---|---|
Product: | webservices | Reporter: | Roderico Cruz <rcruz> |
Component: | Code | Assignee: | Roderico Cruz <rcruz> |
Status: | NEW --- | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 117865 |
Description
Roderico Cruz
2007-12-04 20:53:54 UTC
Using relative location in wsimport ant task looks to me easier to implement then using catalog, see issue 121914 and https://jax-ws.dev.java.net/guide/Developing_client_application_with_locally_packaged_WSDL.html#Using__wsdlLocation_switch for more details, please. You're right. We'll implement this using the -wsdlLocation flag of wsimport. *** Issue 121914 has been marked as a duplicate of this issue. *** moving opened issues where TM != dev to TM=TBD This issue still exists for 6.7.1. If one uses a wsdl in file system, build the project and then trying to deploy the project to another env, the problem with the absolute file path pops up. I have to do the following 2 things: 1. Copy the wsdl to somewhere that will be accessible to runtime code, in build.xml, I added: <target name="-pre-compile"> <!-- Empty placeholder for easier customization. --> <!-- You can override this target in the ../build.xml file. --> <copy todir="${build.classes.dir}"> <fileset dir="${webinf.dir}" includes="TaskCommon.wsdl"/> </copy> </target> 2. Hand edit the jaxws-build.xml, add wsdlLocation="../../../../TaskCommon.wsdl" to wsimport task. I think it is a significant bug, in the case of releasing the GFESBV22, the web project has to be built and preinstalled, without this workaround, the web project deployed has the physical address of the build machine for its wsdl reference. |