I've just started in a project where we thinking about develop with J2EE
reference impl.
I have been using Weblogic for some time and is of course used to that way
of developing and deployment.
What I realise with J2EEri is that you have to package every bean in a jar
file before deploying. Not only the actual remote, home and implementation
classes but all their super classes as well.
As I have understood, that if you recompile the implementation class
without any changes in the signature, you have to redeploy the whole bean.
I have examined the command line options for the deployer as well but they
seem to be as cumbersome.
We wanted to use the J2EEri to avoid vendor lockups. And when we would
deploy the system, we would choose an app server (please spare me any
comments on this...). After that I have tried out the deployment in J2EEri,
I doubt that it is possible to use for development at all, just to prove
that your EJB application follows the EJB specification, which would mean
hours of deployment related work.
Does anyone have any comments on this?
regards
Erik Romson
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
