[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19605:
-----------------------------------
Summary: Avoid need for multiple javax.servlet (was: Avoid need for multiple jetty)
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19605:
----------------------------------------
[~ibuziuk] Thanks!
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple jetty
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19605:
-------------------------------------
AFAIK this is not about jetty bundles but about javax.servlet ones
> Avoid need for multiple jetty
> -----------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBIDE-19605) Avoid need for multiple jetty
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-19605:
--------------------------------------
Summary: Avoid need for multiple jetty
Key: JBIDE-19605
URL: https://issues.jboss.org/browse/JBIDE-19605
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: target-platform, webservices
Affects Versions: 4.3.0.Alpha2
Reporter: Mickael Istria
We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
{code}
On 04/15/2015 11:56 PM, Nick Boldt wrote:
> Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> 3.1.0 in JBDS.
> More importantly... SHOULD we be including both? Or can we just include
> 3.1.0 and drop 3.0.0?
I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
So I've tried the ultimate test:
$ cd jbdevstudio-9.0.0.Alpha2/studio
$ rm plugins/javax.servlet_3.0.0*
$ ./jbdevstudio
And saw
!ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
at org.eclipse.osgi.container.Module.start(Module.java:434)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBIDE-17822) Launch shortcut enablement expression caused exception
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17822?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17822:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Launch shortcut enablement expression caused exception
> ------------------------------------------------------
>
> Key: JBIDE-17822
> URL: https://issues.jboss.org/browse/JBIDE-17822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Beta1
>
> Attachments: error1, error2, error3, error4, error5
>
>
> Sometimes when expanding JAX-RS Explorer, a bunch of errors appears in Error Log.
> There are 5 similar errors:
> {code}
> Launch shortcut 'org.testng.eclipse.shortcut' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.testng.eclipse.shortcut.testngSuite' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesPattern to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.jboss.tools.maven.actions.LifeCycleCleanVerify' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.jboss.tools.maven.ui.isCleanVerifyMenuEnabled to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.eclipse.ant.ui.antShortcutWithDialog' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
> {code}
> Launch shortcut 'org.eclipse.ant.ui.antShortcut' enablement expression caused exception. Shortcut was removed.
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.debug.ui.matchesContentType to type class org.jboss.tools.ws.jaxrs.ui.cnf.UriPathTemplateElement
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBIDE-18516) JAX-RS Validator should report problem when @DefaultValue is used alone
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18516?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18516:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> JAX-RS Validator should report problem when @DefaultValue is used alone
> -----------------------------------------------------------------------
>
> Key: JBIDE-18516
> URL: https://issues.jboss.org/browse/JBIDE-18516
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.2.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Beta1
>
>
> If a method parameter is annotated with {{@DefaultValue}} but has _no_ {{@QueryParam}} (or similar) annotation, then the application will most certainly fail with an error message such as:
> {code}
> failed to execute: javax.ws.rs.NotSupportedException: Could not find message body reader for type: int of content type: */*
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months
[JBoss JIRA] (JBIDE-18101) API updates
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18101?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18101:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> API updates
> -----------
>
> Key: JBIDE-18101
> URL: https://issues.jboss.org/browse/JBIDE-18101
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.0.Beta1
>
>
> Unify the JaxrsElement builders to provide the same methods:
> - buildTransient()
> - buildInMetamodel(JaxrsMetamodel)
> Also, simplify the JaxrsElement#update() method (code could be simpler, with less if/else blocks)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 12 months