EJB3 plans ?

[Bobby Abraham]

I have been scanning the geronimo lists and haven't seen any discussion
of moves toward ejb3 or jsr220 support.

Has any of this development stated yet ?
Should I be looking on openejb lists for this discussion ?

I am interested to know if the plan is to extend openejb or to add
another a persistence container like glassfish or hibernate3 for this
support.  

I understand the licensing issue regarding hibernate (LGPL) but the
glassfish license may be compatible with the apache licence, no ?


-- 
Bobby Abraham <[EMAIL PROTECTED]>
Subtle Guru


signature.asc
Description: This is a digitally signed message part

Re: The autodeploy feature in Geronimo

[Bobby Abraham]

On Sun, 2005-10-23 at 16:00 -0600, Jeff Genender wrote:
> 
> Sachin Patel wrote:
> > 
> > 
> > Jacek Laskowski wrote:
> > 
> >  Am I right that the simplest solution is to develop a GBean that
> > 
> >> would monitor a directory and hand over a deployable to a deployer?
> > 
> > 
> > This was my thinking as well.  The directory would listen for adds, 
> > modifications, and deletions.
> 
> I think this may be somewhat confusing.  I think when dropping in the 
> directory, it should should deploy...then be immediately removed from 
> the directory.  IMHO, this dir should be for hot deploy only.  Let the 
> deployer decide if it should be updated or added.  I think the deletions 
> should not be done through this dir.  We should use the normal undeploy 
> capabilities of the deployer.


As a user it would be nice if a copy to the hot-deploy directory had the
effect of an undeploy of any existing application of the same name and
then reployment of the new one.  This is the most common use case within
development.

It is also very common for the copy to the hot-deploy directory to be
over a slower network.  When this happens it is important to check that
the file is not still being written and avoid deploying an application
before the copy is complete.

There is also the issue of deploying with a separate plan.  In this case
I suggest copying the plan first and ignoring it until the application
is copied, then use the plan for the hot deployment and finally remove
both the plan and the application from the hot-deploy directory. 

- bobby

-- 
Bobby Abraham <[EMAIL PROTECTED]>
Subtle Guru


signature.asc
Description: This is a digitally signed message part

JDK 1.5 Compatibily

[Bobby Abraham]

The jdk 1.5 breakage of Geronimo Corba is a known issue mentioned in the
release notes for M5.

It appears, at first glance, that it is only the corba subsystem which
suffers from this problem.  Do any of the other modules depend on a
running corba subsystem or can I safely ignore these problems under jdk
1.5 ?

While the J2EE 1.4 certification requires corba many people are now
using annotations and ejb3 persistence and it would good if geronimo
allowed and encouraged this.  

Is it feasible to have corba just "fail quietly with an appropriate
message" when running under any JDK other than Sun 1.4 JDK ?  I believe
that same issue applies to the IBM or JRocket JDK's.

- bobby 
  
-- 
Bobby Abraham <[EMAIL PROTECTED]>
Subtle Guru


signature.asc
Description: This is a digitally signed message part