Skip to main content



      Home
Home » Language IDEs » ServerTools (WTP) » Flexible Java Project vs. Dynamic Web Project
Flexible Java Project vs. Dynamic Web Project [message #135520] Mon, 29 August 2005 15:41 Go to next message
Eclipse UserFriend
I recently upgraded from Eclipse 3.1M4 (with WTP pre 0.7) to Eclipse 3.1
w/ WTP 0.7. I had implemented a set of plugins that relied on the
pre-WTP0.7 way of creating J2EE web projects and adding web modules (i.e.
create a flexible Java project and add one or more J2EE modules). Now that
I have upgraded, I see that "Flexible Java Project" and "J2EE Module" have
been replaced by "Dynamic Web Project". Had I not already build
functionality around the old way, I would've thought this change was good
because it consolidates the actions the user must go through to create a
J2EE web project and thus simplifies things. However, since I am now
temporarily broken, and since I had to get up to speed on the new WTP EMF
Module Model, I have to wonder what the reason for the change was. With
"Dynamic Web Project" there does not seem to be a way to have multiple web
modules within 1 web project. However, the WTP EMF Module Model implies
that multiple web modules within the same project should be possible (i.e.
the old Flexible Java Project way).

Why was the "Flexible Java Project" and "J2EE Web Module" method scrapped
at the last minute for the "Dynamic Web Project" way?

Is it still possible to have multiple J2EE modules defined within the same
"Dynamic Web Project"?

Thanks,
Don
Re: Flexible Java Project vs. Dynamic Web Project [message #135584 is a reply to message #135520] Mon, 29 August 2005 19:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: laurentd75___no.sp_am.yahoo.fr

"Don Sedota" wrote:

> I recently upgraded from Eclipse 3.1M4 (with WTP pre 0.7) to Eclipse 3.1
> w/ WTP 0.7.
> <CUT>
> With "Dynamic Web Project" there does not seem to be a way to have
multiple web
> modules within 1 web project. However, the WTP EMF Module Model implies
> that multiple web modules within the same project should be possible (i.e.
> the old Flexible Java Project way).
> Why was the "Flexible Java Project" and "J2EE Web Module" method scrapped
> at the last minute for the "Dynamic Web Project" way?
> Is it still possible to have multiple J2EE modules defined within the same
> "Dynamic Web Project"?

Hi Don,
Between WTP 1.0 M4 and M5, the flexible project handling was slightly
updated to allow either one module per project (the old pre-M4 way), or
multiple modules per project (the M4 way).
As from M5 and later releases (including WTP 0.7), there is a new global
preference setting that you can adjust to switch between these two policies.

So, in order to have your WTP0.7 install behave like M4 did for flexible
projects:

- Select Window > Preferences
- Go to the "J2EE modules" heading
- check the "Allow Multiple modules per project" box and click OK.

Hope this helps,

Laurent
Re: Flexible Java Project vs. Dynamic Web Project [message #135675 is a reply to message #135584] Tue, 30 August 2005 10:19 Go to previous messageGo to next message
Eclipse UserFriend
Thanks for the tip Laurent. That makes more sense. However, I'm still
having issues after setting the preference to allow multiple modules per
project. Now, when I create a new project (named "proj2"), I get an error
after the project builder runs that says;


Errors running builder "Component Structural Dependency Resolver" on
project proj2. Resource /proj2/.deployables does not exist.


Any idea why I'm getting this error? I also do not see a way to add an
additional web module to the project after it has been created. Maybe this
has something to do with the error mentioned above?

Thanks,
Don
Re: Flexible Java Project vs. Dynamic Web Project [message #135702 is a reply to message #135675] Tue, 30 August 2005 13:40 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: Laurentd75_nosp_am.yahoo.fr

Don Sedota wrote:

> I'm still having issues after setting the preference to allow multiple
> modules per project. Now, when I create a new project (named "proj2"),
> I get an error after the project builder runs that says;
> Errors running builder "Component Structural Dependency Resolver" on
> project proj2. Resource /proj2/.deployables does not exist.

Hi Don,

To be honest I've never really used WTP with the "multiple modules per
project" setting, for a number of reasons.

So, I gave it a try to assess your problems, and stumbled on the same
error as you while using the Dynamic Web Project wizard to create both a
new flexible project (WebProj1) and a new Web module (WebProj1_Mod1) at
the same time -- the error I get is similar to yours as you can see below:

[[Errors during build.]]
[[Errors running builder "Component Structural Dependency Resolver" on
project WebProj1. Resource /WebProj1/.deployables does not exist.]]

I first thought WTP was somehow getting mixed up between the single and
multiple module per project structures... Because in M4, it would have
created and looked for ".deployables" in the root of the *module* folder
(ie /WebProj1/WebProj1_Mod1/.deployables).

But after a little investigation, I discovered that WTP 0.7 had created a
/WebProj1/.deployables/WebProj1_Mod1 hierarchy... So it appears that:
- WTP 0.7 still uses a single .deployables folder at the root of the
project folder, regardless of the single/multiple module nature of the
project.
- the error that we get when creating both the project and the 1st Web
module is probably quite innocuous, because WTP seems to "fall back on its
feet" and correct the problem, creating the ".deployables" tree.

STILL, I THINK THIS BEHAVIOUR AND "ERROR" MSG SHOULD BE REPORTED AS A BUG
for assessment by the WTP team. (go to https://bugs.eclipse.org)



> I also do not see a way to add an
> additional web module to the project after it has been created. Maybe this
> has something to do with the error mentioned above?

To add an additionalm Web module to your existing project, just select the
project and select the "New > Dynamic Web project Wizard".

In the wizad, you just have to enter a name for your 2nd web module (I
typed "WebProj1_Mod2"), and select your project from the drop down list
just below (I selected "WebProj1"). Then, click finish after having set
any advanced options you may need (i.e.: Servlet API level, and Context
Root).


It did work smoothly for me, and didn't raise any errors this time round.
And it automatically created a new "WebProj1_Mod2" folder under
"WebProj1/.deployables", where it copied all files related to the 2nd web
module.


I haven't been any further with this, so I don't know whether you can
actually successfully deploy the 2 modules on a Tomcat server and run them
OK, so please keep us posted of any other hurdles you may encounter along
the way!

Cheers Don,

Laurent
Re: Flexible Java Project vs. Dynamic Web Project [message #135753 is a reply to message #135702] Tue, 30 August 2005 18:04 Go to previous messageGo to next message
Eclipse UserFriend
Thanks Laurent. So it does look like the .deployables directory is still
created on my end as well even though I get the error dialog. I will go
ahead and report it as a bug.


It seems a bit non-intuitive to have to go through the Dynamic Web Project
wizard again just to add an additional web module to the project. Maybe
I'll report it as an enhancement request??

Thanks for your help.

Don
Re: Flexible Java Project vs. Dynamic Web Project [message #135806 is a reply to message #135753] Tue, 30 August 2005 18:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: laurentd75___no.sp_am.yahoo.fr

> It seems a bit non-intuitive to have to go through the Dynamic Web Project
> wizard again just to add an additional web module to the project. Maybe
> I'll report it as an enhancement request??

I can see your point Don, it would be more logical in this case if it was
named "New Dynamic Web Module"... But this is a tricky point, since if you
use the "one project = one module" setting, then a Dynamic Web module is
really a Dynamic Web project... In any case, it doesn't hurt I think to
bring this seeming inconsistency to attention by filling in an enhancement
request.

I'm always glad to help others with the little experience I acquired of WTP
over time, so please post again if you have any other worries with this or
other stuff.

While we're at it, if oyu ever need to set up a Web project that depends on
a separate, "utility" Java project, I'd recommend you upgrade your WTP 0.7
to maintenance build M20050815 or later: I recently discovered that the "JAR
dependencies" setting in the Project properties dialogue was broken in WTP
0.7, but was fixed in M20050815... Looks like there are a couple of bugs
left in WTP 0.7, and we could do with an interim release before WTP 1.0 in
December...

Regards,

Laurent
Re: Flexible Java Project vs. Dynamic Web Project [message #135867 is a reply to message #135806] Wed, 31 August 2005 09:50 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ns_dkerber.ns_WarrenRogersAssociates.com

In article <df2o26$75i$1@news.eclipse.org>, laurentd75
___no.sp_am@yahoo.fr says...

....

> While we're at it, if oyu ever need to set up a Web project that depends on
> a separate, "utility" Java project, I'd recommend you upgrade your WTP 0.7
> to maintenance build M20050815 or later: I recently discovered that the "JAR
> dependencies" setting in the Project properties dialogue was broken in WTP
> 0.7, but was fixed in M20050815... Looks like there are a couple of bugs
> left in WTP 0.7, and we could do with an interim release before WTP 1.0 in
> December...


I believe I have run into this project dependency issue. How do I tell
which exact build of WTP I have? I looked in the eclipse Help | About,
and found the list of plugins, including WTP, but couldn't find anything
about which exact build I have of WTP.

Thanks!

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
Re: Flexible Java Project vs. Dynamic Web Project [message #135880 is a reply to message #135867] Wed, 31 August 2005 10:26 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: Laurentd75_nosp_am.yahoo.fr

David Kerber wrote:

> How do I tell which exact build of WTP I have? I looked in the eclipse
> Help | About, and found the list of plugins, including WTP, but couldn't
> find anything about which exact build I have of WTP.

Hi David,

You had the right idea to use Help | About, here's what to do next to
look for the WTP build version:

In the About dialogue, click on the "Features Details" button. The "About
Eclipse SDK Features" window opens, with a datagrid listing all features.

Scrolling the list down while looking at the "Feature Name" column, you
will recognize a number of features pertaining to WTP (such as "J2EE
Standard Tools" or "Web Standard Tools"). Looking at the "Version" column
will only tell you the "release level" of WTP you have (for WTP 0.7, the
version string is "0.7.0").

To identify the actual build you are using, just click on one of the WTP
features in the grid (e.g. click on "Web Standard Tools"): additional info
about the selected feature will be displayed just below the datagrid:
- the feature name:
- the version number
- AND the BUILD ID

On my install of WTP 0.7 M20050819, here's what details I get when I click
on "Web Standard Tools":

- Web Standard Tools
- Version: 0.7.0
- Build id: 200508191754

Regards,
Laurent
Re: Flexible Java Project vs. Dynamic Web Project [message #135890 is a reply to message #135880] Wed, 31 August 2005 10:40 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ns_dkerber.ns_WarrenRogersAssociates.com

In article <6787a0f24a792b19919861a3a344d824$1@www.eclipse.org>,
Laurentd75_nosp_am@yahoo.fr says...
> David Kerber wrote:
>
> > How do I tell which exact build of WTP I have? I looked in the eclipse
> > Help | About, and found the list of plugins, including WTP, but couldn't
> > find anything about which exact build I have of WTP.
>
> Hi David,
>
> You had the right idea to use Help | About, here's what to do next to
> look for the WTP build version:
>
> In the About dialogue, click on the "Features Details" button. The "About
> Eclipse SDK Features" window opens, with a datagrid listing all features.
>
> Scrolling the list down while looking at the "Feature Name" column, you
> will recognize a number of features pertaining to WTP (such as "J2EE
> Standard Tools" or "Web Standard Tools"). Looking at the "Version" column
> will only tell you the "release level" of WTP you have (for WTP 0.7, the
> version string is "0.7.0").

Yep, I saw that.


> To identify the actual build you are using, just click on one of the WTP
> features in the grid (e.g. click on "Web Standard Tools"): additional info
> about the selected feature will be displayed just below the datagrid:
> - the feature name:
> - the version number
> - AND the BUILD ID

I stopped one click too early! ;-) thanks for the detailed description!

....

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
Re: Flexible Java Project vs. Dynamic Web Project [message #136041 is a reply to message #135753] Wed, 31 August 2005 17:17 Go to previous message
Eclipse UserFriend
Just a follow up, there is already a bug reported in the bugzilla database
about the "Component Structural Dependency Resolver" problem - Bug 105462.

Don
Previous Topic:FTP? Is there anything better?
Next Topic:How do I force a refresh of ALL the contents of a web app
Goto Forum:
  


Current Time: Wed Sep 17 18:02:02 EDT 2025

Powered by FUDForum. Page generated in 0.03930 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top