[JBoss JIRA] Created: (JBIDE-8993) Unable to run DroolTest.java because of missing org.eclipse.jdt.core*.jar in project classpath
by Vlado Pakan (JIRA)
Unable to run DroolTest.java because of missing org.eclipse.jdt.core*.jar in project classpath
----------------------------------------------------------------------------------------------
Key: JBIDE-8993
URL: https://issues.jboss.org/browse/JBIDE-8993
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M1
Environment: Linux 32bit, Sun JDK 1.6_25, jbosstools-3.3.0.M1a.aggregate-Update-2011-05-11_15-56-28-H2359
Reporter: Vlado Pakan
Priority: Critical
Fix For: 3.3.0.M1
When creating new Drools Runtime from Drools plugin bundled to JBT org.eclipse.jdt.core*.jar file is not included in this runtime and therefore when running DroolTest.java this error is displayed in console:
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:277)
at org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:262)
at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:175)
at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:153)
at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:218)
at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:146)
at org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilder(KnowledgeBuilderFactoryServiceImpl.java:34)
at org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilder(KnowledgeBuilderFactory.java:46)
at com.sample.DroolsTest.readKnowledgeBase(DroolsTest.java:39)
at com.sample.DroolsTest.main(DroolsTest.java:23)
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:93)
at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:54)
at org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:273)
... 9 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBIDE-10767) Renaming java element does not force to re-validate related resources
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-10767:
--------------------------------------
Summary: Renaming java element does not force to re-validate related resources
Key: JBIDE-10767
URL: https://issues.jboss.org/browse/JBIDE-10767
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core, jsp/jsf/xml source editing
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta1
1. Create an EAR Seam 2 project
2. Open home.xhtml
3. Add #{authenticator.authenticate()}
4. Save the file
5. Open Authenticator.java
6. Rename Authenticator.authenticate() to authenticateNew() using refactoring.
7. #{authenticator.authenticate()} is refactored to #{authenticator.authenticateNew()}. That's good. But there is a marker now: "authenticate" is not recognized. This is not correct since this EL was updated to #{authenticator.authenticateNew()}.
--
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
12 years
[JBoss JIRA] (JBIDE-10703) Follow common pattern in bundle activator classes
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-10703:
---------------------------------------------
Summary: Follow common pattern in bundle activator classes
Key: JBIDE-10703
URL: https://issues.jboss.org/browse/JBIDE-10703
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: common/jst/core
Affects Versions: 3.3.0.M5
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.Beta1
1. Static instance of plugin implementation should be assigned in constructor, not in start() method.
2. Static instance of plugin implementation should not be set to null in method stop() as it may cause logging NullPointerException at Eclipse shutdown (we already had such issues, mostly reproduced in automatic tests).
3. Extend BaseUIPlugin in plugins that depend on common module.
--
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
12 years
[JBoss JIRA] Created: (JBIDE-9772) Unavailable beans for dependent projects
by Alexey Kazakov (JIRA)
Unavailable beans for dependent projects
----------------------------------------
Key: JBIDE-9772
URL: https://issues.jboss.org/browse/JBIDE-9772
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M3
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M4
EXECUTE: Download/clone and install http://seamframework.org/Seam3/SecurityModule as an existing maven project. Make sure CDI support is enabled for the projects.
EXECUTE: Open /seam-security-external/src/main/java/org/jboss/seam/security/external/openid/OpenIdAuthenticator.java
FAILURE: There is a warning "No bean eligible for the injection point" at
{code}
@Inject
HttpServletResponse response;
{code}
It seems that if we have project A and project B (B depends on A) and project A has a jar which is not in project classpath of project B then beans from this jar is not available for injections of project A.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years