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 56824 - mapping file should be generated at META-INF
Summary: mapping file should be generated at META-INF
Status: CLOSED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ pcw
URL:
Keywords: RELNOTE
Depends on:
Blocks:
 
Reported: 2005-03-23 02:10 UTC by Yutaka Yoshida
Modified: 2006-03-24 12:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Instructions on upgrading existing projects that contain web services or clients (1.50 KB, text/plain)
2005-04-02 01:47 UTC, _ pcw 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yutaka Yoshida 2005-03-23 02:10:26 UTC 
Right now, webservice mapping file is generated at
META-INF/wsdl or WEB-INF/wsdl, but according to the
BluePrints book "Designing Web Services with the J2EE
1.4 Platform", page117-119, it should be placed under
META-INF or WEB-INF.
Comment 1 Yutaka Yoshida 2005-03-24 19:02:07 UTC 
Also, file names in META[WEB]-INF are not aligned with
BluePrints naming convention:-
http://java.sun.com/blueprints/code/namingconventions.html
see the names of mapping file and config file in section 4.
Comment 2 _ pcw 2005-03-31 18:11:03 UTC 
Changing the location of the mapping file as referenced in new project is fairly
easy.  The issue here is upgrading existing projects.

If this location is changed, previously existing projects that contain web
services or clients will have a new build file referring to the new location and
existing webservices.xml or web.xml/service-ref entries that refer to the old
location.

The only way to safely upgrade the existing projects is via a project open hook
that detects the old DD entries and fixes them.  This will add unnecessary
overhead to all project open's for a problem that should be in the minority. 
However, if this is not done, anyone that has a preexisting project fitting this
description will have to manually make the changes, or deployment will fail.
Comment 3 Petr Blaha 2005-04-01 09:22:34 UTC 
Since we didn't release officially release of j2ee features, QE team agrees with
changing location without support update existing projects. I suggest to add
comment 'How does update existing project ' in release note.
Comment 4 Petr Jiricka 2005-04-01 12:30:04 UTC 
I agree with Petr B - let's fix this now. The final release will be downloaded
by five times as many users as the prereleases; now we don't have the real
exposure yet. Of course we need to fix all our sample projects that we ship or
offer for download on the web. The reset can be release noted.
Comment 5 _ pcw 2005-04-02 01:47:08 UTC 
Fixed and integrated (no upgrade code - existing projects will require manual
upgrading.)  See next attachment for tentative upgrade instructions.
Comment 6 _ pcw 2005-04-02 01:47:51 UTC 
Created attachment 21306 [details]
Instructions on upgrading existing projects that contain web services or clients
Comment 7 Jan Horvath 2005-07-13 13:37:36 UTC 
v.