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 87913 - [55cat] Project Deploy Fails consistently after previously working
Summary: [55cat] Project Deploy Fails consistently after previously working
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: Macintosh Mac OS X
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-25 00:19 UTC by byteme
Modified: 2006-10-25 14:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NetBeans Log File (84.22 KB, text/plain)
2006-10-25 00:20 UTC, byteme
Details

Note You need to log in before you can comment on or make changes to this bug.
Description byteme 2006-10-25 00:19:27 UTC
[ JDK VERSION : 1.5.0_06 ]

I am developing a Java EE 5 Project made up of servlets and EJBs.  It was deploying and running fine on GlassFish-v1-b14 and SJAS that shipped with RC2.  Now it just stops deploying after a few debug sessions.

1.  I have restarted the IDE.
2.  I have deleted the build-impl and had the IDE re-generate it
3.  I have cleaned and re-built the project and its dependencies
4.  I have run the Verifier --> no errors or warning

It still complains about a class that it used to include in a dependent project.  Which I configured in the properties of the project.  I added the project as a dependency.
Comment 1 byteme 2006-10-25 00:20:00 UTC
Created attachment 35511 [details]
NetBeans Log File
Comment 2 byteme 2006-10-25 14:32:52 UTC
Did some more research on this issue.  It is a JAXB + Web Service annotation
issue.  I did clean install of the new 6.0 M4 and got the same error.  If you
use the @WebService annotation you need to make sure the elements in the java
object you are making into a Web Service are JAXB compatible.  The confusion
arose with the failed deployment errors and no concrete messages.  I will close
this report and make a note somewhere else for better error reporting with Java
EE 5 + JAXB 2.0 + Web Services.

Thanks.