I just merged the fix into branches/2.0 and will deploy an updated set of 2.0.3-SNAPSHOT artifacts to the repo this afternoon.

Please visit the WASCE forum on the IBM developerWorks website for WASCE specific questions and updates -

http://www-128.ibm.com/developerworks/forums/forum.jspa?forumID=541&start=0


-Donald


dcherk wrote:
Jay:


Jay D. McHugh-3 wrote:
What version of Geronimo are you using?

I am actually using WebSphere Application Server Community Edition 2.0.0.1. After not getting satisfaction from their newsgroups I did some research and
tracked to the problem to Geronimo -- thus my post here.



Jay D. McHugh-3 wrote:
Will you be able to move up to the next released version? Or is there some constraint that will force you to stay on the level that you are currently on?

We are constrained to remain on the current version.  But we will work with
our clients to deploy the application in a named context (rather than the
root context).  Hopefully that will be OK with them, so that an immediate
patch won't be necessary.  As it was my first experience with this product,
I needed to know if the problem was mine or not before I could try to work
around it.

Thanks for your help,
Dave Cherkassky


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to