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.

Bug 123394 - [jaxws]Use local wsdl in archive at runtime
Summary: [jaxws]Use local wsdl in archive at runtime
Status: NEW
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Roderico Cruz
: 121914 (view as bug list)
Depends on:
Blocks: 117865
  Show dependency tree
Reported: 2007-12-04 20:53 UTC by Roderico Cruz
Modified: 2009-11-24 10:22 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Roderico Cruz 2007-12-04 20:53:54 UTC
The deployed web service archive should include the OASIS catalog (with the well-known catalog name). In jaxws, if the
catalog is included in deployment, this optimizes the runtime performance as wsdl/schema retrieval from the network will
be avoided.
Comment 1 Lukas Jungmann 2007-12-04 22:55:59 UTC
Using relative location in wsimport ant task looks to me easier to implement then using catalog,
see issue 121914 and
for more details, please.
Comment 2 Roderico Cruz 2007-12-15 00:18:37 UTC
You're right. We'll implement this using the -wsdlLocation flag of wsimport.
Comment 3 Roderico Cruz 2007-12-15 00:28:08 UTC
*** Issue 121914 has been marked as a duplicate of this issue. ***
Comment 4 Lukas Jungmann 2008-04-14 17:14:29 UTC
moving opened issues where TM != dev to TM=TBD
Comment 5 Mei Wu 2009-11-24 10:22:21 UTC
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"/>

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.