[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
[JBoss JIRA] (JBIDE-10439) Implement a JAX-RS 'post-reconcile' mechanism
by Xavier Coulon (Created) (JIRA)
Implement a JAX-RS 'post-reconcile' mechanism
----------------------------------------------
Key: JBIDE-10439
URL: https://issues.jboss.org/browse/JBIDE-10439
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Webservices
Affects Versions: 3.3.0.M4
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta1
In its current implementation, the JAX-RS core plugin processes annotation changes in the working copies, assuming that they will all be caught (ie, in 'post-change' events). However, in some situations, changing and then saving a compilation unit just after (ie, saving before the 'post-change' event occurs) can lead to sync' issue, where the java model is saved and the jax-rs did not apply the changes.
To avoid such a situation, a 'post-reconcile' processing should be done, too. This processing should do a kind of a 'clean' analyse of the given compilation unit build the associated JAX-RS elements.
--
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