[JBoss JIRA] (JBIDE-12618) CLONE - Remove need for jax-rs-api.jar
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12618?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-12618.
-----------------------------------
Release Notes Text: The JAX-RS plugin does not bundle the jaxrs-api.jar anymore. This jar was just used to retrieve some class names.
Resolution: Done
> CLONE - Remove need for jax-rs-api.jar
> --------------------------------------
>
> Key: JBIDE-12618
> URL: https://issues.jboss.org/browse/JBIDE-12618
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Webservices
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 3.3.2
>
> Attachments: JBIDE-10115.patch, JBIDE-10115b.patch
>
>
> The Eclipse Orbit repository (http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/r...) contains the JAX-RS API bundled as a plugin, so we could probably remove the jars I've put in the org.jboss.tools.ws.jaxrs projects' /lib folder and just add a dependency on that plugin, which would reduce the SVN size.
> On the other side, it would add an external dependency that devs should grab to avoid compilation errors, and it may have an impact on the build chain (have to confirm that with Nick Boldt)
> WDYT ?
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-12224) Building JAX-RS metamodel is very slow at times
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12224?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-12224.
-----------------------------------
Release Notes Text:
Previous version of the JAX-RS plugin would scan jars added in the project classpath to look for annotated classes and JAX-RS HTTP Methods. This behavior has been disabled, and the JAX-RS HTTP Methods (@GET, @POST, etc.) are are now built in the plugin.
The result is that changing the project classpath does not involve a long build because of the JAX-RS plugin scanning the jars anymore.
Resolution: Done
> Building JAX-RS metamodel is very slow at times
> -----------------------------------------------
>
> Key: JBIDE-12224
> URL: https://issues.jboss.org/browse/JBIDE-12224
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.0.CR1
> Reporter: Pete Muir
> Assignee: Xavier Coulon
> Labels: respin-a
> Attachments: JBIDE-12224.m4v, JBIDE-12224.patch
>
>
> I haven't worked out when :-(
> I'll try to reproduce it now
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-12619) CLONE - Building JAX-RS metamodel is very slow at times
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12619?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-12619.
-----------------------------------
Release Notes Text:
Previous version of the JAX-RS plugin would scan jars added in the project classpath to look for annotated classes and JAX-RS HTTP Methods. This behavior has been disabled, and the JAX-RS HTTP Methods (@GET, @POST, etc.) are are now built in the plugin.
The result is that changing the project classpath does not involve a long build because of the JAX-RS plugin scanning the jars anymore.
Resolution: Done
> CLONE - Building JAX-RS metamodel is very slow at times
> -------------------------------------------------------
>
> Key: JBIDE-12619
> URL: https://issues.jboss.org/browse/JBIDE-12619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 3.3.2
>
> Attachments: JBIDE-12224.m4v, JBIDE-12224.patch
>
>
> I haven't worked out when :-(
> I'll try to reproduce it now
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13377) Couldn't add more than one database cartridges to openshift app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13377?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-13377.
--------------------------------------
Resolution: Duplicate Issue
thanks for reporting, jing. But this was already filed in JBIDE-13235.
> Couldn't add more than one database cartridges to openshift app
> ---------------------------------------------------------------
>
> Key: JBIDE-13377
> URL: https://issues.jboss.org/browse/JBIDE-13377
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Environment: Jboss openshift tools plugin- 2.4.0.Final-v20130114-2102-B98
> Eclipse:4.2.0
> Reporter: jing zh
> Assignee: Andre Dietisheim
> Attachments: add_cartridge.log, add_cartridge_0115.png, add_cartridge_2_0115.png
>
>
> 1. ASSERT: make sure you're using jboss tool version 2.4.0.Final-v20130114-2102-B98 with eclipse 4.2.0
> 2. EXEC: Create a new openshift user
> 3. EXEC: Create an app, like python-2.6 app.
> 4. EXEC: Add cartridge mysql-5.1 and postgresql-8.4.
> Excepted results:
> Both DB cartridges can be added to the app successfully as it supported to add both database via rhc client.
> Actual results:
> Error is shown that only 1 embedded database permitted.
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-11889) Birt 3.7.2 ClassNotFoundException: javax.xml.parsers.DocumentBuilderFactory with birt module on JBoss 7.1.1
by maher gharbi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11889?page=com.atlassian.jira.plugi... ]
maher gharbi commented on JBIDE-11889:
--------------------------------------
Hi Markus,
Could please tell more about how you integrated birt with JBOSS 7.1.1
I'm facing problems to do this and need it.
Thks
> Birt 3.7.2 ClassNotFoundException: javax.xml.parsers.DocumentBuilderFactory with birt module on JBoss 7.1.1
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11889
> URL: https://issues.jboss.org/browse/JBIDE-11889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Bean Validation
> Affects Versions: 3.2.0.Final
> Environment: Windows XP Service Pack 3
> Reporter: Markus Wuestemann
> Assignee: Snjezana Peco
> Labels: birt
> Fix For: 3.3.0.CR1
>
>
> I'm using Birt 3.7.2 and Jboss 7.1.1.
> I'm using the ReportEngine and added all jar file into the projects lib folder which works perfectly. To avoid a 50mb ear-file i created a JBoss module where I placed all the jars but always get the following Exception at factory.createReportEngine( c );
> ERROR [org.jboss.ws.common.invocation.InvocationHandlerJAXWS] (http--0.0.0.0-8080-1) Method invocation failed with exception: null: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_31]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_31]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_31]
> at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_31]
> at org.jboss.ws.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:111)
> at org.jboss.wsf.stack.cxf.JBossWSInvoker._invokeInternal(JBossWSInvoker.java:181)
> at org.jboss.wsf.stack.cxf.JBossWSInvoker.invoke(JBossWSInvoker.java:127)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_31]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_31]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_31]
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:207)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:108)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.3.GA.jar:2.0.3.GA]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397) [jbossweb-7.0.13.Final.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_31]
> Caused by: java.lang.NoClassDefFoundError: javax/xml/parsers/DocumentBuilderFactory
> at org.eclipse.birt.core.framework.jar.BundleLoader.loadExtensions(BundleLoader.java:147) [org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar:]
> at org.eclipse.birt.core.framework.jar.BundleLoader.load(BundleLoader.java:63) [org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar:]
> at org.eclipse.birt.core.framework.jar.ServicePlatform.installBundle(ServicePlatform.java:57) [org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar:]
> at org.eclipse.birt.core.framework.jar.ServiceLauncher.startup(ServiceLauncher.java:71) [org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar:]
> at org.eclipse.birt.core.framework.Platform.startup(Platform.java:75) [org.eclipse.birt.runtime_3.7.2.v20120214-1408.jar:]
> at com.gelita.webservice.HtmlGenerate.aeuGetReportAsHtml(HtmlGenerate.java:68) [classes:]
> ... 39 more
> Caused by: java.lang.ClassNotFoundException: javax.xml.parsers.DocumentBuilderFactory from [Module "org.birt:main" from local module loader @51052d (roots: C:\jboss-as-7.1.1.Final\modules)]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> ... 45 more
--
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
13 years, 5 months
[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13346:
-------------------------------------
This specific use case should not log the warning, so I'll add a new method signature to suppress logging. Sounds like a plan to me.
> DirectoryScanner fails on non-existing folders
> ----------------------------------------------
>
> Key: JBIDE-13346
> URL: https://issues.jboss.org/browse/JBIDE-13346
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives, JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows XP/Windows 7
> Eclipse 4.3M4
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: org.eclipse.wst.common.component
>
>
> DirectoryScanner can be made to fail on non-existing folders.
> In our setup, these folders are possibly picked up from the Deployment Assembly settings.
> The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse.
> But it seems the Archive DirectoryScanner runs before our builder.
> The stack trace looks like this:
>
> {code}
> java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552)
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588)
> at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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
13 years, 5 months