[JBoss JIRA] (JBIDE-19051) Show warning in case of ambiguous RESTful web services path
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19051?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-19051:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Show warning in case of ambiguous RESTful web services path
> -----------------------------------------------------------
>
> Key: JBIDE-19051
> URL: https://issues.jboss.org/browse/JBIDE-19051
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: jax-rs
> Fix For: 4.5.x
>
>
> If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services.
> It's possible to have multiple items under JAX-RS Web Services node with same label.
> Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22918) RuntimeException below DomUtil.nodeToString (thrown in SerializerBase.getNamespaceURI)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22918?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22918:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> RuntimeException below DomUtil.nodeToString (thrown in SerializerBase.getNamespaceURI)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-22918
> URL: https://issues.jboss.org/browse/JBIDE-22918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.RuntimeException: HIDDEN
> at com.sun.org.apache.xml.internal.serializer.SerializerBase.getNamespaceURI(null:-1)
> at com.sun.org.apache.xml.internal.serializer.SerializerBase.addAttribute(null:-1)
> at com.sun.org.apache.xml.internal.serializer.ToUnknownStream.addAttribute(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(null:-1)
> at org.jboss.tools.vpe.preview.core.transform.DomUtil.nodeToString(DomUtil.java:45)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:84)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | org.jboss.tools.vpe.preview.core | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 3.19.0 | 4.2.0 |
> | MacOSX | 10.11.4 | 10.11.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56fcda44e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-23732) Implement new batch integration ui tests for content assist features in job.xml file.
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23732?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23732:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Implement new batch integration ui tests for content assist features in job.xml file.
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-23732
> URL: https://issues.jboss.org/browse/JBIDE-23732
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.4.2.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: batch, integration_tests
> Fix For: 4.5.x
>
>
> These tests covers both view tabs where content assist feature is used (design and source view). Test:
> 1. Offered batch artifacts in content assist menu for ref attribute
> 2. Offered element's id for id attribute with correct level of context
> 3. Fully qualified names of exceptions used in class attribute of include/exclude tag
> 4. Properties from both property definition in job.xml and from batch artifact with @BatchProperty annotation
> 5. Proper list of element's id referred from next, to attributes and/or restart attributes
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22969:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.5.1.AM1)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
> Attachments: proxy_settings.png, proxy_settings_2.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22584) jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22584:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.5.1.AM1)
> jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22584
> URL: https://issues.jboss.org/browse/JBIDE-22584
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, central-update
> Affects Versions: 4.4.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
>
> Normally, jbosstools-central is built before jbosstools-discovery.
> However, running jbosstools-central build for the first time, ran into this:
> {code}
> 22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s]
> 22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED
> 22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED
> 22:43:52 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could not get content -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs...
> Or, this could be a problem w/ bootstrapping values in ide-config.properties?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months