Hi,
Thank you for the comments.
For part 3), I meant:
In J2SDKEE1.2.1 or JBoss, they both jar the classes and the descriptor
together in one jar file and then just deploy the jar file. I find that this
way is very neat. As for Jonas, skel and stubs are created and the classpath
must include them. How and what must I do if I want to develop in one
machine (where the source is) and deploy them in another machine. Am I
suppose to copy all the class files and the .xml file to the production
machine? Having all in 1 jar file is good when the source code(development)
and deployment is on different machines.
Would like to hear your views on this.
Thanks.
Regards,
Ken, See Kai Leong
----- Original Message -----
From: "H�l�ne JOANIN" <[EMAIL PROTECTED]>
To: "See Kai Leong, Ken" <[EMAIL PROTECTED]>
Cc: "Jonas-User Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, September 19, 2000 19:59
Subject: Re: Deployment
> Hi,
> Comments are embedded.
> Kind regards.
> H�l�ne.
>
> "See Kai Leong, Ken" wrote:
> >
> > Hi,
> >
> > After going through the documentation of Jonas and run the examples, I
have
> > a few questions:
> >
> > 1) Am I right to say that for each bean, I must start EJBServer with a
> > jonas.properties and the .xml in the path.
> Not exactly.
> You can specify a coma-separated list of file's names in the
> jonas.beans.descriptors property.
> Name is either the name of the standard XML deployment descriptor file,
> or the name of the ejb-jar file.
> Ex:
> jonas.beans.descriptors X.xml,Y.xml,Z.jar
> You can have look to
> http://www.objectweb.org/messages/JonasUsers/2000/07/msg00069.html
> for futher information.
> >
> > 2) If I changed my bean by adding an extra function, am I going to stop
the
> > EJBServer and start it again? This is no good in a production
environment
> You are not really be able actually to do that with the current version
> of
> JOnAS, even with the JonasAdmin tool.
> This task is planned for a future version.
> >
> > 3) Deployment means starting a new EJBServer. I cannot deploy my beans
on a
> > running EJBServer right since it needs the jonas.properties and .xml
file at
> > startup.
> Yes you can, by using the JonasAdmin tool (see the -a option).
> >
> > I am currently deciding on an EJB Server that uses as little server
> > specified functions and that development and deployment should be as
close
> > to J2EE as possible.
> JOnAS follows the EJB specification version 1.1 .
> >
> > I see that with newbean and JonasAdmin, Jonas seems to be ahead of e.g.
> > JBoss but the deployment seems to be not using ejb-jar in the INF
directory.
> "... but the deployment seems to be not using ejb-jar in the INF
> directory "
> Sorry, but I don't understand what you mean.
> >
> > I would like to hear some comments from you guys on this.
> >
> --
> -=- H�l�ne JOANIN -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> mailto:[EMAIL PROTECTED] http://www.evidian.com
> Phone: 33.4.76.29.73.53 Fax: 33.4.76.29.76.00
> Download our EJB Server JOnAS at http://www.objectweb.org
> ----
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body of the message "unsubscribe jonas-users".
> For general help, send email to [EMAIL PROTECTED] and
> include in the body of the message "help".
>
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
