[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3456) application.xml is missing in Seam project when debug on server option is selected for the web application

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-3456:
--------------------------------------

I have marked this issue as UpStream because it depends on m2eclipse. See https://jira.jboss.org/jira/browse/JBIDE-3874?focusedCommentId=12472987#action_12472987

> application.xml is missing in Seam project when debug on server option is selected for the web application
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-3456
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3456
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.cr1
>         Environment: Ganyede 3.4.1 JEE Version, JDK 6, JBoss Tools Nightly 20/12/2008, m2eclipse plugin 30/11/2008
>            Reporter: Dirk Pitt
>            Assignee: Snjezana Peco
>             Fix For: LATER
>
>         Attachments: burnout.zip, burnout2.zip, burnout3.rar, configuration.txt
>
>
> My project is not generated from the seamgen or from JBoss Tools Seam Wizard. I created from Wesley Hayes maven archetype and installed necessary facets in eclipse configuration (Seam Facet and Seam Settings)..
> If I build it with maven and deploy it, everything works fine.
> But if I say in the web project in eclipse, debug on the server, I am getting the exception during deployment that application.xml is not there and it is not really there under \.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_AS_4.2.3_Server\deploy... 
> My project configuration seems to be valid one because I am getting all the content assist information for the seam and project runs correctly if it deployed externally to JBoss...
> May be JBoss Tools and m2eclipse plugin are colliding but it is very hard for me to tell that..
> I am attaching my sample project also so may be you can also reproduce it...
> May be one other tip, in maven ear plugin, I can configure the application.xml to be built in the runtime and would be copied to the target\EAR\META-INF directory during the build time (and application.xml there after the maven install). What I don't know does Seam/JBoss Tools look to the target directory to find the application.xml or it is trying to copy it from the source directories. If it tries to copy from sources directory
> ies, that is bad because as I said, this file is placed to the compile directory (target in my case / standart maven configuration). But in anycase I think it makes more sense to find this file from the compile/build directory...

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