Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] server architecture discussion

Hi Ted,
 
Thanks for hosting this event and I will be there.   I would like to bring up a question/issue now that I hope can be responded to either on the call or here in the mailing list if possible.  
 
The JSF Tools project has a concept we call JSF Libraries.   For now, this is really just a named collection of jars that a user can add or remove from a JSF faceted project.   When we orignally conceived the idea, pre-R0.7, we intended them to become classpath containers in the project for build time and, if the library was specified to be deployed, we would use the extension that had existed at the time to copy the jars.   Unfortunately that hook dissappeared and so for M1 of the JSF tools, we were forced to copy the jars to WEB-INF/lib in the project at facet installation time.
 
With the "External JARs not copied to correct module folder in deployable" (https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783) we had hoped that we would be getting that hook back.   Instead, external jars can be made "J2EE Module Dependencies" which puts the jar on the build time classpath and if checked, deployed as well.   However this feature doesn't yet deal with CP containers.    We have entered an enhancement request for this, "To support classpath containers in J2EE Module dependency" (https://bugs.eclipse.org/bugs/show_bug.cgi?id=128851) .   We were asked to propose a patch for this.
 
However, I was hoping to get clarity on whether this feature was intended to support folks like ourselves who want to participate in deployment but may not be ServerRuntime specific.   We see publishTasks ext-pt as being almost what we want, except that it requires a specific (or list of) ServerRuntime typeid which doesn't apply for us necessarily.   
 
So before we start proposing a patch to support CP containers as J2EE module dependencies so that we can get the deploy-time file copying, would proposing to create a extension point that is server runtime agnostic be better?    Would changing publishTasks to accept "*" in typeIds and always be called for any server work?   Are there others out there who are looking for something like this?
 
Best regards,
Gerry Kessler
JSF Tools Team
-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]On Behalf Of Ted Bashor
Sent: Thursday, February 23, 2006 6:36 PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] server architecture discussion

Would like to invite interested parties to participate in a WTP server tools architecture call on Monday.

 

This is an opportunity to discuss any outstanding architecture issues and to design solutions -- perhaps temporarily setting aside annoying practicalities like schedule and api changes :-)

 

I’ll try to send out an agenda doc Monday morning with some topics.  The primary one for us is the facet runtime bridge.  But please feel free to send me any other items you’d like to discuss.

 

Time: Monday, 2/27  11 AM PST / 2 PM EST

Toll free:  866-214-3176

Passcode:  8870689

 

 

Thanks, Ted

 

tbashor@xxxxxxx

 

 

 

 

_______________________________________________________________________
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.

Back to the top