September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9512) Openshift Express: make proj in the local git repo to be recognized as deployable module

by Andre Dietisheim (JIRA)

Openshift Express: make proj in the local git repo to be recognized as deployable module ---------------------------------------------------------------------------------------- Key: JBIDE-9512 URL: https://issues.jboss.org/browse/JBIDE-9512 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 The app that you want to deploy to Openshift Express is present in a local git repo. In order to be able to deploy this proj to an AS7 we need to allow it to be recognized as deployable (WTP-) module -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9511) Openshift Express: create egit action that commits and pushes in 1 step

by Andre Dietisheim (JIRA)

Openshift Express: create egit action that commits and pushes in 1 step ----------------------------------------------------------------------- Key: JBIDE-9511 URL: https://issues.jboss.org/browse/JBIDE-9511 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 Deploying to Openshift Express is done by commiting changes to a local git repo and pushing it to the remote git repo of your app (on openshift). The work would be far smotther if committing and pushing was done in 1 step (compared to the 2 steps that are currently needed in egit) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
18
0 / 0

[JBoss JIRA] Closed: (JBDS-1819) Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-1819?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-1819. ------------------------------ This issue is resolved - any bugs with specific quickstarts will be logged in separate JIRAs. > Configure SOA-P quickstarts to be run OOTB in JBDS 4.1.1 with SOA-P 5.2 > ----------------------------------------------------------------------- > > Key: JBDS-1819 > URL: https://issues.jboss.org/browse/JBDS-1819 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: SOA Platform > Affects Versions: 4.1.0.CR3 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.M1 > > Attachments: bfitzpat_examples.png, product_examples.png, runtimes.png > > > Need to ensure there are sample ESB quickstarts available to run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > Need to verify that all JBDS supplied sample ESB quickstarts run cleanly with SOA-P 5.2 on JBDS 4.1.1 > Was: > This subject comes up now and then - it would be very useful to new users to have the full set of SOA-P quickstarts configured to run OOTB from JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-1806) BPEL validation in BPEL editor is broken

by Len DiMaggio (JIRA)

BPEL validation in BPEL editor is broken ---------------------------------------- Key: JBDS-1806 URL: https://issues.jboss.org/browse/JBDS-1806 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration, SOA Platform Affects Versions: 4.1.0.GA Reporter: Len DiMaggio Priority: Critical BPEL validation in BPEL editor is broken - see: https://issues.jboss.org/browse/SOA-2629 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9697) CLONE - Project Example project zips that require empty folders (i.e. src folders) need to be imported properly

by Len DiMaggio (JIRA)

CLONE - Project Example project zips that require empty folders (i.e. src folders) need to be imported properly --------------------------------------------------------------------------------------------------------------- Key: JBIDE-9697 URL: https://issues.jboss.org/browse/JBIDE-9697 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M2 Reporter: Brian Fitzpatrick Assignee: Snjezana Peco Fix For: 3.2.2.M1, 3.3.0.M3 While working on some new project examples for JBDS 4.1.1, I ran into an issue. I have a project within a project examples zip that has an empty src folder but requires that the folder be in place to compile properly. Talking with Snjeza, she mentioned that the code skips empty folders during the import process. Is there any way to short-circuit that behavior for the "src" directory at least? The workaround is to include a file (like a dummy txt file) in the empty directory so it's no longer empty before you export the project(s) as a zip to be used by the project examples wizard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1818) Seam in EAP 5.1.1 upgraded Drools libraries - update your Project wizards

by Marek Novotny (JIRA)

Seam in EAP 5.1.1 upgraded Drools libraries - update your Project wizards ------------------------------------------------------------------------- Key: JBDS-1818 URL: https://issues.jboss.org/browse/JBDS-1818 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: drools, seam Affects Versions: 4.0.1, 4.1.0.GA Environment: JBDS 4.x, Sun Java 6, Linux Reporter: Marek Novotny Seam in EAP 5.1.1 upgraded Drools libraries tp 5.1.0.BRMS. Drools doesn't have anymore Eclipse Compiler aka core.jar in its dependencies, instead of it there is ecj.jar. Update your Seam Project wizards to include this jar into project classpath. While ecj.jar is not in classpath testng Seam action tests are throwing exception: {noformat} WARN [org.jboss.seam.security.permission.PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required. FAILED CONFIGURATION: @BeforeMethod begin org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.security.ruleBasedPermissionResolver at org.jboss.seam.Component.newInstance(Component.java:2170) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:305) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:279) at org.jboss.seam.contexts.Lifecycle.beginSession(Lifecycle.java:233) at org.jboss.seam.contexts.ServletLifecycle.beginSession(ServletLifecycle.java:181) at org.jboss.seam.mock.AbstractSeamTest.begin(AbstractSeamTest.java:898) at org.jboss.seam.mock.SeamTest.begin(SeamTest.java:31) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:525) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeMethod(Invoker.java:613) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at org.testng.TestRunner.runWorkers(TestRunner.java:1125) at org.testng.TestRunner.privateRun(TestRunner.java:749) at org.testng.TestRunner.run(TestRunner.java:600) at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274) at org.testng.SuiteRunner.run(SuiteRunner.java:223) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:995) at org.testng.TestNG.runSuitesLocally(TestNG.java:920) at org.testng.TestNG.run(TestNG.java:856) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:110) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:205) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174) Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: securityRules at org.jboss.seam.Component.newInstance(Component.java:2170) at org.jboss.seam.Component.getInstance(Component.java:2024) at org.jboss.seam.Component.getInstance(Component.java:1986) at org.jboss.seam.Component.getInstance(Component.java:1980) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:148) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:51) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:54) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:157) at org.jboss.seam.Component$ELInitialValue.getValue(Component.java:2557) at org.jboss.seam.Component.initialize(Component.java:1530) at org.jboss.seam.Component.postConstructJavaBean(Component.java:1456) at org.jboss.seam.Component.postConstruct(Component.java:1379) at org.jboss.seam.Component.newInstance(Component.java:2155) ... 33 more Caused by: org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.rule.builder.dialect.java.JavaDialectConfiguration' at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:283) at org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:268) at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:181) at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:159) at org.jboss.seam.drools.RuleBase.compileRuleBase(RuleBase.java:46) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2275) at org.jboss.seam.Component.callCreateMethod(Component.java:2198) at org.jboss.seam.Component.newInstance(Component.java:2158) ... 49 more Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:94) at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:55) at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:279) ... 62 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1836) Relabel "Certified" features as "Selected" to match the actual level of support provided for those add-ons in 4.x

by Nick Boldt (JIRA)

Relabel "Certified" features as "Selected" to match the actual level of support provided for those add-ons in 4.x ----------------------------------------------------------------------------------------------------------------- Key: JBDS-1836 URL: https://issues.jboss.org/browse/JBDS-1836 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, documentation, updatesite Affects Versions: 4.1.1.M1, 5.0.0.M3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.1.Final, 5.0.0.M4 Per lengthy discussions, I believe the plan is to relabel some features on the JBDS Extras sites for *BOTH 4.x and 5.x* as follows: {code} * Selected * FindBugs Git (5.x version includes eGit, jGit, and Mylyn support for GitHub; 4.x version is just eGit/jGit) Maven/m2e (including wtp integration) Mylyn (incl. connectors for CVS, SVN, Git, GitHub; JIRA support only in 5.x) PMD Subclipse jslint (new for JBDS 5.x) checkstyle (new for JBDS 5.x) * Certified * Spring IDE (per Burr) BPEL Editor (per Mike) TestNG (per Max) {code} To facilitate with this exercise, I've changed the update site index pages to list the features they contain. Here are the latest nightlies for 4.x and 5.x: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-4.1_stable... and http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... (not technically an "Extras" site but listed here in case people wonder where BPEL went) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-1840) Changes to the devstudio.jboss.com/updates/4.0 update site, page

by Burr Sutter (JIRA)

Changes to the devstudio.jboss.com/updates/4.0 update site, page ---------------------------------------------------------------- Key: JBDS-1840 URL: https://issues.jboss.org/browse/JBDS-1840 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Burr Sutter Attachments: devstudio_update_site.png Please remove the phrases "supported", "certified", "selected" and "Unsupported As-is" Replace "Unsupported As-Is" with "Additional" or "Preview" See attached screenshot. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBDS-1853) helloworld_mail quickstart - relies on queue definitioni used by helloworld quickstart - user cannot deploy them both at the same time

by Len DiMaggio (JIRA)

helloworld_mail quickstart - relies on queue definitioni used by helloworld quickstart - user cannot deploy them both at the same time -------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1853 URL: https://issues.jboss.org/browse/JBDS-1853 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.M1 Environment: Version: 4.1.1.GA Build id: v20110908-0132-H1012-GA Build date: 20110908-0132 Reporter: Len DiMaggio Priority: Minor Fix For: 4.1.1.Final The queue is: <jms-provider connection-factory="ConnectionFactory" name="JBossMQ"> <jms-bus busid="quckstartEsbChannel"> <jms-message-filter dest-name="queue/quickstart_helloworld_Request_esb" dest-type="QUEUE"/> </jms-bus> </jms-provider> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDS-1854) helloworld_mail quickstart - client app missing javax.mail jar from build path

by Len DiMaggio (JIRA)

helloworld_mail quickstart - client app missing javax.mail jar from build path ------------------------------------------------------------------------------ Key: JBDS-1854 URL: https://issues.jboss.org/browse/JBDS-1854 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Platform Affects Versions: 4.1.1.M1 Environment: Version: 4.1.1.GA Build id: v20110908-0132-H1012-GA Build date: 20110908-0132 Reporter: Len DiMaggio Fix For: 4.1.1.Final org.jboss.soa.esb.samples.quickstart.helloworld_mail.test.SendMailMessage requires javax.mail for these imports: import javax.mail.Message; import javax.mail.Message.RecipientType; import javax.mail.MessagingException; import javax.mail.PasswordAuthentication; import javax.mail.Session; import javax.mail.Transport; import javax.mail.URLName; import javax.mail.internet.AddressException; import javax.mail.internet.InternetAddress; import javax.mail.internet.MimeMessage; A Java mail jar is not included in the client app. as installed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
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 September 2011