[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2249) Deploying problem of the Seam project to the server that was created in released 2.0 GA.

[Rob Stryker (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-2249?page=comments#action_12413913 ] 
            
Rob Stryker commented on JBIDE-2249:
------------------------------------

i have finally replicated this issue. 

It turns out our permissive patch is not as permissive as it could be.  The *patch* itself is (and does not need to be changed).  My JstPublisher is still having trouble telling the difference between jst.client jars that are projects and jst.client jars that are zip files.

Specifically, the following xml in application.xml is causing the problems:

  
   <module>
	   <java>jboss-el.jar</java>
   </module>   

And other lines like that.  The workaround is to remove all NON-modules from the application.xml.  Investigating a solution. 

> Deploying problem of the Seam project to the server that was created in released 2.0 GA.
> ----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-2249
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-2249
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.1.0.GA
>            Reporter: Anton Klimkovich
>         Assigned To: Rob Stryker
>            Priority: Critical
>             Fix For: 2.1.0.GA
>
>
> EXECUTE: Create Seam 2.0.1 EAR project in released 2.0 GA ()
> EXECUTE: Open 2.10 GA 
> EXECUTE: Import created Seam web project as existing project to workspace
> ASSERT:    Imported project will be marked with exception in application.xml 
> EXECUTE: Correct application.xml
> EXECUTE: On JBoss Server View select "Add and remove projects" and add imported Seam project to the server
> EXECUTE: Click Publish or Clean
> FAILURE:    java.lang.NullPointerException
> 	at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.packModuleIntoJar(JstPublisher.java:261)
> 	at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.fullPublish(JstPublisher.java:134)
> 	at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:110)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:132)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:835)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669)
> 	at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
> 	at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
> 	at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira