[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9013) Cannot deploy Seam Portlet Example to JBoss EPP 4.3

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Fri May 27 12:17:01 EDT 2011


    [ https://issues.jboss.org/browse/JBIDE-9013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605006#comment-12605006 ] 

Snjezana Peco commented on JBIDE-9013:
--------------------------------------

The Seam Portlet Example had the following build path:

...
	<classpathentry kind="src" output="WebContent/WEB-INF/dev" path="src/action"/>
	<classpathentry kind="src" path="src/model"/>
	...
	<classpathentry kind="output" path="build/classes"/>
...

and the following component.xml (that was invalid)

...
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/action"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/model"/>
...        

Previous versions of WTP were deploying both of the source folders to WEB-INF/classes and there was no error.

WTP >3.2.4 deploys the "/src/action" source to both WEB-INF/dev (because of the declaration in .classpath) and "/WEB-INF/classes" (due to the declaration in component.xml).

I have changed component.xml to:

...
<wb-resource deploy-path="/WEB-INF/dev" source-path="/src/action"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/model"/>
...        

which is a correct mapping and all the versions of WTP deploy "/src/action" to "/WEB-INF/dev" only no matter if they use .classpath or component.xml.

> Cannot deploy Seam Portlet Example to JBoss EPP 4.3
> ---------------------------------------------------
>
>                 Key: JBIDE-9013
>                 URL: https://issues.jboss.org/browse/JBIDE-9013
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Portal/GateIn
>            Reporter: Pavol Srna
>            Assignee: Snjezana Peco
>             Fix For: 3.2.1.CR1, 3.2.2, 3.3.0.M2
>
>         Attachments: server.log
>
>
> See log attached.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list