|[cross-project-issues-dev] RE: issue with ICU4J on weblogic 8|
WLS 8 is not cert’ed with ICU4J, but I’m happy to pass this by my support/CCE team to see what they know. Will report back when I hear, but don’t expect an update by this Friday’s Callisto meeting.
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Wenfeng Li
Hi, Fellow Callisto teams,
I am not sure this is a cross team issue, but would like to share it, since we are all moving to ICU4J.
After moving to ICU4J in BIRT, we have run into resource loading issue on the Weblogic 8 app server platform, other app server platform works. Searching on the ICU4J bug log, it seems others have run into similar problem. Following are the 3 bug entries for ICU in this area...
They points to resource loading issue withing ICU4J on app servers platforms, specifically weblogic 8.1..
Did any of your projects run into this issue? Is there a work around for this?
cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of Bjorn Freeman-Benson
Planning Council members, Cross project mailing list
Simultaneous Release is hard a problem. A simultaneous release is a hard
problem just within a single company where everyone reports to the same VP
Engineering. It's an even harder problem in open source where the projects are
staffed by (effectively) volunteers and from multiple competing companies. The
only way we are going to make this work is to keep all of our colleagues well
informed of our status, our progress, our problems, and any potential schedule
slips. Just posting to our own project websites or mailing lists isn't good
enough - we have to reach out to our colleagues (I'm talking about the
collective Callisto team) and actively keeping everyone informed.
_______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.