[ErikEngerd]

Hi,

I have created a web project with one jsp init (the standard one that is generated), and have modified it to include a single statement
<% out.println(“blabla”); %>.

Now when I modify the text and save the jsp file, and subsequently refresh the web page in my browser, I do not see any change. Therefore, it appears that sync-on-demand is not working. I do see eclipse validation the deployment descriptor and recompiling the jsp.

Info:
* Jboss with tomcat: 3.2.1 and 4.1.24 resp.
* Eclipse: 2.1.1
* MyEclipse: 2.5.1

I am using exploded deployment of course.

What am I doing wrong?

Cheers
Erik

[support-michael]

Can you inspect the .project file of the problematic project for the presence of the following build command:

<buildCommand>
<name>com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name>
<arguments>
</arguments>
</buildCommand>

This builderCommand is responsible for synchronizing deployments.

Michael
MyEclipse Support

[ErikEngerd]

Hi,

The builder command you specified was not present in the .project file. After adding it however, it still does not work. Now, I cannot even deploy the application. Also, it is strange that it uses the name ‘webmail.jar’ for deployment when it used to use ‘webmail.war’.

Also, I get errors from JBoss telling me

23:45:28,909 INFO [Engine] StandardHost[localhost]: MAPPING configuration error for request URI /webmail
23:45:37,020 INFO [Engine] StandardHost[localhost]: MAPPING configuration error for request URI /webmail/index.jsp

Cheers
Erik

[ErikEngerd]

Hi,

I also noticed that the web.xml and the index.jsp files are not part of the Webmail.jar file in the deployment directory. Strangely enough after undoing the change to the .project file (after shutting down eclipse), the behavior stays the same.

Cheers
Erik

[support-michael]

Hi Erik,

I encourage you to upgrade to MyEclipse 2.6.2 (released today). Among a number of JSP fixes it contains logic to identify rare cases (such as your’s) where a deployed project lacks the deployment builder (see previous msg).

http://www.myeclipseide.com/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=5&categories=Installation+and+Updates&parent_id=4

After upgrading try:
1) undeploying the project
2) verify that all classfiles copied to the JBoss deploy location have been removed, if residual files exist manually remove them
3) redeploy and verify correct deployment

Please let us know how this works out.

Michael
MyEclipse Support

[ErikEngerd]

Hi Michael,

It has not worked out, the results are exactly the same. I think I will send a zip file of the project to you and try to create a new web project from scratch. It would be good if you can reproduce the problem and find a way to solve it. I am just imagining a case with a non-trivial project where the same thing happens.

Cheers
Erik

[support-michael]

Erik,

Please send me a copy of your project to [email protected]. Just mark it to my attention. Also have you upgraded to MyEclipse 2.6.2 that was released yesterday (Wed)?

Michael
MyEclipse Support

[ErikEngerd]

Hi Michael,

I have already mailed you the sources. In the meanwhile I have also recreated the project and now it works. When inspecting the differences, I see that the webrootdir in the .mymetadata file is set to “etc/servlet” in the correct version and to “/etc/servlet” in the not-working version.

This setting cannot be changed from the menu (project properties). By editing the file in the correct version and modifying “etc/servlet” to “/etc/servlet”, my project stops working as before. Strangely enough though, when I change it back again, the project still does not work.

Cheers
Erik

[ErikEngerd]

Even more information….
* When I delete the project (excluding contents)
* Reimport the project
* Use project/properties to modify the web root and web context
root.

Then the problem can be solved. I have no idea how my
.mymetadata file became corrupt in the first place.

Cheers
Erik

[support-michael]

I was just looking over your project and noticed the same situation as you identify with the missing ‘/’ on the web-root directory path. I haven’t seen this before.

When you reverted your “good” project back with a ‘/’ web-root path did you restart MyEclipse? This is necessary since it is cached internally by the MyEclipse J2EE project model.

Michael
MyEclipse Support

[support-michael]

As I indicated we have never seen this case before so it is odd. Thanks for your patience and perserverance. We’ll be on the look out for repeats of this situation.

Regards,

Michael
MyEclipse Support

[Author]

Posts