[JBoss JIRA] Created: (JBIDE-3878) Seam validator throws NPE for classes which extends binary components.
by Alexey Kazakov (JIRA)
Seam validator throws NPE for classes which extends binary components.
----------------------------------------------------------------------
Key: JBIDE-3878
URL: https://jira.jboss.org/jira/browse/JBIDE-3878
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.GA
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.0.0.GA
EXECUTE: Create Seam Web Project
EXECUTE: Create new class:
import org.jboss.seam.ScopeType;
import org.jboss.seam.annotations.Install;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Observer;
import org.jboss.seam.annotations.Scope;
import org.jboss.seam.annotations.Startup;
import org.jboss.seam.security.Identity;
@Scope(ScopeType.SESSION)
@Install(precedence=Install.APPLICATION)
@Startup
public class MyIdentity extends Identity {
@Observer("myEvent")
public void foo() {}
}
EXECUTE: Ctrl+S
ASSERT: There is an error message on foo method: "Only component class can have @Observer method"
But now there is not such error marker but NPE is thrown:
java.lang.NullPointerException
at org.jboss.tools.seam.internal.core.validation.ValidationErrorManager.addError(ValidationErrorManager.java:119)
at org.jboss.tools.seam.internal.core.validation.ValidationErrorManager.addError(ValidationErrorManager.java:81)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateMethodOfUnknownComponent(SeamCoreValidator.java:725)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validateMethodsOfUnknownComponent(SeamCoreValidator.java:706)
at org.jboss.tools.seam.internal.core.validation.SeamCoreValidator.validate(SeamCoreValidator.java:199)
at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validate(SeamValidatorManager.java:78)
at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:63)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
EXECUTE: Add @Name("org.jboss.seam.security.identity") to MyIdentity, Ctrl+S
ASSERT: There is not any error messsage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-3610) JBDS 2.0.0.CR1 Uses Java 6 when environment only has Java 5
by Aaron Pestel (JIRA)
JBDS 2.0.0.CR1 Uses Java 6 when environment only has Java 5
-----------------------------------------------------------
Key: JBIDE-3610
URL: https://jira.jboss.org/jira/browse/JBIDE-3610
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Environment: JBoss Developer Studio
Version: 2.0.0.CR1
Build id: R200812221144
Build date: 12/22/2008 11:54
Java 1.5.0_16
Reporter: Aaron Pestel
Priority: Minor
I'm quite sure the only JVM I have on my machine is Java 1.5. If I say "which java", "java -version", "$JAVA_HOME/bin/java -version", "$JAVA_HOME/jre/bin/java -version", they are all Java 1.5.0_16. I downloaded the new JBDS 2.0.0.CR1 from the download site and did no configuration to it, just started it by default (what configuration it may have picked up from previous JBDS versions I've run, is something I don't know, but other customers will likely have the same scenario, at least some of them).
When I start JBDS, I've dumped the configuration from Help | About | Configuration, and it's running with a 1.5.0_16 JVM. When I go to create a new server runtime so that I can have a SOA-P 4.3 server, the only JVM available to me is 1.5.0_16. If I look in Eclipse at "Preferences | Java | Installed JREs", the only JRE installed is 1.5.0_16. So, I create my SOA-P 4.3 runtime, create a simple ESB project and deploy it to the SOA-P 4.3 server. Everything works fine until I add a custom Java action to my ESB project. In that case, by default, it compiles the Java class with Java 1.6 (from where, I don't know, maybe a plugin that ships with Eclipse/JBDS?), and the ESB project fails to deploy on the SOA-P server with a class version mismatch exception.
I can change my ESB project preferences to use the Java 5 facet, and everything works fine. I was surprised that I had to change my ESB project preferences from Java 6 to Java 5 when I don't think I even have Java 1.6 installed on my machine and when I'm not even sure if SOA-P 4.3 actually works with Java 1.6.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-3887) Problems with "Validate" action in Package Explorer.
by Aliaksey Nis (JIRA)
Problems with "Validate" action in Package Explorer.
----------------------------------------------------
Key: JBIDE-3887
URL: https://jira.jboss.org/jira/browse/JBIDE-3887
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: WindowsXP SP2
JBoss Tools
Version: 3.0.0.GA
Build id: JBossTools-ALL-win32-3.0.0.GA-N200902260002-H1459
JRE 1.5_08
Reporter: Aliaksey Nis
Priority: Optional
EXECUTE: Create Seam 1.2 war project.
EXECUTE: Go to Window > Preferences > JBoss Tools > Web > Seam. Delete Seam 1.2 runtime, which was used during creation of project.
EXECUTE: Package Explorer. Right click on seam project, select Validate.
ASSERT: Error(Seam runtime not defined) appears in Problems view.
EXECUTE: Right click on seam project, select Properties > Seam settings.
EXECUTE: Add new seam 1.2 runtime with new name(different from previous name) to this project. Press Apply and Ok.
FAILURE: Project didn't rebuild automatically. Error didn't dissappear from Problems View.
EXECUTE: Package Explorer. Right click on seam project, select Validate.
FAILURE: Error didn't dissappear from Problems View after validation.
If "clean workspace" used instead of "Validate" - all work fine. So validate option work strange.
If after runtime deletion "clean workspace" option used instead of "Validate" - then project rebuild automatically after new runtime was added.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month