[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] post M8 api changes

Hi Thomas,

The getLocation() method was removed from IJ2EEModule since none of the J2EE modules in WTP have a single 'location'. Now that the .deployables directory is gone, from a server's view the modules really consist of a set of directories, e.g. the web content and the compiled Java output in different locations. IJ2EEModule is really the interface for a flexible J2EE project, and it's the mechanism that allows the servers in WTP to deploy this type of module. Given that the flexible project will never have a single output location (i.e. it could never be using in WTP and would always return null), I'm not in favor of leaving this method on the interface. The long term goal is actually to get rid of these interfaces completely and allow servers to adapt directly to the flexible project model.

Note that if you want to create a new type of J2EE project in a downstream product, you can either extend IJ2EEModule or allow your modules to be adapted to a different interface, thus providing additional support or methods above what is provided in the standard flexible projects.

Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)

"Thomas Yip" <tyip@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

10/17/2005 02:29 PM

Please respond to
"General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
RE: [wtp-dev] post M8 api changes

Regarding 2/, what if the module isnât a flex project.
I think the IModule and IJ2EEModule provide an abstraction so that user can plug their own implementation. Most code that deals with IModule doesnât necessary care about the actual type of IModule. I think it is a good idea to have getLocation() method back.

From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of John Lanuti
Monday, October 17, 2005 9:23 AM
General discussion of project-wide or architectural issues.
Re: [wtp-dev] post M8 api changes


Hey Sachin,

1. The ComponentHandle class has been deleted in M9.  It is no longer necessary since there is only one component per project.

2.  You want to call J2EEFlexProjDeployable.getURI(IModule)

3.  The project facet support is sort of a next step in evolution of project natures.  See the following link:


Substitute anytime you see the word "feature" and replace with "Facet".

Hope that helps,

John Lanuti
Software Engineer, IBM Rational
t/l 441-7861

"I know this lady way down in my country.
She is so pretty that my eyes throw disguises at me.
Now we will sit and we'll wonder about our future,
But now I'm thinking that today sounds fine to me."  - Of A Revolution

Sachin Patel <sppatel2@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

10/17/2005 11:58 AM

Please respond to
"General discussion of project-wide or architectural issues."

wtp-dev <wtp-dev@xxxxxxxxxxx>
[wtp-dev] post M8 api changes



I have just moved to last fridays integration build, and due to the
.deployable design changes I've run into the following errors.  Could
someone guide me on how I need to react?

(1) Can no longer get component handle from J2EEFlexProjDeployable, even
though constructor takes in IVirtualComponent.
(2) Can't get location of IModule.  Before I loaded the IJ2EEModule
adapter and called getLocation().
(3) ServerCore.getProjectProperties is deprecated.  JavaDoc refers to
Project facet support.  What is project facet support?

Thanks in advance.


wtp-dev mailing list
wtp-dev mailing list