May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11612) Runtime detection does not add database connection for EAP6/AS7

by Martin Malina (JIRA)

Martin Malina created JBIDE-11612: ------------------------------------- Summary: Runtime detection does not add database connection for EAP6/AS7 Key: JBIDE-11612 URL: https://issues.jboss.org/browse/JBIDE-11612 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Affects Versions: 3.3.0.Beta3 Environment: JBT nightly 2012-04-21 Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 3.3.0.Beta3 When you search for JBoss AS servers using Runtime Detection, database connection is detected and configured for EAP 5.1.2, but not for EAP6/AS7. In AS7, Hypersonic is no longer used, but instead H2 is included. The common scenario for me is to detect JBoss AS, detect Seam and then create a Seam Project. But for a Seam Project you need a database connection which is automatically configured for EAP 5.x, but not EAP6/AS7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
8
0 / 0

[JBoss JIRA] (JBIDE-11768) All @MatrixParam parameters values are equals to first one's when setting with "WS Tester: URL Parameters" dialog

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11768: ----------------------------------------- Summary: All @MatrixParam parameters values are equals to first one's when setting with "WS Tester: URL Parameters" dialog Key: JBIDE-11768 URL: https://issues.jboss.org/browse/JBIDE-11768 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11732) Question mark is weirdly added after last query param in Web Service Tester

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11732: ----------------------------------------- Summary: Question mark is weirdly added after last query param in Web Service Tester Key: JBIDE-11732 URL: https://issues.jboss.org/browse/JBIDE-11732 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta3, 3.3.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11867) Tooling for CDI Event identifies invalid observer

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-11867: ---------------------------------- Summary: Tooling for CDI Event identifies invalid observer Key: JBIDE-11867 URL: https://issues.jboss.org/browse/JBIDE-11867 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta2 Environment: Eclipse Version: Indigo Service Release 2 Build id: 20120216-1857 JBoss Tools Nightly Context and Dependency Injection Tools 1.2.0.v20120508-1258-H1103-CR1 org.jboss.tools.cdi.feature.feature.group JBoss by Red Hat Reporter: Cody Lerum Assignee: Alexey Kazakov Attachments: cdi_event.png With the following event {code} @Inject private Event<EventLog> eventLog; {code} Tooling suggests that the following is a valid observer which it is not because it specifics an additional qualifier. Additionally it should show a warning that no observer exists to receive this event. {code} public void log(@Observes @Now EventLog eventLog) { ... } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-11838) Exclude methods named get* with return type void from properties

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-11838: --------------------------------------------- Summary: Exclude methods named get* with return type void from properties Key: JBIDE-11838 URL: https://issues.jboss.org/browse/JBIDE-11838 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.CR1 EXECUTE: Create bean {code} @Named public class MyBean { public void getName() { } } {code} Method getName() does not define Java property 'name', because it has no return. ASSERT: Content assist does not suggest 'name' in #{myBean.|} ASSERT: Open-on does not suggest to open method getName() in #{myBean.name}. ASSERT: EL validation marks 'name' as not recognized in #{myBean.name}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-11731) beans.xml validation error message is not straightforward

by Tomas Remes (JIRA)

Tomas Remes created JBIDE-11731: ----------------------------------- Summary: beans.xml validation error message is not straightforward Key: JBIDE-11731 URL: https://issues.jboss.org/browse/JBIDE-11731 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta2 Reporter: Tomas Remes Assignee: Alexey Kazakov When you reference some nonexisting class in beans.xml, following error message is displayed: There is no class with the specified name [JSR-299 §8.2] I think that's not much helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-11892) JaxRsMetaModelBuilder runs on non-JAXRS enabled projects

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-11892: ----------------------------------- Summary: JaxRsMetaModelBuilder runs on non-JAXRS enabled projects Key: JBIDE-11892 URL: https://issues.jboss.org/browse/JBIDE-11892 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Fred Bricon Assignee: Xavier Coulon Priority: Critical Fix For: 3.3.0.CR1 At some point, I had severe performance issues (all cores at 100%) while importing the projects from https://github.com/hibernate/hibernate-search. I disabled all the JBT maven configurators to try to see if this was caused by our maven integration. I can't tell if it's related but, during import, I saw several JAX RS Metamodel build jobs running very slowly, even though none of the hibernate search projects have the jaxrs nature or builder enabled. jstack showed me that : {noformat} "Worker-114" prio=6 tid=0x0000000010134800 nid=0x310 waiting on condition [0x00000000203de000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:259) at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:214) at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:515) at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:584) at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.searchForAnnotatedTypes(JaxrsAnnotationsScanner.java:172) at org.jboss.tools.ws.jaxrs.core.jdt.JaxrsAnnotationsScanner.findHttpMethodTypes(JaxrsAnnotationsScanner.java:148) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:182) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:122) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelBuildJob.run(JaxrsMetamodelBuildJob.java:56) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} JaxrsMetamodelBuildJob doesn't seem to filter the projects elligible for JAXRS stuff. I can't say this is the cause of the performance issues I saw (I need to do some profiling) but anyway JaxrsMetamodelBuildJob should never run for non-JAXRS enabled projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] (JBDS-2147) branch numbers for JBDS SOA Tooling are inconsistent

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2147: -------------------------------- Summary: branch numbers for JBDS SOA Tooling are inconsistent Key: JBDS-2147 URL: https://issues.jboss.org/browse/JBDS-2147 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 5.0.0.Beta2-SOA Reporter: Nick Boldt Assignee: Douglas Palmer http://svn.jboss.org/repos/devstudio/branches/ has the following soatools branches: http://svn.jboss.org/repos/devstudio/branches/soatools-5.0.0.Beta1/ http://svn.jboss.org/repos/devstudio/branches/soatools-3.3.0.Beta2/ Why the change from 5.0 to 3.3? Note that for http://svn.jboss.org/repos/jbosstools/branches/ we have: http://svn.jboss.org/repos/jbosstools/branches/soatools-3.3.0.Beta1/ http://svn.jboss.org/repos/jbosstools/branches/soatools-3.3.0.Beta2/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12002) Wrong reference in unified.target to "org.jboss.tools.maven.apt.feature"

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12002: -------------------------------------- Summary: Wrong reference in unified.target to "org.jboss.tools.maven.apt.feature" Key: JBIDE-12002 URL: https://issues.jboss.org/browse/JBIDE-12002 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Reporter: Mickael Istria Assignee: Nick Boldt Fix For: 3.3.0.CR1 When trying a build using up-to-date Target Platforms, we see {code} > mvn clean install -Dmaven.test.skip -P unified.target ... org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/mistria/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT-unified.target at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: Failed to resolve target definition /home/mistria/.m2/repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT-unified.target at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.addTargetFileContentToTargetPlatform(P2TargetPlatformResolver.java:407) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:220) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:89) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:61) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.jboss.tools.maven.apt.feature.feature.group/1.0.0.201205021739" in the repositories of the current location at org.eclipse.tycho.p2.target.TargetDefinitionResolver.getUnitInstance(TargetDefinitionResolver.java:199) at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:111) at org.eclipse.tycho.p2.target.TargetPlatformBuilderImpl.addTargetDefinition(TargetPlatformBuilderImpl.java:330) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.addTargetFileContentToTargetPlatform(P2TargetPlatformResolver.java:402) ... 16 more ... {code} Not sure about how this should be solved. Simply remove reference to this feature in unified.target ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-11973) should maven.gwt feature be included in JBDS or JBDS Extras?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11973: ---------------------------------- Summary: should maven.gwt feature be included in JBDS or JBDS Extras? Key: JBIDE-11973 URL: https://issues.jboss.org/browse/JBIDE-11973 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, central, GWT, maven, updatesite Affects Versions: 3.3.0.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.CR1 Noticed that while maven.gwt is on the JBT Nightly site (http://download.jboss.org/jbosstools/updates/nightly/core/trunk/features/...), it's not in JBDS Product, JBDS Extras, or JBDS Central. Should it be? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
13
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2012