[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-12860:
----------------------------------------
{quote}Why not open bugzilla with details above and provide patch with tests so we can push it in luna.{quote}
We can do it. But we can't wait for Luna to get it fixed. We have to fix it now. So we are going to fix it on our side first. Then we could provide a patch for WST which BTW will be useless for us since we already fixed it JBT.
> 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, 7 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-12860:
---------------------------------------
{quote}We have already spent so much time on debugging WST validation and adopting our CommonValidation to every weird behaviour/bugs of WST that we made an ugly monster out of our CommonValidation which is hard to support and extend. We should have created in the first place our own independent validation builder instead of using WST. It would be much easier.{quote}
Why not open bugzilla with details above and provide patch with tests so we can push it in luna.
> 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, 7 months
[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15499:
---------------------------------------
There is no differ between Beta1-v20131025-1922-B102, Beta1-v20131026-0928-B470 and Beta1-v20131031-0912-B483
The issue you have described, can also be reproduced using Beta1-v20131025-1922-B102.
Eclipse treats your red areas as the Eclipse editor area, but doesn't as the JBoss Central editor area.
You can also reproduce this issue when dropping a URL to the title area of the Java editor. The issue will happen even if you use pure Eclipse without any JBoss Tools plugins.
The issue is reproducible on Windows and Linux with the difference that Windows doesn't throw an exception.
The issue can be fixed if we add our D&D to the Eclipse editor area. I have created JBIDE-15838 and will try to fix it.
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
> Attachments: JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 7 months
[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15499 at 11/1/13 1:36 PM:
-------------------------------------------------------------
I have updated my system from the older kernel to this:
{code}Linux thunk 3.11.4-101.fc18.x86_64 #1 SMP Thu Oct 10 14:05:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux{code}
Still works fine, as explained above, in Eclipse JEE SR1 with org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102.jar installed.
However, I can reproduce the unhandled loop exception in JBDS 7.1.0.Beta1-v20131026-0928-B470.
If I then update JBDS to 7.1.0.Beta1-v20131031-0912-B483 from [1], which includes these central plugins:
{code}
org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102.jar
com.jboss.jbds.central_7.1.0.Beta1-v20131031-0912-B483.jar
{code}
I can install successfully, but ONLY if I drag into the editor itself, *not into its edges*.
If I drag anywhere else, I get Unhandled event loop exception (see below for green areas that work and red areas that do not). Everything outside the Central editor (such as the main icon/coolbar at the top of the UI, the Outline view, or the Error Log view) works fine when I drag this URL [2] from Firefox 24.0 into it.
With an earlier JBDS build, I think other views failed to hear the events too. (Not sure.)
!JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png!
[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71...
[2] http://download.jboss.org/jbosstools/central/install?connectors=org.tigri...
was (Author: nickboldt):
I have updated my system from the older kernel to this:
{code}Linux thunk 3.11.4-101.fc18.x86_64 #1 SMP Thu Oct 10 14:05:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux{code}
Still works fine, as explained above, in Eclipse JEE SR1 with org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102.jar installed.
However, I can reproduce the unhandled loop exception in JBDS 7.1.0.Beta1-v20131026-0928-B470.
If I then update JBDS to 7.1.0.Beta1-v20131031-0912-B483 from [1], I can install successfully, but ONLY if I drag into the editor itself. If I drag anywhere else, I get Unhandled event loop exception (see below for green areas that work and red areas that do not). Everything outside the Central editor (such as the main icon/coolbar at the top of the UI, the Outline view, or the Error Log view) works fine when I drag this URL [2] from Firefox 24.0 into it.
!JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png!
[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71...
[2] http://download.jboss.org/jbosstools/central/install?connectors=org.tigri...
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
> Attachments: JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 7 months
[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15499 at 11/1/13 1:32 PM:
-------------------------------------------------------------
I have updated my system from the older kernel to this:
{code}Linux thunk 3.11.4-101.fc18.x86_64 #1 SMP Thu Oct 10 14:05:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux{code}
Still works fine, as explained above, in Eclipse JEE SR1 with org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102.jar installed.
However, I can reproduce the unhandled loop exception in JBDS 7.1.0.Beta1-v20131026-0928-B470.
If I then update JBDS to 7.1.0.Beta1-v20131031-0912-B483 from [1], I can install successfully, but ONLY if I drag into the editor itself. If I drag anywhere else, I get Unhandled event loop exception (see below for green areas that work and red areas that do not). Everything outside the Central editor (such as the main icon/coolbar at the top of the UI, the Outline view, or the Error Log view) works fine when I drag this URL [2] from Firefox 24.0 into it.
!JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png!
[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71...
[2] http://download.jboss.org/jbosstools/central/install?connectors=org.tigri...
was (Author: nickboldt):
I have updated my system from the older kernel to this:
{code}Linux thunk 3.11.4-101.fc18.x86_64 #1 SMP Thu Oct 10 14:05:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux{code}
Still works fine, as explained above, in Eclipse JEE SR1 with org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102.jar installed.
However, I can reproduce the unhandled loop exception in JBDS 7.1.0.Beta1-v20131026-0928-B470.
If I then update JBDS to 7.1.0.Beta1-v20131031-0912-B483 from [1], I can install successfully, but ONLY if I drag into the editor itself. If I drag anywhere else, I get Unhandled event loop exception (see below for green areas that work and red areas that do not). Everything outside the editor throws the same Unhandled event loop exception too.
!JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png!
[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71...
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
> Attachments: JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 7 months
[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15499:
-------------------------------
Attachment: JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png
I have updated my system from the older kernel to this:
{code}Linux thunk 3.11.4-101.fc18.x86_64 #1 SMP Thu Oct 10 14:05:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux{code}
Still works fine, as explained above, in Eclipse JEE SR1 with org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102.jar installed.
However, I can reproduce the unhandled loop exception in JBDS 7.1.0.Beta1-v20131026-0928-B470.
If I then update JBDS to 7.1.0.Beta1-v20131031-0912-B483 from [1], I can install successfully, but ONLY if I drag into the editor itself. If I drag anywhere else, I get Unhandled event loop exception (see below for green areas that work and red areas that do not). Everything outside the editor throws the same Unhandled event loop exception too.
!JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png!
[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71...
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
> Attachments: JBIDE15499-JBDS710beta1b-areas-in-green-and-red.png
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 7 months
[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-15499 at 11/1/13 1:25 PM:
----------------------------------------------------------------
{quote}
which mechanism is it you would use to register DND ?
{quote}
{code}
DropTarget target = new DropTarget(control, DND.DROP_MOVE | DND.DROP_COPY | DND.DROP_LINK);
target.setTransfer(new Transfer[] { URLTransfer.getInstance() });
...
target.addDropListener(...);
{code}
{quote}
looks like DropTarget is a bit tricky but they seem to have added api to get listeners - at least that is what https://bugs.eclipse.org/bugs/show_bug.cgi?id=215388 documents.
{quote}
We would use that API if the MPC client used it too. However, the MPC client doesn't use the API so if our plugin would register DND before the MPC client, the MPC client would throw an annoying exception that would propose to shutdown Eclipse. We can't control the order in which DNDs are registered.
I can create a bug against MPC and add a patch if you want.
I have created a PR.
If you don't have the MPC plugin, you will be able to drag an url to an Eclipse instance (the toolbar, menu, or a view or editor that doesn't have a drop target).
Otherwise, you can drag it to the JBoss Central editor. The MPC plugin will work as usual.
The installation works as follows:
- if some connector can't be found or is already installed, Eclipse will show a dialog with those informations and allows a user to continue or stop the installation.
If the user wants to continue with the installation, Eclipse will call the standard P2's install wizard (including the Remediation page). I will fix JBIDE-14794 immediately after applying this PR.
See http://screencast.com/t/e6lmfJktil. The screencast uses the http://download.jboss.org/jbosstools/central/install?connectors=org.tigri... url.
was (Author: snjeza):
{quoute}
which mechanism is it you would use to register DND ?
{quote}
{code}
DropTarget target = new DropTarget(control, DND.DROP_MOVE | DND.DROP_COPY | DND.DROP_LINK);
target.setTransfer(new Transfer[] { URLTransfer.getInstance() });
...
target.addDropListener(...);
{code}
{quote}
looks like DropTarget is a bit tricky but they seem to have added api to get listeners - at least that is what https://bugs.eclipse.org/bugs/show_bug.cgi?id=215388 documents.
{quote}
We would use that API if the MPC client used it too. However, the MPC client doesn't use the API so if our plugin would register DND before the MPC client, the MPC client would throw an annoying exception that would propose to shutdown Eclipse. We can't control the order in which DNDs are registered.
I can create a bug against MPC and add a patch if you want.
I have created a PR.
If you don't have the MPC plugin, you will be able to drag an url to an Eclipse instance (the toolbar, menu, or a view or editor that doesn't have a drop target).
Otherwise, you can drag it to the JBoss Central editor. The MPC plugin will work as usual.
The installation works as follows:
- if some connector can't be found or is already installed, Eclipse will show a dialog with those informations and allows a user to continue or stop the installation.
If the user wants to continue with the installation, Eclipse will call the standard P2's install wizard (including the Remediation page). I will fix JBIDE-14794 immediately after applying this PR.
See http://screencast.com/t/e6lmfJktil. The screencast uses the http://download.jboss.org/jbosstools/central/install?connectors=org.tigri... url.
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 7 months
[JBoss JIRA] (JBIDE-15830) openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15830:
----------------------------------
Component/s: openshift
> openshift-java-client: incompatibility with OpenShift Enterprise and Origin when using the remote-user authentication plugin
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15830
> URL: https://issues.jboss.org/browse/JBIDE-15830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Brenton Leanhardt
> Assignee: Andre Dietisheim
> Labels: openshift-java-client
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of authentication to be handled by Apache and other parts to be delegated to the openshift-origin-controller codebase. I've found that all versions of openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the OpenShift remote-user plugin.
> In order for a request to bypass the Apache authentication and passthrough to the OpenShift Broker the user-agent header is inspected. If the user-agent is 'OpenShift' then the Broker will require an encrypted authentication token. Today this is used by the jenkins cartridge but I believe it's also still used for scaling.
> You can see this for details:
> https://github.com/openshift/origin-server/blob/master/documentation/arch...
> In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift' however all versions after this set the user-agent to the java version (eg, User-Agent: Java/1.7.0_45).
--
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, 7 months