[Tony Herstell]

Build id: 8.6M1-20100525 – Exploded deployment as .ear

Tried to deploy ear as exploded and got a number of errors.

Tried to deploy as packaged and all worked fine.

Is there a known error? I think exploded tries to deploy project as the new .war format… this is BAD for us (for now)… can it have a radio button to select the old “.ear” format.

Odd that packaged works!

I have stopped Dev team moving onto 8.6M1 for now as will cripple productivity if we have to go back to ant etc.

[Tony Herstell]

java.lang.NullPointerException
at com.genuitec.eclipse.ast.deploy.core.packaging.WarPackager.�(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.WarPackager.getWarDependencyProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.getLibraryProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.getProjectDependencies(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.explodeDependentProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.PackageUtils.explodeDependentProjects(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.Ć(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.WebDeployment.doProjectTypeSpecificPostResyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.resyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ModuleDeployment.deployAsExplodedArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.resyncAll(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsExplodedArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.�(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[Tony Herstell]

java.lang.IllegalArgumentException: Invalid component handle: P/RisingStarsWeb
at org.eclipse.wst.common.componentcore.ArtifactEdit.<init>(ArtifactEdit.java:379)
at org.eclipse.wst.common.componentcore.ArtifactEdit.<init>(ArtifactEdit.java:332)
at org.eclipse.wst.common.componentcore.ArtifactEdit.<init>(ArtifactEdit.java:316)
at org.eclipse.jst.jsf.facesconfig.util.FacesConfigArtifactEdit.<init>(FacesConfigArtifactEdit.java:47)
at org.eclipse.jst.jsf.facesconfig.util.FacesConfigArtifactEdit.getFacesConfigArtifactEditForRead(FacesConfigArtifactEdit.java:59)
at org.eclipse.jst.jsf.validation.internal.appconfig.AppConfigValidator.validateFile(AppConfigValidator.java:188)
at org.eclipse.jst.jsf.validation.internal.appconfig.AppConfigValidator.validate(AppConfigValidator.java:77)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1132)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:732)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:695)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:836)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:699)
at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:300)
at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:108)
at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:60)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:70)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:106)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:90)
at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:218)
at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:177)
at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:125)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[support-shalini]

balanceofpower,
Can you give us some more information regarding the issue?
1. What is the server you are deploying on?
2. Is the EAR created in MyEclipse?
3. If you create a new EAR and deploy it, do you still get the same issue?

[Tony Herstell]

Deploying onto JBoss 5.x

> 2. Is the EAR created in MyEclipse?
Not sure what you mean…
The project is an EAR project as far as MyEclipse is concerned.

No works fine if you do a non exploded deployment.

I will do whatever you need to assist (temporary access to SVN etc.)

[Tony Herstell]

Any more news on this problem?

[support-shalini]

balanceofpower,
Sorry for the delayed response.

> 2. Is the EAR created in MyEclipse?
Not sure what you mean…
The project is an EAR project as far as MyEclipse is concerned.

Can you clarify if the project was originally created in MyEclipse or if the project is imported from another IDE.
For a quick test, If you create a new EAR in MyEclipse, with a new Web module and deploy it on Jboss5 in exploded mode,
do still get the same issue?

[Tony Herstell]

Yes, the ear was originally create in MyEclipse.
Willing to let you have temporary acceess to SVN to see for yourself.
Download, exploded deploy; bang!

[Brian Fernandes]

balanceofpower,

First off, thank you for trying 8.6M1. What was the last version of MyEclipse in which this application was successfully deployed?

As far as the EAR is concerned, how many modules does it have? Is it only composed of multiple web projects (how many) or does it have EJB projects as well? Did you try your old workspace in 8.6M1 or did you import the projects into a new workspace? We did not make any changes to deployment formats – there is no new form of deployment.

[Tony Herstell]

Yes working fine for years; not in this release it breaks.

1 Ear, 1 Jar and 1 War.

It’s not complicated in any way.

Imported from SVN (main project told it to find projects under the SNV head).

So what DID you break?

We update appication.xml manually as you don’t support Seam projects very well.

Again (have done this before and found the problem quickly) I offer you SVN access so you can try.

I see in builders I have the following:
Missing builder (org.jboss.tools.jst.web.kb.kbbuilder)
Missing builder (org.jboss.tools.seam.core.seambuilder)

Possibly another member of team has set something up I dont know about.

[Brian Fernandes]

Yes working fine for years; not in this release it breaks.

Good to know, but knowing exactly the last release in which it worked for you would help. So if I know it worked for you in ME 7.5, or 8, 8.5, it would help.
Looks like someone has been using your project with JBoss tools, which is why those builders are in there, but should be harmless inside MyEclipse.

Would appreciate access to your repo, you can PM me the connection details and I will take a look immediately.

[Brian Fernandes]

balanceofpower,

We investigated the files sent to us an could replicate exactly the same NPE as you described. However, it was related to a missing classpath container which may (or may not) be a problem in your workspace since you shifted workspaces.

Go to the project properties of eSafeNSoundWeb and then select Java Build Path. On the libraries tab, do you have any entries with an error marker on them? Such as “[JVM 1.6.0 (MacOS X Default)] (unbound)”? This indicates that your project was bound to a specific JRE instance which does not exist in your current workspace. To fix this, simply remove the entry (select and hit Remove) and then choose Add Library > JRE System Library and either use the default or one which you have configured in your workspace.

Let us know if this fixes the problem.

[Tony Herstell]

Sorry just got back from Oz.
That worked; thx heaps.
May want to catch error and report some meaningful error for those that follow after me…
Thx again.

[Brian Fernandes]

balanceofpower,

Glad to know that was the issue. I agree that it was a badly managed error, I have just overseen a fix where we display a more meaningful error message.

Thanks for reporting this.

[Author]

Posts