[JBoss JIRA] (WFLY-11157) Remove unused module dependencies on org.jboss.as.threads
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11157?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11157:
---------------------------------
Fix Version/s: 15.0.0.Final
> Remove unused module dependencies on org.jboss.as.threads
> ---------------------------------------------------------
>
> Key: WFLY-11157
> URL: https://issues.jboss.org/browse/WFLY-11157
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JDR, JPA / Hibernate, Web (Undertow)
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> A number of modules depend on org.jboss.as.threads but don't use it.
> {code}
> $ git grep org.jboss.as.threads | grep module.xml
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/clustering/infinispan/main/module.xml: <module name="org.jboss.as.threads"/>
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/connector/main/module.xml: <module name="org.jboss.as.threads"/>
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/ejb3/main/module.xml: <module name="org.jboss.as.threads"/>
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jdr/main/module.xml: <module name="org.jboss.as.threads"/>
> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/jpa/main/module.xml: <module name="org.jboss.as.threads"/>
> feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/batch/jberet/main/module.xml: <module name="org.jboss.as.threads"/>
> servlet-feature-pack/src/main/resources/modules/system/layers/base/org/wildfly/extension/undertow/main/module.xml: <module name="org.jboss.as.threads"/>
> {code}
> The connector, ejb3 and batch-jberet modules actually use org.jboss.as.threads; the others do not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11175) Simplify TransactionManager integration in JMSBridgeService
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11175?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11175:
---------------------------------
Fix Version/s: 15.0.0.Final
> Simplify TransactionManager integration in JMSBridgeService
> -----------------------------------------------------------
>
> Key: WFLY-11175
> URL: https://issues.jboss.org/browse/WFLY-11175
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> JMSBridgeService has an odd static method called from start() where it does an MSC ServiceRegistry lookup to find the TransactionManager service. That would be unreliable if the service had no MSC dependency on the TM service. But JMSBridgeAdd creates such a dependency when it installs the bridge service.
> This whole thing should be converted into a normal service injection.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11125) Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11125?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11125:
---------------------------------
Fix Version/s: 15.0.0.Final
> Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
> -----------------------------------------------------------------------------
>
> Key: WFLY-11125
> URL: https://issues.jboss.org/browse/WFLY-11125
> Project: WildFly
> Issue Type: Enhancement
> Components: CDI / Weld, Security
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> The more optional deps the Weld subsystem module has, the better as it helps allow slimmer runtimes.
> 1) org.jboss.as.security -- classes from this module (SimpleSecurityManager[Service] should only be loaded if the org.wildfly.legacy-security capability is present, so this dep can be optional.
> -2) org.picketbox -- AFAICT these are only used via org.jboss.weld.security.spi.SecurityServices impl methods that are never called. And it seems like they wouldn't be expected to work without the org.wildfly.legacy-security capability being present anyway. So I believe this dep can be optional.-
> (Edited to comment out the second point since a) the SecurityServices methods are indeed called and b) it's not obvious they'd never be expected to be called without the security subsystem. Probably wouldn't work right but it's too complex a task to validate that.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10616) ContextResolver doesn't work
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10616?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10616:
---------------------------------
Fix Version/s: 15.0.0.Final
> ContextResolver doesn't work
> ----------------------------
>
> Key: WFLY-10616
> URL: https://issues.jboss.org/browse/WFLY-10616
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 13.0.0.Final
> Reporter: George Trudeau
> Assignee: R Searls
> Priority: Major
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
> Attachments: test.war
>
>
> I have a simple ContextResolver to set Date serialization format for my JAX-RS service, it works on 12.0.0.Final but it doesn't anymore on 13.0.0.Final :
> {code:java}
> @Provider
> public class DateResolver implements ContextResolver<ObjectMapper>
> {
> private final ObjectMapper mapper;
> public DateResolver()
> {
> mapper = new ObjectMapper();
> mapper.setDateFormat(new SimpleDateFormat("yyyy-MM-dd"));
> mapper.disable(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS);
> }
> @Override
> public ObjectMapper getContext(Class<?> type) { return mapper; }
> }
> {code}
> The {{getContext}} method isn't called on 13.0.0.Final.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months