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 140925 - [65cat] build/deploy issues with WebJpa example app
Summary: [65cat] build/deploy issues with WebJpa example app
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Windows Vista
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-20 21:14 UTC by pbelbin
Modified: 2008-09-24 21:09 UTC (History)
1 user (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 pbelbin 2008-07-20 21:14:30 UTC
[ BUILD # : 200807170007 ]
[ JDK VERSION : 1.6.0_07 ]

initial deployment works ok, but, doing a 'clean and build' followed
by an 'undeploy and redeploy' produces the following error:

deployment started : 0%
Deploying application in domain failed; Deployment Error -- Could not
resolve a persistence unit corresponding to the
persistence-unit-ref-name
[enterprise.web_jpa_war.servlet.ListPersonServlet/emf] in scope of
the module called [C:\nbprojects\WebJpa\build\web]. Please verify
your application.
Deployment error:
The module has not been deployed.
See the server log for details.
        at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(
Deployment.java:193)
        at
org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:104)
        at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown
Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
orImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java
:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:357)
        at org.apache.tools.ant.Target.performTasks(Target.java:385)
        at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
        at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
        at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExec
utor.java:41)
        at
org.apache.tools.ant.Project.executeTargets(Project.java:1189)
        at
org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java
:273)
        at
org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java
:485)
        at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151
)
Caused by: The module has not been deployed.
        at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(
Deployment.java:187)
        ... 16 more
BUILD FAILED (total time: 0 seconds)


the above error is repeatable.

same thing when you change the source from JDK5 to JDK6 and 'update
and deploy'.
Comment 1 Vince Kraemer 2008-07-20 23:27:10 UTC
what is your deployment server in this situation?
Comment 2 pbelbin 2008-07-21 15:16:59 UTC
glassfish v2 that comes with the daily build.
Comment 3 Vince Kraemer 2008-09-23 19:13:52 UTC
clean and build is problematic on windows when you have an app deployed... before doing a clean and build... undeploy
the app.  following this advice will save you a lot of trouble.  one other bit of advice: use the Run item to deploy
changes incrementally. 
Comment 4 Vince Kraemer 2008-09-24 04:55:08 UTC
I have been trying to reproduce this but haven't been able to.

Please provide a set of detailed steps that I can follow to reproduce this issue...

The most interesting steps would be any actions that you perform after the first successful deploy and the unsuccessful
deploy.

Attaching a copy of the server log and the IDE log would be helpful, too.
Comment 5 pbelbin 2008-09-24 21:00:35 UTC
I tried reproducing this error, and find that I am unable to do so now too.

I suspect it's because there have been other things in the deploy to server area that have changed between when I 
originally reported this and now.

in any case, I don't believe it's an issue any more.

Comment 6 Vince Kraemer 2008-09-24 21:09:16 UTC
thanks for the updated info.