[JBoss JIRA] (JBTIS-198) Split BPMN2 tests into *.reddeer and *.ui.bot.test projects
by Marek Baluch (JIRA)
[ https://issues.jboss.org/browse/JBTIS-198?page=com.atlassian.jira.plugin.... ]
Marek Baluch closed JBTIS-198.
------------------------------
> Split BPMN2 tests into *.reddeer and *.ui.bot.test projects
> -----------------------------------------------------------
>
> Key: JBTIS-198
> URL: https://issues.jboss.org/browse/JBTIS-198
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: QE
> Affects Versions: 4.1.3
> Reporter: Andrej Podhradsky
> Assignee: Marek Baluch
> Fix For: 4.1.3
>
>
> There should be the following projects
> * org.jboss.tools.bpmn2.reddeer
> * org.jboss.tools.bpmn2.ui.bot.test
> Please put into org.jboss.tools.bpmn2.reddeer only classes related to BPMN2 editor without all 3rd party libs. I think you are using them in tests so the dependent libs should be in org.jboss.tools.bpmn2.ui.bot.test.
--
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, 5 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-12860:
-------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Alexey, could you take a look at this last test case ?
It seems that my JaxrsMetamodelValidator class is not called by the underlying CommonValidator if the project in the workspace is new and when I delete the copy of App2 class. If I close the runtime workbench and start it again, it works fine. Is there anything you can find in the Common Validator
btw, the builder ordering looks good:
{code}
...
<buildCommand>
<name>org.jboss.tools.ws.jaxrs.metamodelBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.wst.validation.validationbuilder</name>
<arguments>
</arguments>
</buildCommand>
...
{code}
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-12860
> URL: https://issues.jboss.org/browse/JBIDE-12860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Alexey Kazakov
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 5 months
[JBoss JIRA] (JBIDE-15357) Unexpected state of deployed project when project is deleted
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15357?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-15357:
-----------------------------------
Assignee: Max Rydahl Andersen (was: Rob Stryker)
with a test
> Unexpected state of deployed project when project is deleted
> ------------------------------------------------------------
>
> Key: JBIDE-15357
> URL: https://issues.jboss.org/browse/JBIDE-15357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Final
> Environment: JBDS 7.0.0.GA, L64
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> When project is deployed in IDE and then removed expected behavior would expect project would be undeployed. When I've tried that everything seemed as undeployed (I mean Server view) but project is still deployed. This is not user expected behavior IMO.
--
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, 5 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-12860:
----------------------------------
Fix Version/s: (was: 4.2.0.Alpha1)
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-12860
> URL: https://issues.jboss.org/browse/JBIDE-12860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 5 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-12860:
------------------------------------
Labels: respin-a respin-b (was: respin-a)
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-12860
> URL: https://issues.jboss.org/browse/JBIDE-12860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Max Rydahl Andersen
> Labels: respin-a, respin-b
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 5 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-12860:
------------------------------------
Labels: respin-b (was: respin-a respin-b)
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-12860
> URL: https://issues.jboss.org/browse/JBIDE-12860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Max Rydahl Andersen
> Labels: respin-b
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 5 months
[JBoss JIRA] (JBIDE-15502) Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15502?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15502:
-------------------------------------
The "Show in web browser" action was originally a "Show Welcome Page" action, and had since been converted. This action was not originally designed to show modules, just the server's welcome page. It seems adding the ability to open a specific module was added later, and it seems to have inefficiently duplicated code done elsewhere.
The patch is to use the ILaunchAdapter types which underly the "Run On Server" action, which has the effect of re-using most of the code from run-on-server.
I'll be submitting a PR shortly, once my DNS returns. UGH.
> Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-15502
> URL: https://issues.jboss.org/browse/JBIDE-15502
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Tomas Repel
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
>
> I am using JBDS 7.0.0.GA with Integration Stack, EAP 6.1.0 is configured in Servers tab. When importing JDF example ejb-in-ear [1], then right-click on jboss-ejb-in-ear-ear -> Run As -> Run on Server, the example is deployed and the internal browser window is opened automatically using following URL: http://localhost:8080/jboss-ejb-in-ear/greeter.jsf (this is correct behavior).
> If you go to Servers tab, expand the EAP 6.1 Server, right-click on deployed jboss-ejb-in-ear-ear, use Show in menu item and then click Web Browser, the internal browser is opened with wrong URL (http://localhost:8080/jboss-ejb-in-ear-web/).
> It seems the configuration in application.xml file is ignored for some reason.
> [1] http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/ejb-in-ear/
--
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, 5 months