completing the web project in netbeans

i'm really need an explaination on how to finishing my project so that my
project can be execute as and existing source on other machine
--
View this message in context: http://www.nabble.com/completing-th...8p17660948.html
Sent from the Netbeans - J2EE mailing list archive at Nabble.com.

I am not sure I understand your question. If you create a web application
doing a clean and build, you will produce a .war file in the dist directory
of your project. This .war file can be deployed to your target server. This
has some caveats which are not related to the application itself per se.

1. The target server should match the type of server you developed on. For
example, developed on Glassfish to deploy on Glassfish. If you deploy it to
another application server, it may have specific deployment requirements.
Glassfish and apache Tomcat are generally OK.

2. Any resources like databases need to be configured on the target server.

John

On Wed, Jun 4, 2008 at 10:47 PM, imp117 <mr_ibrahim117-/E1597aS9LQAvxtiuMwx3
w@public.gmane.org> wrote:

>
> i'm really need an explaination on how to finishing my project so that my
> project can be execute as and existing source on other machine
> --
> View this message in context:
> http://www.nabble.com/completing-th...48
.html
> Sent from the Netbeans - J2EE mailing list archive at Nabble.com.
>
>


--
John Yeary
--
http://javaevangelist.blogspot.com

"Far better it is to dare might things, to win glorious triumphs, even
though checkered by failure,

than to take rank with those poor spirits who neither enjoy much nor suffer
much, because they live in the grey

twilight that knows not victory nor defeat." -- Theodore Roosevelt

John Yeary-2 wrote:
>
> I am not sure I understand your question. If you create a web application
> doing a clean and build, you will produce a .war file in the dist
> directory
> of your project. This .war file can be deployed to your target server.
> This
> has some caveats which are not related to the application itself per se.
>
> 1. The target server should match the type of server you developed on. For
> example, developed on Glassfish to deploy on Glassfish. If you deploy it
> to
> another application server, it may have specific deployment requirements.
> Glassfish and apache Tomcat are generally OK.
>
> 2. Any resources like databases need to be configured on the target
> server.
>
> John
>
> On Wed, Jun 4, 2008 at 10:47 PM, imp117 <mr_ibrahim117-/E1597aS9LQAvxtiuMw
x3w@public.gmane.org> wrote:
> 
>
>
> --
> John Yeary
> --
> http://javaevangelist.blogspot.com
>
> "Far better it is to dare might things, to win glorious triumphs, even
> though checkered by failure,
>
> than to take rank with those poor spirits who neither enjoy much nor
> suffer
> much, because they live in the grey
>
> twilight that knows not victory nor defeat." -- Theodore Roosevelt
>
>


yeah!! that solved my problems, thanks bro.
--
View this message in context: http://www.nabble.com/completing-th...8p17725240.html
Sent from the Netbeans - J2EE mailing list archive at Nabble.com.