[JBoss JIRA] (JBIDE-14786) Create SY bot test - WS Proxy SOAP
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-14786:
-----------------------------------------
Summary: Create SY bot test - WS Proxy SOAP
Key: JBIDE-14786
URL: https://issues.jboss.org/browse/JBIDE-14786
Project: Tools (JBoss Tools)
Issue Type: Task
Components: QA
Affects Versions: 4.0.0.Alpha1-SOA
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.0.0.Alpha1-SOA
The switchayrd bot bot test will model Web Service Proxy using SOAP
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14770) Missing components when JBT 4.1.Beta1 is installed via Marketplace
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14770?page=com.atlassian.jira.plugi... ]
Jiri Peterka closed JBIDE-14770.
--------------------------------
Verified, missing features added, remaining explained.
> Missing components when JBT 4.1.Beta1 is installed via Marketplace
> ------------------------------------------------------------------
>
> Key: JBIDE-14770
> URL: https://issues.jboss.org/browse/JBIDE-14770
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.1.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Beta1
>
> Attachments: jbide14770.png
>
>
> Missing components when JBT 4.1.Beta1 is installed via Marketplace, specifially:
> Some of them might be intentional:
> - Arquillian support (Experimental) 1.0.4.Beta1-v20130518-2210-B3
> - Forge Tools Extensions (Forge 2.0 Support - Experimental) 1.0.0.Beta1-v20130524-1739-B66
> - JBoss BIRT Integration 1.5.0.Beta1-v20130518-0411-B36
> - JBoss Central - UI Themes for Eclipse 1.2.0.Beta1-v20130523-1233-B39
> - JBoss GWT Integration (Experimental) 1.1.0.Final-v20130205-2223-B78
> - JBoss Maven GWT Configurator 1.5.0.Beta1-v20130523-1233-B39
> - JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7
> - JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60
> - JBoss Tools Common - Mylyn 3.5.0.Beta1-v20130525-0108-B68
> - JBoss Tools LiveReload 1.0.0.Beta1-v20130524-1307-B28
> - Maven Integration for Eclipse JDT APT 1.0.1.201209200721
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14780) Add ShrinkWrap Archive name/type validation
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14780?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-14780:
-------------------------------------
Assignee: Snjezana Peco
> Add ShrinkWrap Archive name/type validation
> -------------------------------------------
>
> Key: JBIDE-14780
> URL: https://issues.jboss.org/browse/JBIDE-14780
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> *Given*
> {code}
> ShrinkWrap.create(WebArchive.class, "test.jar")
> ShrinkWrap.create(WebArchive.class, "test.ear")
> ShrinkWrap.create(JavaArchive.class, "test.ear")
> ShrinkWrap.create(WebArchive.class, "test")
> {code}
> *When*
> User is creating a Archive
> *Then*
> The known Archive types should match given archive name extensions.
> *Expected*
> Warning; Creating an archive of type WebArchive but given name does not match to predefined name extension; .war
> *Actual*
> Nothing.. waits for Arquillian to fail.
> This is a very common and annoying user error. The Container/Server will 99% of the time rely on the deployment file extension to determine what type of archive this is. While our 'WebArchive' Archive types are only convenience views on how to add data to correct locations within the target archive and can be any type; we choose to validate this runtime in Arquillian core to warn that 'hey, this is probably not what you intended to do' to hopefully save users from a few hours pointless debugging.
> See https://github.com/arquillian/arquillian-core/blob/master/container/spi/s... for our extension type mapping.
> Our validation logic is; if extension does not match, but Archive is of Type then warn.
> That allows users to use Custom views without warning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14778) 'Generate deployment method' uses wrong location for option 'add empty beans.xml' when war type is selected
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14778?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-14778:
-------------------------------------
Assignee: Snjezana Peco
> 'Generate deployment method' uses wrong location for option 'add empty beans.xml' when war type is selected
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14778
> URL: https://issues.jboss.org/browse/JBIDE-14778
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> Given:
> Generate Deployment Method Dialog
> When:
> * Archive type: WebArchive
> * Add an empty beans.xml file: true
> Then:
> Generated ShrinkWrap deployment should have a EmptyAsset.INSTANCE to beans.xml mapping added in the correct location.
> *Expected*
> When WebArchive:
> {code}
> archive.addAsWebInfResource(EmptyAsset.INSTNACE, "beans.xml")
> {code}
> When JavaArchive:
> {code}
> archive.addAsManifestResource(EmptyAsset.INSTNACE, "beans.xml")
> {code}
> When Enterprise Archive:
> Field _Add an empty beans.xml file_ should be disabled. No CDI on EAR level in spec.
> Actual result:
> Both JavaArchive, WebArchive, EnterpriseArchive use ManifestResource location
> {code}
> .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml");
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months