geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Sisson <jrsis...@gmail.com>
Subject Re: Release 1.1 - Question about Java 1.5 Warning message
Date Sat, 29 Apr 2006 00:36:52 GMT
Could you make it so it can be configured to be an error or a warning as 
I am sure there will be use cases where a configuration should not be 
started (an error produced rather than a warning) if it is known that 
the runtime environment might cause loss of data etc.

John

Paul McMahan wrote:
> On 4/27/06, Aaron Mulder <ammulder@alumni.princeton.edu> wrote:
>> FYI, if we distribute DayTrader as a plugin, we can tag it as running
>> on JDK 1.4.* only, and then you won't be able to install it into a
>> server running on 1.5.
>>
>> I think we should move the JDK 1.5 warning to a GBean we put in the
>> j2ee-corba configuration, so if that configuration is started for any
>> reason it will spew out the warning if running on JDK 1.5.
>
> Long term this sounds like the best idea to me.  If the gbean were
> implemented in a generic way it could be reused by other
> applications/components that have specific runtime reqs.  They could
> pass a list of properties (using CSVs if needed) to the gbean that get
> compared (via substring) to the JVM system properties, along with the
> warning text to emit if there's a mismatch.
>
> e.g. something like:
>
>    <gbean name="RuntimeCheck"
>                 
> class="org.apache.geronimo.system.util.RuntimeCheckGBean">
>        <attribute name="systemProperties">
>            java.runtime.version=1.3,1.4.2
>            os.arch=i386
>            os.name=Linux
>        </attribute>
>        <attribute name="warningText">
>           The runtime environment does not meet the requirements of
> this application:
>           {$systemProperties}
>          Serialization errors and JNI problems may occur.
>        </attribute>
>    </gbean>
>
> Could that be useful to an application like daytrader?  If there's
> interest in this approach (or something similar) then I am happy to
> volunteer.
>
>
>>
>> Thanks,
>>     Aaron
>>
>> On 4/27/06, Joe Bohn <joe.bohn@earthlink.net> wrote:
>> > +1 on #3.  We should not the JDK 1.5 concerns in the readme.
>> >
>> > I also like Dave Colasurdo's suggestion that we issue a warning 
>> message
>> > if we can detect that we are running on JDK 1.5 and CORBA EJBs are 
>> being
>> > used.  Not sure how feasible (or visible) it will be to add those
>> > warnings but it would be nice to have.
>> >
>> > Joe
>> >
>> > Matt Hogstrom wrote:
>> > > All,
>> > >
>> > > I wanted to clarify what our plan is for the JVM Check that is 
>> done to
>> > > verify that a user is running on Java 1.4.  If someone chooses to 
>> accept
>> > > the responsibility and use Java 1.5 it would be rather annoying 
>> to have
>> > > this message come out every time.
>> > >
>> > > I think we have three options:
>> > >
>> > > 1. Leave it as is (warning comes out all the time)
>> > > 2. Allow someone to set a property or other mechanism to tell the 
>> server
>> > > to not to issue the warning message.
>> > > 3. Take the message out because 1.1 will tolerate 1.5 and we're not
>> > > shipping DayTrader installed so the javax.xml.namespace.QName 
>> problem
>> > > won't be visible.
>> > >
>> > > Personally I prefer 3 if there are no other issues.
>> > >
>> > > Thoughts?
>> > >
>> > > Matt
>> > >
>> > >
>> >
>> > --
>> > Joe Bohn
>> > joe.bohn at earthlink.net
>> >
>> > "He is no fool who gives what he cannot keep, to gain what he cannot
>> > lose."   -- Jim Elliot
>> >
>>
>


Mime
View raw message