[JBoss JIRA] (JBIDE-13578) Provide quickfixes to existing JAX-RS Application
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13578?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-13578:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> Provide quickfixes to existing JAX-RS Application
> -------------------------------------------------
>
> Key: JBIDE-13578
> URL: https://issues.jboss.org/browse/JBIDE-13578
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> A quickfix to annotate the JAX-RS Application with javax.ws.rs.ApplicationPath should be provided if an error is detected.
> ----
> From JAX-RS 1.1 spec, chap 2.3.2:
> When using the pluggability mechanism the following conditions MUST be met:
> • If no Application subclass is present the added servlet MUST be named: javax.ws.rs.core.Application
> and all root resource classes and providers packaged in the web application MUST be included in the published JAX-RS application. The application MUST be packaged with a web.xml that specifies a servlet mapping for the added servlet.
> • If an Application subclass is present and there is already a servlet defined that has a servlet initial- ization parameter named:
> javax.ws.rs.Application
> whose value is the fully qualified name of the Application subclass then no new servlet should be added by the JAX-RS implementation’s ContainerInitializer since the application is already being handled by an existing servlet.
> • If an Application subclass is present that is not being handled by an existing servlet then the servlet added by the ContainerInitializer MUST be named with the fully qualified name of the Application subclass. If the Application subclass is annotated with @ApplicationPath and no servlet-mapping exists for the added servlet then a new servlet mapping is added with the value of the @ApplicationPath annotation with ”/*” appended otherwise the existing mapping is used. If the Application subclass is not annotated with @ApplicationPath then the application MUST be packaged with a web.xml that specifies a servlet mapping for the added servlet. It is an error for more than one application to be deployed at the same effective servlet mapping
--
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, 4 months
[JBoss JIRA] (JBIDE-14842) Include optional dependencies in pom.xml at surefire level
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14842?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14842:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> Include optional dependencies in pom.xml at surefire level
> ----------------------------------------------------------
>
> Key: JBIDE-14842
> URL: https://issues.jboss.org/browse/JBIDE-14842
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.1.0.Beta1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> running tests during a tycho build on MacOSX requires an optional/platform specific bundle (o.e.jdt.launching.macosx) that is currently defined in a profile.
> Problem is that this profile includes *all* optional dependencies, not only this one, while other profiles (ie, platform) include no optional dependency at all.
> Solution: configure this optional dependency at the surefire level and for macosx only
--
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, 4 months
[JBoss JIRA] (JBIDE-15881) Annotated field with QueryParam missing in URL Endpoint template
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15881?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15881:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> Annotated field with QueryParam missing in URL Endpoint template
> ----------------------------------------------------------------
>
> Key: JBIDE-15881
> URL: https://issues.jboss.org/browse/JBIDE-15881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo1")
> private String foo2;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> ASSERT: the URL Template for the Endpoint should be something like
> /products/{productType}/{id}?foo1={String}
--
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, 4 months
[JBoss JIRA] (JBIDE-13309) New Restful Webservice wizard shouldn't change web.xml by default
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13309?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-13309:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> New Restful Webservice wizard shouldn't change web.xml by default
> -----------------------------------------------------------------
>
> Key: JBIDE-13309
> URL: https://issues.jboss.org/browse/JBIDE-13309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Pete Muir
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> We recommend the class-style activation of JAX-RS applications
> {code}
> /**
> * A class extending {@link Application} and annotated with @ApplicationPath is the Java EE 6
> * "no XML" approach to activating JAX-RS.
> *
> * <p>
> * Resources are served relative to the servlet path specified in the {@link ApplicationPath}
> * annotation.
> * </p>
> */
> @ApplicationPath("/rest")
> public class JaxRsActivator extends Application {
> /* class body intentionally left blank */
> }
> {code}
> JBDS should offer this as the default approach.
--
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, 4 months
[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-13003:
----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> No support for inheritance in JAX-RS API scan
> ---------------------------------------------
>
> Key: JBIDE-13003
> URL: https://issues.jboss.org/browse/JBIDE-13003
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Alpha2
> Reporter: Ron Ratovsky
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> Assume:
> class BaseRest {
> @POST
> public Response save(Object o) {
> ....
> }
> }
> @Path("/url")
> class RealRest extends BaseRest {}
> The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview.
> While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class.
--
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, 4 months
[JBoss JIRA] (JBIDE-15807) Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15807?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15807:
----------------------------------------
Ubuntu, OpenJDK 1.7.0_45
VM arguments:
-Xmx2048M
-Xms256M
-XX:PermSize=512M
-XX:MaxPermSize=1024M
> Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-15807
> URL: https://issues.jboss.org/browse/JBIDE-15807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> 1. I tried to run JBDS from developer's environment with vm args - -XX:MaxPermSize=512m -Xms1024m -Xmx2048m with all plugins from my workspace
> and I got follow exception:
> {code}
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.createEntry(HashMap.java:869)
> at java.util.HashMap.addEntry(HashMap.java:856)
> at java.util.HashMap.put(HashMap.java:484)
> at org.apache.felix.resolver.Candidates.copy(Candidates.java:1002)
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1288)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1083)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:261)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.refresh(ModuleContainer.java:877)
> at org.eclipse.osgi.storage.Storage.discardBundlesOnLoad(Storage.java:206)
> at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:87)
> at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:75)
> at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:287)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> 2. If I try to run new run configuration with only plugins from target platform I got follow stack trace:
> {code}
> !SESSION 2013-10-28 10:29:47.350 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_24
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.platform.ide
> Command-line arguments: -product org.eclipse.platform.ide -data /home/daniel/workspaces/JBDS_GIT/../runtime-New_configuration(2) -dev file:/home/daniel/workspaces/JBDS_GIT/.metadata/.plugins/org.eclipse.pde.core/New_configuration (2)/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog
> !ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2013-10-28 10:36:19.748
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:782)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:151)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:310)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.addEntry(HashMap.java:770)
> at java.util.HashMap.put(HashMap.java:402)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196)
> at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> Root exception:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.addEntry(HashMap.java:770)
> at java.util.HashMap.put(HashMap.java:402)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196)
> at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> {code}
> 3. If I try same as 2. but with "Running Platform" as target platform - eclipse starts
--
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, 4 months