The other limitation we ran into was lack
of api for ordering these extensions.
On that note, I’d like to make another
plug for convergence of the module assembly extension points/api for the
publish and archive processes in 2.0. While you may execute somewhat
different logic for archive vs publish, the programming model should feel very
familiar. Ideally, you’d be able to register your publish and archive
handlers based on facet and runtime component ids.
Behalf Of Jason A Sholl
Sent: Tuesday, May 30, 2006 9:08
discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Export J2EE
The IDataModelOperation extensions framework may be
able to help you. Using the
org.eclipse.wst.common.frameworks.OperationExtension point you can register a
custom operation(s) to execute before or after the primary operation responsible
for export. You will not, however, be able to replace the primary export
operation. The various export operations are:
are a few examples in the org.eclipse.wst.common.tests plugin on how to setup
an extended operation. Take a look at the plugin.xml for an example of
the extension point. The testcase you can execute is org.eclipse.wst.common.frameworks.datamodel.tests.extended.ExtendedOperationTests
Jason A. Sholl
919-543-0011 (t/l 441-0011)
05/29/2006 12:32 PM
"General discussion of project-wide or
architectural issues." <wtp-dev@xxxxxxxxxxx>
discussion of project-wide or architectural issues."
[wtp-dev] Export J2EE archive file
We (SAP) are adopting WTP and would like to
customize the export J2EE
archive feature, as we have our custom J2EE
archive build. Is there any
extension point or some other way to so that when
an J2EE archive file
is being exported our buld classes to be invoked.
wtp-dev mailing list
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.