Sorry to start this again, I've been away.

> 1. to showcase Jboss (yes, they could run on other servers, 
> but focus on JB as the 1st server) 
> 2. provide a set of components that could be used as-is or 
> customized for your application 
> 3. provide some example Uis either using a rich or thin 
> client that utilize these server-side component 
> 4. provide a good jumpstart for new applications with a 
> starter build system (combine ant, xdoclet, junit, etc. etc.) 
> , several prewritten applications that use the apis as 
> examples or skeletons, etc. 

If the purpose of this is to showcase JBoss then this would
get my vote.  If it is to create a new library then it wouldn't
(for reasons mentioned earlier).

> When I contemplated embarking on a simliar OSS project that 
> would work on the top 5 app servers, I got some interesting 
> comments from Rickard Öberg, which I neglected to pursue with 
> further discussion at the time (shame on me):
> 
> "Let's say I wanted to impose access checks on modifying a 
> user, or if I 
> wanted to add custom fields to an account, how would I do 
> that with your 
> solution? Do you have any way to handle extensibility and 
> integration? 
> How about getting user info from various backends, such as 
> RDBMS or LDAP 
> or XML or..?
> 
> IMHO there are vital points missing in todays toolkit in 
> order to allow 
> wide reuse of components such as those you outline. These 
> holes will be 
> filled, but IMHO they're not right now."

I think it would be a very good idea to show off the capabilities
of JBoss, after all the easiest way to convince someone to use it
is via demonstration.  We should, however, use some of the projects
which are already out there as a basis.  If they do not have what
we require then we should persuade them to change/add functionality
from the inside (as members) or outside (as users).

We would then be in a position to say 'yes you can do this with
another server but look what else you can do with JBoss!'

> So, I would think the idea would be to ensure its OSS so we 
> can make changes to the code, encourage it for new projects 
> where you may be able to have some flexibility in your 
> implementation if something is currently missing from a 
> component's API, and not get too fancy with things like 
> XML->code generators and other things since there are 
> projects out there that provide these solutions already (see 
> previous messages in this thread). KISS.
> 
> James

A second for KISS.  Please do not reinvent the wheel!

        Kev

Kevin Conner
Orchard Information Systems Limited
Newcastle Technopole, Kings Manor
Newcastle Upon Tyne, NE1 6PA. United Kingdom
Registered in England, Number 1900078
Tel: +44 (0) 191-2032536  Fax: +44 (0) 191 2302515


-------------------------------------------------------
This sf.net email is sponsored by: DEDICATED SERVERS only $89!
Linux or FreeBSD, FREE setup, FAST network. Get your own server
today at http://www.ServePath.com/indexfm.htm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to