[Smitht19]

I upgraded from MyEclipse 9.1 to 10. I am My project was running fine with JBOSS 5.1. Now when I try to run in MyEclipse 10 I get this errror – WARNING [config] Unable to process deployment descriptor for context and the application does not deploy.

Please advise

[cconway]

Hi Smitht19,

Sorry to hear you are running into this issue. Could you please answer the below queries to help me understand your environment and profile.

1. Open MyEclipse IDE. From menu options click on Help > About MyEclipse and copy and paste buildId and versionID here

2. From menu options click on MyEclipse > Installation Summary > Installation Details and copy and paste the same here

[Smitht19]

1. Open MyEclipse IDE. From menu options click on Help > About MyEclipse and copy and paste buildId and versionID here

Version: 10.0.0
Build ID: 10.0.0 Build 7 (111109_1440)

2. From menu options click on MyEclipse > Installation Summary > Installation Details and copy and paste the same here

*** Date:
Thursday, April 5, 2012 4:04:50 PM EDT

*** System properties:
OS=WindowsXP
OS version=5.1.0
OS arch=x86
Profile arch=x86
Window system=win32
Java version=1.6.0_13
Workspace=file:/C:/Documents and Settings/smitht19/Desktop/IBS-10.1/
VM Args=-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-Djava.class.path=C:\PROGRA~1\Genuitec\MYECLI~1\../../../Java/Genuitec/Common/plugins/OR02A7~1.JAR

*** Subscription information
Product Id: E3MS (MyEclipse for Spring Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20120517
Number of users: 26

*** Eclipse details:
MyEclipse for Spring

Version: 10.0.0

Build ID: 10.0.0 Build 7 (111109_1440)

Blueprint: MyEclipse for Spring 10

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse for Spring 10 – 1\myeclipseforspring.exe
-name
Myeclipseforspring
–launcher.library
C:\Program Files\Genuitec\MyEclipse for Spring 10 – 1\../../../Java/Genuitec/Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_4.2.0.v201201111650\eclipse_4201.dll
-startup
C:\Program Files\Genuitec\MyEclipse for Spring 10 – 1\../../../Java/Genuitec/Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-install
C:\Program Files\Genuitec\MyEclipse for Spring 10 – 1
-configuration
C:\Program Files\Genuitec\MyEclipse for Spring 10 – 1\configuration
-vm
C:\Java\Genuitec\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll

Attachments:

You must be logged in to view attached files.

[cconway]

Thanks for those details.

When you say the project does not deploy, is there an error message, or is there only the warning you posted? From what I’ve seen that warning doesn’t necessarily cause the project to not deploy.

Here is a post on the jboss forums that may be helpful:
https://community.jboss.org/message/631387#631387

[Smitht19]

WARNING [javax.enterprise.resource.webcontainer.jsf.config] (main) Unable to process deployment descriptor for context ‘/IBS’

this is the warning

I now get a 404 error when I go to
http://localhost:8080/IBS/

used to work find in version 9.01

[Smitht19]

So in version 9.01
has a WebRoot in side of there we had a WEB-INF with the web.xml

In 10.1

We have src/main/webapp/WEB-INF

than the web.xml

After the 10.1 conversion I have both set up I just described and if move my web.xml the warning message goes away and I get a new error

HTTP Status 404 – /IBS/jsp/login/loginpage.jsp

there is some going on with the new layout ?????

[Smitht19]

I am not sure if I am on to some there here between 9 and 10

Attachments:

You must be logged in to view attached files.

[cconway]

Yes, it looks like you are on to something.

src/main/webapp is the path used by a project with Maven enabled. The [root]\WebApp path is typically in a project that doesn’t use Maven.

Were you using Maven before the upgrade? Did someone enable Maven on the project?

Take a look at the project properties dialog and select MyEclipse > Web. Which folder is shown as the web-root folder? Hopefully that property will help you clean it up.

[Smitht19]

Here is a Maven Web Project MyEclipse 9.1. I have included a screen shot of the project file layout. Unless I did some thing wrong MyEclipse 9.1 does not create
src/main/webapp with Maven enabled. Myeclipse 9.1 creates [root]\WebApp path

The steps to get this result

select new webproject check the box to add maven support than finish

I guess my big issue is we have 6 new projects some that started in 8.6 and converted to 9.1 and some that started in 9.1 all with this layout and now we can’t use 10 unless we want to make alot of changes test and redeploy. I am trying to set things up here so we don’t need to keep several versions of MyEclipse around. It would be nice to be able to open a project from a old version in a newer version and not have the layout change. But I know it is not a perfect world.

I am not sure I believe that Tomcat is J2EE compliant. It looks like Tomcat lets you get away with this directory layout where Jboss 5.1 does not.

Attachments:

You must be logged in to view attached files.

[cconway]

I’ve put in a question to the MyEclipse Pro team about this. From 9 to 10 there was a major maven update. Hopefully they will have some input to help you through the problems.

[Brian Fernandes]

Smitht,

Let me clarify a few issues up front. In MyEclipse 10, we significantly improved our support for Maven enterprise projects, as a result Maven support has actually been enhanced to large extent.

With MyEclipse 10, when you create a Maven Web / EJB or EAR project, you get the opportunity to choose the structure of the project. You can either go with the traditional MyEclipse project layout or the Standard Maven project layout (src/main/java, src/main/webapp), etc The former layout is compatible with MyEclipse 10.x and below, the newer “Standard Maven” layout is not; however, this is the default for MyEclipse 10. We’ll make it more clear in the next release that the standard layout is not compatible with earlier versions of MyEclipse, sorry.

When projects created in older versions of MyEclipse are imported into newer versions, we do not change the project structure at all. My suggestion would be to use the MyEclipse Maven structure if you wish to shift your project between several MyEclipse versions < 10, or use the Standard Maven structure if your entire team is only using MyEclipse 10 and above.

Now, as far as your current problems are concerned – first you should decide on which project structure you want to use (assuming you are creating a new project). Could you please go to the actual deployment area (it’s a context menu action on your deployment in the Server view) and observe which files from your project did not get transferred to the deployment area? It would appear that some files are missing causing the application to fail. Could you also go to the project properties > MyEclipse > Deployment Assembly and check if Deployment Assembly is enabled for the project(s) in question?

A related point is that the layout for Web projects (when deployed) is fixed and is the same for both Tomcat and JBoss 5. In MyEclipse 10, no matter what your layout within the workspace is, if Deployment Assembly is enabled, it will make sure your resources are deployed to the right location.

Hope this helps.

[Author]

Posts