RE: [Webwork-devel] WW/JavaOne get together

[<fbe...@py...>]

> > I think it makes more sense technically to integrate OS and WW.
> Even if technically there is no integration to be made? Or what would
> that imply, specifically?
I have not tought about all the technical possibilities but here are some:
- Unified configuration file
- Management/Monitoring console
- Tag libraries
- I am sure there are ways to take advantage of OSCache in a nice manner in
WW beside simply just using the tags
- I am sure we can also come up with ideas related to SiteMesh
- There is probably also oportunities with OSUser
- Some things in OSCore can probably be migrated into WW and then keep very
general stuff in OSCore move other stuff out of OSCore into OSCoreEJB
- Other great ideas that would come out of community discussions

Cheers,
___________________________
François Beauregard, b.ing.
Vice-président
Recherche et développement
Pyxis Technologies
www.pyxis-tech.com

T : (450) 681-9094, poste 102
F : (450) 681-5758
fbe...@py...

-----Original Message-----
From: Rickard [mailto:ri...@mi...]
Sent: April 3, 2002 4:18 PM
To: fbe...@py...
Cc: web...@li...
Subject: Re: [Webwork-devel] WW/JavaOne get together


François Beauregard wrote:

> I think it makes more sense technically to integrate OS and WW.


Even if technically there is no integration to be made? Or what would
that imply, specifically?


> The idea is to come up with value added components that can be used in any
> J2EE environment (including JBoss).
> Mike explained in a previous post the reasoning behind the Open Symphony
> name.
> Components developed in a truly open source and community philosophy that
> work together as a Symphony.


Yes, that is very clear to me.


> Therefore, I vote to keep the already made decision of slowly integrating
WW
> into OS by first :
> - Create a section for WW on OS's site
> - Issue a press release annoucing the collaboration, the reasonning behind
> and the goals
> - Come up with ideas to enhance using OS components and WW together
(unified
> configuration file, management console, overlaps, ...). May be create a
> subproject who would be responsible for this.
> - Components should always be usable on their own but be easily integrated
> in a complete framework for J2EE. This promotes highly modularized and
> customizable components.


But this has not much to do with the decision, but rather the execution
of the decision if made in OS's favor.


> I also like Mike's idea of a showcase application using WW that runs on
> JBoss and use it a promotion for JBoss, WW and OS.
> (Please don't start a discussion on joining the three)


Hehe...


> Bottom line :
> Integrating OS and WW make sense both technically and from a promotion
point
> of view.
> Some combined promotion effort by JBoss and WW also makes sense.


Is the technical point about configuration? Or is there more to it?

/Rickard

--
Rickard Öberg