[JBoss JIRA] Created: (JBIDE-7969) Empty error message from KB validator
by Max Andersen (JIRA)
Empty error message from KB validator
-------------------------------------
Key: JBIDE-7969
URL: https://issues.jboss.org/browse/JBIDE-7969
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Reporter: Max Andersen
Assignee: Alexey Kazakov
Fix For: 3.2.0.CR1
Not sure what triggered it but got about 10 of these in my error log:
The error message is empty in the error log view; only the stack trace reveals details.
org.eclipse.jface.text.BadLocationException
at org.eclipse.jface.text.ListLineTracker.getLineNumberOfOffset(ListLineTracker.java:140)
at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161)
at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:915)
at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:398)
at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:223)
at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:259)
at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:175)
at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:126)
at org.jboss.tools.jst.web.kb.internal.validation.ValidationErrorManager.addError(ValidationErrorManager.java:140)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1213)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:440)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateAll(CDICoreValidator.java:268)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateAll(ValidatorManager.java:116)
at org.jboss.tools.jst.web.kb.internal.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
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
13 years, 11 months
[JBoss JIRA] (JBIDE-9902) Add support for Seam REST
by Jozef Hartinger (Created) (JIRA)
Add support for Seam REST
-------------------------
Key: JBIDE-9902
URL: https://issues.jboss.org/browse/JBIDE-9902
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: CDI extensions
Affects Versions: 3.3.0.M3
Reporter: Jozef Hartinger
Attachments: client.png
Seam REST provides client integration. When using it, the user specifies an injection point whose type is an interface with no implementation in the deployment. Seam REST dynamically creates producer methods for these injection points in which a proxy for the interface is create, thus avoiding UnsatisfiedResolutionException. See http://docs.jboss.org/seam/3/rest/snapshot/reference/en-US/html/rest.clie... for more details.
The problem with JBoss Tools is that when they validate injection points, the dynamically-registered producer methods are not taken into consideration (obviously). As a result, a user is warned of unsatisfied dependency:
{quote}No bean is eligible for injection to the injection point [JSR-299 §5.2.1]{quote}
Would it be possible to add an exception, so that when a CDI injection point contains the org.jboss.seam.rest.client.RestClient qualifier, it would be considered satisfied if Seam REST is on classpath?
--
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, 11 months
[JBoss JIRA] Created: (JBIDE-9763) CDI Tools should take into account parametrized beans when resolving injection points
by Alexey Kazakov (JIRA)
CDI Tools should take into account parametrized beans when resolving injection points
-------------------------------------------------------------------------------------
Key: JBIDE-9763
URL: https://issues.jboss.org/browse/JBIDE-9763
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: Create a mavenized CDI project.
EXECUTE: Add infinispan jars to it:
{code}
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-core</artifactId>
<version>5.1.0.ALPHA2</version>
</dependency>
<dependency>
<groupId>org.infinispan</groupId>
<artifactId>infinispan-cdi</artifactId>
<version>5.1.0.ALPHA2</version>
</dependency>
{code}
EXECUTE: Create the following bean:
{code}
@Stateless
public class FooEJB {
@Inject
Cache<String, String> defaultCache;
}
{code}
FAILURE: The injection is marked as a problem. It has unsatisfied dependency.
ASSERT: Ctrl+Click on the injection. It should suggest opening org.infinispan.cdi.CacheManager.getAdvancedCache() producer.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months