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 142367 - Run action removes content of build/web/WEB-INF/classes
Summary: Run action removes content of build/web/WEB-INF/classes
Status: RESOLVED DUPLICATE of bug 142360
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 10:17 UTC by Milan Kuchtiak
Modified: 2008-08-04 00:52 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kuchtiak 2008-07-31 10:17:42 UTC
WS Support generates, and compiles, JAX-WS stubs into build/web/WEB-INF/classes directory. Run action removes the
content of this directory, That breaks entirely WS Functionality.
See also very similar issue 142360.

Note: this has something to do with "Deploy on Change" feature.
Comment 1 Petr Jiricka 2008-08-01 16:52:34 UTC
So Milan, does the same hotfix need to be done for web projects as was done for J2SE projects in issue 142360? I think
this is a beta stopper, so something needs to be done by Monday. Thanks.
Comment 2 Vince Kraemer 2008-08-01 21:42:07 UTC
I cannot reproduce this after I applied the fix for issue 142392...

Since there are not steps that outline how to produce this issue, I may just have taken a successful path, while the
filer  took an unsuccessful one.

Here is what I did...


1. create a web app project to host a service.
2. created the service. echo(String s) => s+s
3. deployed the service.
4. used the GF admin gui to test the service
   it worked correctly
5. created a new web project... to be a client.
6. ran the project
   saw the standard Hello world message.
7. created a servlet
8. used Run File to verify that the servlet would run correctly
   double checking the fix for issue 142392 in the process... it ran correctly.
9. used the wizard to add a call to the web service that was created in step 2 and tested in step 4.
10. used Run File on the servlet again
   saw the correct value... including the response from the WS.

FILER:  does this resemble the steps you followed to produce this issue initially?

Comment 3 David Konecny 2008-08-04 00:52:57 UTC
Temporary fix applied by Milan in issue 142360 solves this issue as well. 

*** This issue has been marked as a duplicate of 142360 ***