[ome-devel] OMERO and Ports for Productionsystem

[Gernot Stocker]

Hi Josh,
sorry for the delayed answer but I was busy during the last days. 

On Tuesday 30 September 2008, josh.moore at gmx.de wrote:
> [...]
> I installed your configuration into JBoss 4.2.3, with OMERO Beta3.0.1
> and didn't get the error you were having:
> 

OK, that's not what I hoped to read from you ;-)

> [...]
> How dependent are your web apps on JBoss 4.2.1? Would it be possible
> for you to upgrade to OMERO Beta3 and JBoss 4.2.3 and test this out?
> (Psst, don't tell, but OMERO Beta3.1 will be coming out very soon if
> that makes a difference). The Beta3 series is a pretty big jump in
> terms of tech, so it would probably be to your benefit anyway.

OK that's great news! I've seen, that Beta3.1(Oct 2008) is out NOW and 
if the client is working now we will develop against this version. This 
brings me to an important question regarding API stability of the Client. 

We would like to include in one of our next iLAP releases the OMERO-
support. How stable is the client and how different will the OmeroBlitz-
API for OMERO 4 compared to the current RMI Client 3.1?

 > If you definitely need to stay on the Beta2.3 version, the most
> complete solution will be the support offered by Glencoe Software. 

Since all of our JBoss-instances are running independently from each other 
we can easily switch version for one single application. I will immediately 
try out the Beta 3.1 release and report my experiences with it regarding 
the ports problem.

Thanks, 
Gernot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20081001/d32136af/attachment.pgp