[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [wtp-dev] EAR cannot be added to a Server
|
Chuck, Gorkem, thank for your answers.
I was caught a bit off-guard that EAR support wasn't ready in M4! In the
mean time, I think the best I can do is filing bugs (and, hopefully some
patches) along the line of EAR-support.
I have another question, EAR reference used to be represented by normal
Eclispe project reference. So, the call,
earModule.getProject().getReferencedProjects()
got me the list of projects referenced by an EAR, and I can obtain
module from the projects.
What is the new way of doing so under the new flexible project?
I tried to obtain an adapter of type IEnterpriseApplication, and call
its getModules(). However, the modules returned is IJ2EEModule[] instead
of IModule[]. And, I don't see how to traverse between the two...
Thomas
> -----Original Message-----
> From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On
> Behalf Of Gorkem Ercan
> Sent: Thursday, May 05, 2005 12:11 AM
> To: General discussion of project-wide or architectural issues.
> Subject: Re: [wtp-dev] EAR cannot be added to a Server
>
> Hi,
> To support deployments of EARs we needed changes in two components. In
> j2ee module adaptors and generic servers. Actually Brad and I made
> necessary changes before M4 but we decided to hold them back since
> there was little time to test them. If I am not mistaken Thomas needs
> the changes Brad had more than my changes since he wants to be able to
> target an ear module for publishing to a server (possibly WLS :)) and
> those changes exactly does that.
> Brad, I am ready to commit my changes, but please let me know when you
> are done so I can test.
>
> By the way, Chuck I am used to one letter misspellings of my name but
> your misspelling holds the record so far :)
>
> --
> Gorkem Ercan
>
>
>
>
> On 5/5/05, Chuck Bridgham <cbridgha@xxxxxxxxxx> wrote:
> >
> > Hi Thomas,
> >
> > As I understand it, the EAR server support was not ready in M4, so
the
> "Run
> > on.." menu was pulled.
> > Gorcam, is there a timeline on ear module support?
> >
> > Thanks - Chuck
> >
> > Rational J2EE Tooling Team Lead
> > IBM Software Lab - Research Triangle Park, NC
> > Email: cbridgha@xxxxxxxxxx
> > Phone: 919-254-1848 (T/L: 444)
> >
> >
> >
> >
> > "Thomas Yip" <tyip@xxxxxxx>
> > Sent by: wtp-dev-bounces@xxxxxxxxxxx
> >
> > 05/04/2005 08:56 PM
> >
> > Please respond to
> > "General discussion of project-wide or architectural issues."
> >
> >
> > To <wtp-dev@xxxxxxxxxxx>
> >
> > cc
> >
> > Subject [wtp-dev] EAR cannot be added to a Server
> >
> >
> >
> >
> >
> >
> > Hi all,
> >
> >
> > I am trying to port a server adapter to M4.
> >
> > EAR project can no longer being added to the server.
> >
> > Taking a brief look at the code and cvs. The change was made in Apr
27.
> >
> > Would anyone mind shinning some light on the problem?
> >
> >
> >
> >
> > Thanks in advance!
> >
> >
> >
> >
> > Thomas Yip
> >
> >
> >
> > ------------ affected file ------------
> >
> >
> > package org.eclipse.jst.j2ee.internal.deployables;
> >
> > public class EnterpriseApplicationDeployableFactory {
> >
> > // ...
> >
> > public IModule[] getModules() {
> > //turned off for M4
> > /*cacheModules();
> > ArrayList moduleList = new
> ArrayList();
> > for (Iterator iter =
> > projects.values().iterator();
> > iter.hasNext();) {
> > IModule[] element
=
> > (IModule[]) iter.next();
> > for (int j = 0; j
<
> > element.length; j++) {
> >
> > moduleList.add(element[j]);
> > }
> > }
> > IModule[] modules = new
> > IModule[moduleList.size()];
> > moduleList.toArray(modules);
> > return modules;*/
> > return null;
> >
> > }
> > }
> >
> > --------------------
> > Thomas Yip
> > Senior Software Engineer
> > BEA Systems
> > Email: tyip@xxxxxxx YIM: thomasleaf Phone: (206) 926-2906
> >
> >
> > "The complexity you remove can never fail." Burt Rutan.
> >
> >
> > Notice: This email message, together with any attachments, contains
> > information of BEA Systems, Inc. (San Jose, California, USA) 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, lease immediately return this by email and then
> delete
> > it.
> >
> >
> > _______________________________________________
> > wtp-dev mailing list
> > wtp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/wtp-dev
> >
> >
> > _______________________________________________
> > wtp-dev mailing list
> > wtp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/wtp-dev
> >
> >
> >
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev