[JBoss JIRA] (WFLY-7395) Allow to provide deployment dependency to JNDI resource
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-7395?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-7395:
----------------------------------------
[~ehugonnet] FYI re the above discussion.
I kind of doubt we would do what's requested here. We'd need to add a new API library for the annotation (unless I've forgotten one that would suit.) It wouldn't work like @org.jboss.annotation.ejb.Depends which allowed dependencies on mbean services. In AS > 6 the services we provide and their names are internal details. So it would have to be something else. Using a JNDI name is possible and then the server could wire in a dependency on the service backing the binding.
Perhaps the dependency thing could be done, but we'd have to know it actually solves the complete problem. If there's a different solution that's fine.
> Allow to provide deployment dependency to JNDI resource
> -------------------------------------------------------
>
> Key: WFLY-7395
> URL: https://issues.redhat.com/browse/WFLY-7395
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 10.1.0.Final
> Reporter: Miroslav Novak
> Assignee: Brian Stansberry
> Priority: Major
> Labels: user_experience
>
> For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly 10.x
> For example if EJB contains dependency to queue registered in JNDI:
> {code}
> @Resource(mappedName = "java:/jms/queue/OutQueue")
> private Queue outQueue;
> {code}
> then it would not get deployed when OutQueue is not present. Purpose of this feature request is to add possibility to provide such dependency in the way as @org.jboss.annotation.ejb.Depends did.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12379) Discussion of MP compatibility guarantees in WildFly docs
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12379?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-12379:
---------------------------------------
Assignee: (was: Brian Stansberry)
> Discussion of MP compatibility guarantees in WildFly docs
> ---------------------------------------------------------
>
> Key: WFLY-12379
> URL: https://issues.redhat.com/browse/WFLY-12379
> Project: WildFly
> Issue Type: Task
> Components: Documentation
> Reporter: Brian Stansberry
> Priority: Major
>
> The MP specifications innovate more rapidly than EE historically has and the MP community is more willing to accept incompatible changes than EE historically has been. The result is the MP features the WF provides may change in incompatible ways between releases more frequently than typical WF features do. We should have some discussion of this in our documentation.
> * The Admin Guide sections on the various MP subsystems should have some mention of this fact, focused on how output formats may change (if relevant for a spec) or how management API may change if a spec change forces an integration change that in turn requires an incompatible management API change (not expected but possible.)
> * The Developer Guide should have a brief Microprofile section that highlights this fact, but focused on user API and output formats. There can be subsections for the specs we support (where we have useful content) that can provide brief further details; e.g. links to things like the MP Metrics spec changelog.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13360) Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13360:
------------------------------------
Issue Type: Enhancement (was: Bug)
> Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-13360
> URL: https://issues.redhat.com/browse/WFLY-13360
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
> {code}
> EJB 3.2 specification
> 4.9.7 Session Bean’s Business Interface
> - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
> - All business interfaces must be explicitly designated as such if any of the following is true:
> - the bean exposes a no-interface view
> - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
> - using the Local or Remote annotation with a non-empty value on the bean class
> - using the Local or Remote annotation on the interface
> - in the deployment descriptor
> {code}
> If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
> {code}
> public interface I {...}
>
> @Stateless
> public class A implements I {...}
>
> @Stateless
> public class B extends A {...}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13360) Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13360:
-----------------------------------------
AIUI there is no spec violation by WildFly here, just a desire to perhaps be helpful by notifying users of something that may (or may not) be a flaw in their code. So that would be a possible enhancement, not a bug.
> Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-13360
> URL: https://issues.redhat.com/browse/WFLY-13360
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
> {code}
> EJB 3.2 specification
> 4.9.7 Session Bean’s Business Interface
> - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
> - All business interfaces must be explicitly designated as such if any of the following is true:
> - the bean exposes a no-interface view
> - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
> - using the Local or Remote annotation with a non-empty value on the bean class
> - using the Local or Remote annotation on the interface
> - in the deployment descriptor
> {code}
> If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
> {code}
> public interface I {...}
>
> @Stateless
> public class A implements I {...}
>
> @Stateless
> public class B extends A {...}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13360) Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13360:
------------------------------------
Description:
>From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
{code}
EJB 3.2 specification
4.9.7 Session Bean’s Business Interface
- The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
- All business interfaces must be explicitly designated as such if any of the following is true:
- the bean exposes a no-interface view
- any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
- using the Local or Remote annotation with a non-empty value on the bean class
- using the Local or Remote annotation on the interface
- in the deployment descriptor
{code}
If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
{code}
public interface I {...}
@Stateless
public class A implements I {...}
@Stateless
public class B extends A {...}
{code}
was:
>From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
EJB 3.2 specification
4.9.7 Session Bean’s Business Interface
- The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
- All business interfaces must be explicitly designated as such if any of the following is true:
- the bean exposes a no-interface view
- any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
- using the Local or Remote annotation with a non-empty value on the bean class
- using the Local or Remote annotation on the interface
- in the deployment descriptor
If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
public interface I {...}
@Stateless
public class A implements I {...}
@Stateless
public class B extends A {...}
> Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-13360
> URL: https://issues.redhat.com/browse/WFLY-13360
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
> {code}
> EJB 3.2 specification
> 4.9.7 Session Bean’s Business Interface
> - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
> - All business interfaces must be explicitly designated as such if any of the following is true:
> - the bean exposes a no-interface view
> - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
> - using the Local or Remote annotation with a non-empty value on the bean class
> - using the Local or Remote annotation on the interface
> - in the deployment descriptor
> {code}
> If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
> {code}
> public interface I {...}
>
> @Stateless
> public class A implements I {...}
>
> @Stateless
> public class B extends A {...}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12485) Galleon layers for embedded infinispan-based web clustering
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12485?page=com.atlassian.jira.plugi... ]
Brian Stansberry resolved WFLY-12485.
-------------------------------------
Resolution: Out of Date
[~pferraro] Just an FYI in case I missed something. I filed this quite a long time ago and then I think I forgot it existed and we've done various bits other ways, e.g. in WFLY-12507, WFLY-12604, WFLY-12751, all related to web-clustering layer, and then WFLY-13150 for non-clustered web session caching.
So I'm resolving it.
> Galleon layers for embedded infinispan-based web clustering
> -----------------------------------------------------------
>
> Key: WFLY-12485
> URL: https://issues.redhat.com/browse/WFLY-12485
> Project: WildFly
> Issue Type: Enhancement
> Components: Build System, Clustering
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> Make it easier to create configuration profiles supporting web session clustering using in-process infinispan for the caching.
> Web clustering using hotrod is a good thing to do but isn't part of this.
> This is basically a matter of factoring out some of the config chunks Galleon uses to generate our standard configs into separate feature-groups, and then composing those into a layer.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13314) Metrics smallrye contains duplicated help lines
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13314?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13314:
------------------------------------
Priority: Critical (was: Major)
> Metrics smallrye contains duplicated help lines
> -----------------------------------------------
>
> Key: WFLY-13314
> URL: https://issues.redhat.com/browse/WFLY-13314
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 18.0.1.Final
> Reporter: Matthias Depuydt
> Assignee: Jeff Mesnil
> Priority: Critical
>
> The metrics endpoint on which the wildfly microprofile-metrics-smallrye:2.0 subsystem exposes all metrics can't be scraped with prometheus.
> Both the base_gc_time_total & base_gc_total metrics have their help line duplicated which causes prometheus to throw the following error:
> Could not build time series for component wildfly: text format parsing error in line 34: second HELP line for metric name "base_gc_total"
> I have confirmed this is the case for wildfly 18.0.1
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13314) Metrics smallrye contains duplicated help lines
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13314?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-13314:
---------------------------------------
Component/s: MP Metrics
Assignee: Jeff Mesnil (was: Brian Stansberry)
> Metrics smallrye contains duplicated help lines
> -----------------------------------------------
>
> Key: WFLY-13314
> URL: https://issues.redhat.com/browse/WFLY-13314
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 18.0.1.Final
> Reporter: Matthias Depuydt
> Assignee: Jeff Mesnil
> Priority: Major
>
> The metrics endpoint on which the wildfly microprofile-metrics-smallrye:2.0 subsystem exposes all metrics can't be scraped with prometheus.
> Both the base_gc_time_total & base_gc_total metrics have their help line duplicated which causes prometheus to throw the following error:
> Could not build time series for component wildfly: text format parsing error in line 34: second HELP line for metric name "base_gc_total"
> I have confirmed this is the case for wildfly 18.0.1
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years