For the renaming part that is purely a server error I don't think that
it is actually a server problem though.
With the following:
Start with a working application as in the guide though I cannot get it
to test the deployment and run works so it is fine.
Scenario 1
1. right click on the application and select run. You will see the
application being deployed.
2. right click on the application and select run again. You will see the
application being deployed again.
All is fine in the world.
Scenario 2
1. right click on the application and select deploy. You will see the
application being deployed.
2. make a change to the code, such as adding a space to make sure it
will recognize a change.
3. right click on the application and select deploy. You will see the
application being deployed.
4. you will see the application deployment failing due to the rename
error.
All is not right in the application world.
It is like NB does not shut down the server correctly. This has nothing
to do with doing any renaming of anything within netbeans. It is trying
to rename the files that were deployed to filename_old in glassfish to
avoid overwriting them. I am not sure if this is a NB problem or a
glassfish problem I just know what the result is.
Now if I manually shut down the server and then deploy it will start the
server and deploy correctly. It is only after I do a deploy through NB
that this happens.
So the workaround for this is to shutdown the server manually before a
second deploy. If a deploy fails then shutdown the server and let NB
start is with the deploy.
Dru Devore
> -------- Original Message --------
> Subject: Re: JAX-WS 2.0 with NetBeans 5.0
> From: Bobby Bissett - Javasoft <bobby.bissett_at_sun.com>
> Date: Wed, February 08, 2006 1:47 pm
> To: users_at_jax-ws.dev.java.net
>
> > I am not trying to rename the application. If you deploy the project
> > then make a change to the application and deploy again or select Run
> > Project it will try to deploy the project and throws the error.
>
> Ok, *now* I'm seeing some similar errors. I don't know what causes that,
> but am going to try things again with build 36 since you have that one
> and see if I can check with someone on the GlassFish team. The
> workaround (obviously) is to make a new project instead of changing the
> example one, but it seems strange to me that I can't change some code
> and redeploy it! I'm sure there is just something I'm leaving out, or it
> may have to do with "file in use" issues (am going to try on Solaris now).
>
> Thanks for bringing up that the tips section didn't match the rest --
> the renaming part was written and tested when I wrote the standalone
> (using tomcat built into NB) version of the article. I have corrected it
> and, for now, mention just creating a new project rather than suggesting
> changing the package and classes in the old one. Will look into the
> "rename app" problem and will let you know if I come up with something.
>
> Thanks,
> Bobby
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net