[JBoss JIRA] (JBIDE-14782) Add ShrinkWrap Archive file location validation
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14782?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-14782:
----------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.1.x)
(was: 4.2.x)
> Add ShrinkWrap Archive file location validation
> -----------------------------------------------
>
> Key: JBIDE-14782
> URL: https://issues.jboss.org/browse/JBIDE-14782
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> *Given*
> A Deployment method
> *When*
> {code}
> war.addAsManifestResource(X, "beans.xml")
> ear.addAsManifestResource(X, "beans.xml")
> war.addAsManifestResource(X, "persistence.xml")
> {code}
> *Then*
> Warn that known EE descriptor files are in the wrong location
> Some mapping on top of my head:
> WebArchive
> {code}
> web.xml -> /WEB-INF/
> web-fragment.xml -> Not supported ?
> beans.xml -> /WEB-INF/
> persistence.xml -> /WEB-INF/classes/META-INF/
> ejb-jar.xml -> /WEB-INF/classes/META-INF/
> {code}
> JavaArchive
> {code}
> web.xml -> Not supported
> web-fragment.xml -> /META-INF/
> beans.xml -> /META-INF/
> persistence.xml -> /META-INF/
> ejb-jar.xml -> /META-INF/
> {code}
> EnterpriseArchive
> {code}
> beans.xml -> Not supported
> persistence.xml -> Not supported
> ejb-jar.xml -> Not supported
> application.xml -> /META-INF/
> {code}
> One common mistake is using addAsManifestResource on WebArchives. A quickfix / suggestion would be to use addAsWebInfResource for the files located in /WEB-INF/
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3199:
------------------------------------
Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA
(I used the embedded EAP in JBDS 8.0 GA)
> Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3199
> URL: https://issues.jboss.org/browse/JBDS-3199
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
>
> These "kitchensink" strings are retained:
> grep -ir kitchen *
> main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS"
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true"
> test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS"
> test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3199:
------------------------------------
Project based on the org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final Maven archetype
> Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3199
> URL: https://issues.jboss.org/browse/JBDS-3199
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
>
> These "kitchensink" strings are retained:
> grep -ir kitchen *
> main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS"
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true"
> test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS"
> test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months
[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16695:
----------------------------------
Fix Version/s: 4.2.1.Final
> Add marker/quick fix if test contains non static deployment method
> ------------------------------------------------------------------
>
> Key: JBIDE-16695
> URL: https://issues.jboss.org/browse/JBIDE-16695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive:
> {code}
> @Deployment
> public static WebArchive createDeployment() {
> ...code to create deployment here...
> }
> {code}
> As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 11 months