[JBoss JIRA] (JBIDE-18039) Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
by Ron Šmeral (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18039?page=com.atlassian.jira.plugi... ]
Ron Šmeral commented on JBIDE-18039:
------------------------------------
OK, I can't reproduce it anymore after cleaning the workspace and the quickstart directory. I'll try to figure out the original conditions.
> Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-18039
> URL: https://issues.jboss.org/browse/JBIDE-18039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Environment: JBDS 8.0.0.Beta3
> Reporter: Ron Šmeral
>
> JBDS currently shows _No bean is eligible for injection to the injection point_ for injection points which are implemented using DeltaSpike's PartialBean extension. This also affects DeltaSpike's Data module, which is based on PartialBean.
> The injection point:
> {code:java|title=QueryServiceTest.java}
> @Inject
> private PersonQueryService personQueryService;
> {code}
> The injected interface:
> {code:java|title=PersonQueryService.java}
> @RequestScoped
> @QueryServiceBinding
> public interface PersonQueryService {
> ...
> {code}
> A partial bean binding annotation:
> {code:java|title=QueryServiceBinding.java}
> @PartialBeanBinding
> @Target(TYPE)
> @Retention(RUNTIME)
> public @interface QueryServiceBinding {
> }
> {code}
> The handler:
> {code:java|title=QueryServicePartialBean.java}
> @RequestScoped
> @QueryServiceBinding
> public class QueryServicePartialBean implements InvocationHandler {
> public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
> ...
> {code}
> There's no implementing class directly in the project, and that's what JBDS is complaining about. The interface is implemented dynamically, using an extension which looks for:
> * interfaces and abstract classes annotated with a partial bean binding
> * invocation handlers which handle calls to methods of those interfaces
> and then adds beans for those interfaces in the ABD phase.
> The same goes for DS Data module's {{@Repository}} ( = a partial bean binding) beans.
> JBDS should not show the no-bean-eligible warning for dynamically implemented interfaces or for DS Data repositories and should instead point to the invocation handler associated with those interfaces through the partial bean binding.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18039) Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
by Ron Šmeral (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18039?page=com.atlassian.jira.plugi... ]
Ron Šmeral updated JBIDE-18039:
-------------------------------
Description:
JBDS currently shows _No bean is eligible for injection to the injection point_ for injection points which are implemented using DeltaSpike's PartialBean extension. This also affects DeltaSpike's Data module, which is based on PartialBean.
The injection point:
{code:java|title=QueryServiceTest.java}
@Inject
private PersonQueryService personQueryService;
{code}
The injected interface:
{code:java|title=PersonQueryService.java}
@RequestScoped
@QueryServiceBinding
public interface PersonQueryService {
...
{code}
A partial bean binding annotation:
{code:java|title=QueryServiceBinding.java}
@PartialBeanBinding
@Target(TYPE)
@Retention(RUNTIME)
public @interface QueryServiceBinding {
}
{code}
The handler:
{code:java|title=QueryServicePartialBean.java}
@RequestScoped
@QueryServiceBinding
public class QueryServicePartialBean implements InvocationHandler {
public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
...
{code}
There's no implementing class directly in the project, and that's what JBDS is complaining about. The interface is implemented dynamically, using an extension which looks for:
* interfaces and abstract classes annotated with a partial bean binding
* invocation handlers which handle calls to methods of those interfaces
and then adds beans for those interfaces in the ABD phase.
The same goes for DS Data module's {{@Repository}} ( = a partial bean binding) beans.
JBDS should not show the no-bean-eligible warning for dynamically implemented interfaces or for DS Data repositories and should instead point to the invocation handler associated with those interfaces through the partial bean binding.
was:
JBDS currently shows _No bean is eligible for injection to the injection point_ for injection points which are implemented using DeltaSpike's PartialBean extension. This also affects DeltaSpike's Data module, which is based on PartialBean.
This can be seen e.g. in the deltaspike-partialbean-advanced quickstart: https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x-devel...
The injection point:
{code:java|title=QueryServiceTest.java}
@Inject
private PersonQueryService personQueryService;
{code}
The injected interface:
{code:java|title=PersonQueryService.java}
@RequestScoped
@QueryServiceBinding
public interface PersonQueryService {
...
{code}
A partial bean binding annotation:
{code:java|title=QueryServiceBinding.java}
@PartialBeanBinding
@Target(TYPE)
@Retention(RUNTIME)
public @interface QueryServiceBinding {
}
{code}
The handler:
{code:java|title=QueryServicePartialBean.java}
@RequestScoped
@QueryServiceBinding
public class QueryServicePartialBean implements InvocationHandler {
public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
...
{code}
There's no implementing class directly in the project, and that's what JBDS is complaining about. The interface is implemented dynamically, using an extension which looks for:
* interfaces and abstract classes annotated with a partial bean binding
* invocation handlers which handle calls to methods of those interfaces
and then adds beans for those interfaces in the ABD phase.
The same goes for DS Data module's {{@Repository}} ( = a partial bean binding) beans.
JBDS should not show the no-bean-eligible warning for dynamically implemented interfaces or for DS Data repositories and should instead point to the invocation handler associated with those interfaces through the partial bean binding.
Steps to Reproduce: Import the deltaspike-partialbean-advanced quickstart: https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x-devel...
> Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-18039
> URL: https://issues.jboss.org/browse/JBIDE-18039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Environment: JBDS 8.0.0.Beta3
> Reporter: Ron Šmeral
>
> JBDS currently shows _No bean is eligible for injection to the injection point_ for injection points which are implemented using DeltaSpike's PartialBean extension. This also affects DeltaSpike's Data module, which is based on PartialBean.
> The injection point:
> {code:java|title=QueryServiceTest.java}
> @Inject
> private PersonQueryService personQueryService;
> {code}
> The injected interface:
> {code:java|title=PersonQueryService.java}
> @RequestScoped
> @QueryServiceBinding
> public interface PersonQueryService {
> ...
> {code}
> A partial bean binding annotation:
> {code:java|title=QueryServiceBinding.java}
> @PartialBeanBinding
> @Target(TYPE)
> @Retention(RUNTIME)
> public @interface QueryServiceBinding {
> }
> {code}
> The handler:
> {code:java|title=QueryServicePartialBean.java}
> @RequestScoped
> @QueryServiceBinding
> public class QueryServicePartialBean implements InvocationHandler {
> public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
> ...
> {code}
> There's no implementing class directly in the project, and that's what JBDS is complaining about. The interface is implemented dynamically, using an extension which looks for:
> * interfaces and abstract classes annotated with a partial bean binding
> * invocation handlers which handle calls to methods of those interfaces
> and then adds beans for those interfaces in the ABD phase.
> The same goes for DS Data module's {{@Repository}} ( = a partial bean binding) beans.
> JBDS should not show the no-bean-eligible warning for dynamically implemented interfaces or for DS Data repositories and should instead point to the invocation handler associated with those interfaces through the partial bean binding.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18039) Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
by Ron Šmeral (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18039?page=com.atlassian.jira.plugi... ]
Ron Šmeral updated JBIDE-18039:
-------------------------------
Issue Type: Bug (was: Feature Request)
I just found JBIDE-13419, therefore changing this from RFE to Bug.
> Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-18039
> URL: https://issues.jboss.org/browse/JBIDE-18039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Environment: JBDS 8.0.0.Beta3
> Reporter: Ron Šmeral
>
> JBDS currently shows _No bean is eligible for injection to the injection point_ for injection points which are implemented using DeltaSpike's PartialBean extension. This also affects DeltaSpike's Data module, which is based on PartialBean.
> This can be seen e.g. in the deltaspike-partialbean-advanced quickstart: https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x-devel...
> The injection point:
> {code:java|title=QueryServiceTest.java}
> @Inject
> private PersonQueryService personQueryService;
> {code}
> The injected interface:
> {code:java|title=PersonQueryService.java}
> @RequestScoped
> @QueryServiceBinding
> public interface PersonQueryService {
> ...
> {code}
> A partial bean binding annotation:
> {code:java|title=QueryServiceBinding.java}
> @PartialBeanBinding
> @Target(TYPE)
> @Retention(RUNTIME)
> public @interface QueryServiceBinding {
> }
> {code}
> The handler:
> {code:java|title=QueryServicePartialBean.java}
> @RequestScoped
> @QueryServiceBinding
> public class QueryServicePartialBean implements InvocationHandler {
> public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
> ...
> {code}
> There's no implementing class directly in the project, and that's what JBDS is complaining about. The interface is implemented dynamically, using an extension which looks for:
> * interfaces and abstract classes annotated with a partial bean binding
> * invocation handlers which handle calls to methods of those interfaces
> and then adds beans for those interfaces in the ABD phase.
> The same goes for DS Data module's {{@Repository}} ( = a partial bean binding) beans.
> JBDS should not show the no-bean-eligible warning for dynamically implemented interfaces or for DS Data repositories and should instead point to the invocation handler associated with those interfaces through the partial bean binding.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18039) Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
by Ron Šmeral (JIRA)
Ron Šmeral created JBIDE-18039:
----------------------------------
Summary: Support DeltaSpike's PartialBean dynamically implemented interfaces and Data repositories
Key: JBIDE-18039
URL: https://issues.jboss.org/browse/JBIDE-18039
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi-extensions
Environment: JBDS 8.0.0.Beta3
Reporter: Ron Šmeral
JBDS currently shows _No bean is eligible for injection to the injection point_ for injection points which are implemented using DeltaSpike's PartialBean extension. This also affects DeltaSpike's Data module, which is based on PartialBean.
This can be seen e.g. in the deltaspike-partialbean-advanced quickstart: https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.x-devel...
The injection point:
{code:java|title=QueryServiceTest.java}
@Inject
private PersonQueryService personQueryService;
{code}
The injected interface:
{code:java|title=PersonQueryService.java}
@RequestScoped
@QueryServiceBinding
public interface PersonQueryService {
...
{code}
A partial bean binding annotation:
{code:java|title=QueryServiceBinding.java}
@PartialBeanBinding
@Target(TYPE)
@Retention(RUNTIME)
public @interface QueryServiceBinding {
}
{code}
The handler:
{code:java|title=QueryServicePartialBean.java}
@RequestScoped
@QueryServiceBinding
public class QueryServicePartialBean implements InvocationHandler {
public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
...
{code}
There's no implementing class directly in the project, and that's what JBDS is complaining about. The interface is implemented dynamically, using an extension which looks for:
* interfaces and abstract classes annotated with a partial bean binding
* invocation handlers which handle calls to methods of those interfaces
and then adds beans for those interfaces in the ABD phase.
The same goes for DS Data module's {{@Repository}} ( = a partial bean binding) beans.
JBDS should not show the no-bean-eligible warning for dynamically implemented interfaces or for DS Data repositories and should instead point to the invocation handler associated with those interfaces through the partial bean binding.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17919) Snapshot wizard: snapshot file name is not refreshed upon changes between full and deployment type
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17919?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-17919:
---------------------------------------
In summary to my IRC chat with [~adietish]:
* The filename should cycle between 'full' and 'deployment' all the time, even when saving an application more then once
* The filename when the snapshot already exists needs to be corrected to place the 'numerical suffice' in the correct location.
> Snapshot wizard: snapshot file name is not refreshed upon changes between full and deployment type
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17919
> URL: https://issues.jboss.org/browse/JBIDE-17919
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: snapshot_wizard
> Fix For: 4.2.0.CR1
>
>
> When trying to create a new snapshot of FULL or DEPLOYMENT type after creating a snapshot earlier, there is no change of file name for the snapshot. It's still the same file name as it was for the snapshot created right before.
> I think there was intention to let user overwrite previously created snapshot. But this brings complications because of snapshot type. We should not override FULL snapshot with DEPLOYMENT snapshot. I think also, that there should not be overriding at all, but it should be distinguished as it is (after workaround) by number of snapshot.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16363) improve the whatsnew section
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16363?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16363.
---------------------------------
> improve the whatsnew section
> ----------------------------
>
> Key: JBIDE-16363
> URL: https://issues.jboss.org/browse/JBIDE-16363
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha2
>
>
> the link to JBT versions should open a new page, not just expand the menu. They could link to the first component in the list of N&N.
> The N&N for a given version (.Alphax, .BetaX, .CRx) could be a single page using Bootstrap scrollspy to track scrolling a provide anchors (ie, URLs) that the users could share.
> For the .Final version, a merge of all N&N per component could be interesting.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16362) Improve the features section
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16362?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-16362.
---------------------------------
> Improve the features section
> ----------------------------
>
> Key: JBIDE-16362
> URL: https://issues.jboss.org/browse/JBIDE-16362
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Alpha2
>
>
> N&N in the /features may be more confusing than anything. Let's just remove them from here and provide all N&N content in the /whatsnew section instead
> Also, reorganize the menu to keep the features order when browsing from one to another (instead of the current model where all other fatures fall into an 'Other Features' section on the left nav menu)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months