|
To elaborate more on this point... Each
runtime instance is composed of multiple runtime components. There is an
extension point that maps between runtime components and the facets that they
support. See the “supported” element of the “org.eclipse.wst.common.project.facet.core.runtimes”
extension point. Right now all of the runtimes are using the default bridge,
which creates a runtime with two runtime components, one for the jre and one
for the server. It’s possible to write a custom bridge for any given
runtime, but I don’t believe anyone has done that yet. With a custom
bridge, you can create a runtime that’s composed of any number of runtime
components. For instance, for Geronimo you could define a runtime component for
each of the containers, such as “Geronimo EJB Container” and “Geronimo
Web Container”. Then you could map the “jst.ejb” facet to the
“Geronimo EJB Container” runtime component, etc. If the user
encounters a Geronimo runtime that doesn’t have the “Geronimo EJB
Container” runtime component, he/she will not be able to target an EJB
project to that runtime. One of the reasons we are pushing for
elimination of the bridge architecture is to make these facilities easier for
the runtime provider to take advantage off. Let me know if you have further questions
on this. - Konstantin From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of >(1) After defining a
runtime, based on that runtime, what project types am I capable of creation and
what facets can be added? This mapping is supported (it’s one of the top couple reasons for
the whole facets initiative). Try targeting an EAR project or EJB project
to Tomcat during project creation. -Ted From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sachin Patel Thanks for hosting this call. Along the lines of the runtime discussion, we at a Geronimo have a use
case scenario which I think may provide a good example on future needs on
facet/runtime support in WTP. Geronimo is headed toward a model where users can actually build their
own custom server image/distribution, with the specific services they
require. So aside from the actual delivery distributions packaging all of
geronimo's services, users will be able to generate for example an image
containing only a ejb container, or web container, or even a distribution with
no j2ee at all. In addition we foresee an appcentric solution to
deployment. So given an application I want to deploy, build me the
minimum server capable of running this application. So since each
distribution could be different, how does this affect the concept of a runtime? I see the following being useful... (1) After defining a runtime, based on that runtime, what project types
am I capable of creation and what facets can be added? I don't think
there is a link between facet's and runtimes to be able to do this type of
validation yet. Taking preventive measures at project creation time would
be excellent to have to avoid users debugging deployment errors. (2) Dynamic runtime creation. I want to create a web project that
will run on Geronimo. Without any additional input generate me a runtime
that is capable of handling this. So essentially this means multiple
applications could be targeting the same server however the cp container on
each project would differ. I haven't really thought through this
scenario completely, its just an idea so far. - sachin On Feb 27, 2006, at 12:37 PM, Some talking points for the call. Apologies if I didn’t
capture some of the suggestions, I’m sure this is way more than
we’ll have time to cover today. 1) Bridge between
org.eclipse.wst.common.project.facet.core.runtime.IRuntime and
org.eclipse.wst.server.core.IRuntime * implementing a runtime requires
using two different api / extension points. * interacting with the runtime, one
has to move across the boundary between the server tools and the j2ee tools /
facets. * Poor performance. Since the bridge
does not know when the runtimes change, it is forced to do a lot of unnecessary
work to make sure it doesn't get out of sync. * Very difficult to take advantage of
some of the extensibility offered by the faceted project runtimes. For
instance, in order to have runtimes with more than two runtime components, one
has to implement a custom runtime bridge. * Unable to add "New" button
(to create a new runtime) to the facet selection panel since the project facets
framework has no idea how runtimes are created and they maybe coming from
multiple sources (multiple bridges). 1a) https://bugs.eclipse.org/bugs/show_bug.cgi?id=111545
- relationship server instance configuration to the server.core and facet
runtime representations. 2) Server Adapter API (publish) * Have found the module array
difficult to work with. Publish Tasks and Module Publishers generally
need to operate on, or within the context of, each EAR, Standalone WAR,
Standalone EJB module heirarchy. (See Bug 123676.) * Need to be able to abort the
publishing of an individual EAR, Stndalone WAR, or Stndalone EJB, while
allowing other deployable units to continue to process/publish. * User interaction during publish
process? 3) Typing and filtering of (component)
resources used during publish * Mechanism for publish tasks/publish
process delegate to facet implementation classes? 4) File delta perf/scalability From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of 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 _______________________________________________________________________Notice: This email message, together with any attachments, may containinformation of BEA Systems, Inc., its subsidiaries and affiliatedentities, that may be confidential, proprietary, copyrighted and/orlegally privileged, and is intended solely for the use of the individualor entity named in this message. If you are not the intended recipient,and have received this message in error, please immediately return thisby email and then delete it._______________________________________________________________________Notice: This email message, together with any attachments, may containinformation of BEA Systems, Inc., its subsidiaries and affiliatedentities, that may be confidential, proprietary, copyrighted and/orlegally privileged, and is intended solely for the use of the individualor entity named in this message. If you are not the intended recipient,and have received this message in error, please immediately return thisby email and then delete it.
_______________________________________________________________________ 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. _______________________________________________________________________ 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. |
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
