Rickard and Marc, thanks for your replies. I'll add on the new questions now. :)
Rickard �berg wrote:
> >
> > 2. Free: Because of the various types of "free" licenses, we need to evaluate
> > the license of whichever product we choose to make sure that it is compatible
> > with out business model.
>
> GPL. We are applying it in a rather non-strict fashion though. Apps are
> not GPL.
>
I hate to get caught up in legaleze, but can you determine how the license is
enforced? Don't get me wrong, I am a huge proponent of open-source, but I can't make
my company give away their source code; and if a license looks remotely like somebody
could make them give it away, that is dangerous.
> > 3. Scalable: Must scale from a single process to multiple processes on a single
> > machine to multiple machines.
>
> This we don't have right now.
>
Any idea on a timeframe for that?
> > 4. Java-based: Must be able to transparently run Java code. This does not mean
> > that the app server itself is necessarily written in Java, just that it has full
> > Java integration.
>
> Check. The reliance on JMX makes it very easy to integrate with other
> Java code.
>
So is all cross-component communication handled via JMX? If yes, how does that affect
performance?
> > 6. Non-proprietary: In order to prevent us from being locked into a single
> > vendor, any app server chosen must either use non-proprietary standards or have
> > proprietary components available in such a way that they could be integrated in
> > other systems.
>
> Check. No proprietary code needed. If you do use any jBoss components
> directly they are easily portable by virtue of being JMX components.
>
That is a cool feature. Just had to throw that in. :)
> > 5. Support for component management
>
> Vague requirement. What would this translate to in terms of
> functionality?
I guess a better way to phrase this is will jBoss support JMX? Having a standard way
of managing beans, especially if it can plug in to SNMP, is a huge win on a complex
system.
And the final question. I'm looking at jBoss and Enhydra. Tell me, what do you see
as the primary things that differentiate jBoss from Enhydra and make it a safer bet
for development six months from now?
Again, thanks for you help. Getting this kind of info makes my life so much easier.
:)
tj
--
Travis Jensen <[EMAIL PROTECTED]>
"Writing with Light" http://www.digijen.com/travis/wwl
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
