[JBoss JIRA] Created: (JBIDE-7988) CDI tools model is not updated after quick fix.
by Alexey Kazakov (JIRA)
CDI tools model is not updated after quick fix.
-----------------------------------------------
Key: JBIDE-7988
URL: https://issues.jboss.org/browse/JBIDE-7988
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.0.CR1
1. Create the following class in CDI-enabled project:
class Goose_Broken {
@Inject
public Goose_Broken(String foo) {}
@Inject
public Goose_Broken(String foo, Double bar) {}
}
2. Build the project. There is two error markers on the injections because a bean can have only one constructor annotated @Inject.
3. Double click on any error marker. Select "Delete @Inject annotation from all the constructors but....". Press finish.
4. Now there is the only one @Inject in the class but error markers didn't disappear. It's a problem of CDI model. It still has two @Inject methods. Try to modify the file and Ctrl+S. It helps to get rid of the markers.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7948) Weird errors logged to error log from CDI on closed/reopened projects
by Max Andersen (JIRA)
Weird errors logged to error log from CDI on closed/reopened projects
---------------------------------------------------------------------
Key: JBIDE-7948
URL: https://issues.jboss.org/browse/JBIDE-7948
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Max Andersen
Assignee: Alexey Kazakov
Fix For: 3.2.0.CR1
I imported seam-forge as maven projects; closed the forge-shell project to try and cause a full rebuild to remove validation markers (JBIDE-7946) and I suddenly had a tons of these errors:
Java Model Exception: Java Model Status [forge-shell does not exist]
and when opening the project:
/Users/max/.m2/repository/org/jboss/seam/forge/forge-shell/1.0.0-SNAPSHOT/forge-shell-1.0.0-SNAPSHOT.jar is not on its project's build path
Why are these being logged as errors ? or rather, why is the code being invoked on closed projects and why does it care about that snapshot jar ?
Java Model Exception: Java Model Status [forge-shell does not exist]
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1170)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
at org.eclipse.jdt.internal.core.SourceField.getTypeSignature(SourceField.java:135)
at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:41)
at org.jboss.tools.cdi.internal.core.impl.BeanField.setField(BeanField.java:43)
at org.jboss.tools.cdi.internal.core.impl.BeanField.setDefinition(BeanField.java:30)
at org.jboss.tools.cdi.internal.core.impl.ClassBean.setDefinition(ClassBean.java:99)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1128)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:996)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1000)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:276)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:165)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
null
Error
Sun Dec 19 08:54:54 CET 2010
/Users/max/.m2/repository/org/jboss/seam/forge/forge-shell/1.0.0-SNAPSHOT/forge-shell-1.0.0-SNAPSHOT.jar is not on its project's build path
Java Model Exception: Java Model Status [/Users/max/.m2/repository/org/jboss/seam/forge/forge-shell/1.0.0-SNAPSHOT/forge-shell-1.0.0-SNAPSHOT.jar is not on its project's build path]
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
at org.eclipse.jdt.internal.core.BinaryMethod.getTypeParameterSignatures(BinaryMethod.java:387)
at org.jboss.tools.cdi.internal.core.impl.definition.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:125)
at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:44)
at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setMethod(BeanMethod.java:68)
at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setDefinition(BeanMethod.java:43)
at org.jboss.tools.cdi.internal.core.impl.ClassBean.setDefinition(ClassBean.java:84)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1128)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:996)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1000)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:276)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:165)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7701) Errors when creating and deleting Seam EAR project
by Snjezana Peco (JIRA)
Errors when creating and deleting Seam EAR project
--------------------------------------------------
Key: JBIDE-7701
URL: https://jira.jboss.org/browse/JBIDE-7701
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, Seam
Affects Versions: 3.2.0.Beta2
Environment: Windows XP/Linux, JBT trunk, JBoss AS 5.1.0.GA
Reporter: Snjezana Peco
Assignee: Rob Stryker
Steps to reproduce :
- create the JBoss AS 5.1.0.GA server
- start it
- create a Seam EAR project (test)
The project isn't deployed properly. I have attached the log file (log1.txt).
- restart the server
The project is deployed properly.
- select all the projects and delete them
You will face a few exceptions. Log file attached (log2.txt). The project isn't removed from the server (even if the server is stopped).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBIDE-7548) Deploy from Helios fails for 0.0.0.0
by Andreas Jay (JIRA)
Deploy from Helios fails for 0.0.0.0
------------------------------------
Key: JBIDE-7548
URL: https://jira.jboss.org/browse/JBIDE-7548
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, Seam
Affects Versions: 3.2.0.Beta1
Environment: jboss-5.1.0.GA Server
jboss-seam-2.2.0.GA
Linux 2.6.28-19-generic #61-Ubuntu SMP x86_64 GNU/Linux
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode)
eclipse: Helios Service Release 1
Build id: 20100917-0705
Reporter: Andreas Jay
Assignee: Rob Stryker
Hello,
I have a problem to deploy my seam web project successfully having the jboss exposed to the network via configuration of the server view switching from localhost to 0.0.0.0
This worked perfectly fine with the same project using ganymede. Since I use Helios now this described operation does not work anymore. Setting back to localhost works perfectly fine.
The server boot ends up with this line in the logfile:
14:37:52,175 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 56s:260ms
and stops after this. It does not deploy the web project.
I verified that the same project can be successfully deployed using ganymede and the latest jboss tools version for ganymede and it works to expose to 0.0.0.0
What I tried to make it work on helios:
Created a new server with "New server-> JBoss AS 5.1" etc.
Start eclipse with -clean option
touch descriptors to enforce deployment but it didn`t help. After message "synchroniz...." in IDE nothing happens. Also the logfile does not give any errors.
None of this helped.
Thank you in advance.
A.Jay
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months