[JBoss JIRA] (WFLY-2160) Allow Expression for datasource subsystem enabled property
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-2160?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-2160.
----------------------------
> Allow Expression for datasource subsystem enabled property
> ----------------------------------------------------------
>
> Key: WFLY-2160
> URL: https://issues.jboss.org/browse/WFLY-2160
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 8.0.0.Alpha4
> Reporter: Steven Rose
> Assignee: Stefano Maestri
> Priority: Minor
> Labels: wildfly
> Fix For: 10.0.0.Beta1
>
>
> Currently the datasource sub system does not allow expressions. I would like to be able to do this: <datasource jta="true" jndi-name="java:/ds1DS" pool-name="ds1DS" enabled="${ds1.enabled}" use-java-context="true" use-ccm="true"> and set the ds1.enabled property via a properties file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-5067) Ensure proper WS dependencies order in org.wildfly:wildfly-feature-pack
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5067?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5067.
----------------------------
> Ensure proper WS dependencies order in org.wildfly:wildfly-feature-pack
> -----------------------------------------------------------------------
>
> Key: WFLY-5067
> URL: https://issues.jboss.org/browse/WFLY-5067
> Project: WildFly
> Issue Type: Task
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 10.0.0.Beta1
>
>
> Apache CXF and JBossWS both provide an implementation of javax.xml.ws.spi.Provider, which is basically the entry point for a JAX-WS client API implementation.
> As a consequence, unless endorsing is expected to be used, the JBossWS jars need to come before the Apache CXF ones when defining a flat classpath meant to be used by JAX-WS clients applications.
> Currently, the WildFly integration testsuite relies on a flat classpath derived from the maven dependency tree of org.wildfly:wildfly-feature-pack, which hence need to be properly tuned.
> This is of course not a problem at all in-container on WildFly, as proper module dependencies are already in place and defining the classloaders. Same reasoning applies for those relying on the org,jboss.ws.cxf:jbossws-cxf-client dependency only (as that pulls the whole JBossWS-CXf and Apache CXF dependency tree in the proper order), instead of explicitly declaring single dependencies without allowing transitive dependencies (as it's done in wildfly-feature-pack).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (WFLY-4654) JGroups transport type can't be set
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4654?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4654.
----------------------------
> JGroups transport type can't be set
> -----------------------------------
>
> Key: WFLY-4654
> URL: https://issues.jboss.org/browse/WFLY-4654
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Alpha1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 10.0.0.Alpha3
>
>
> I'm trying to set transport type for JGroups UDP transport. After successful setting via CLI (or model node) and reload, this value is reverted back to undefined.
> [standalone@localhost:9990 transport=UDP] :write-attribute(name="type" ,value="TUNNEL")
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> [standalone@localhost:9990 transport=UDP] ls
> property diagnostics-socket-binding=undefined oob-executor=undefined shared=false thread-factory=undefined
> thread-pool machine=undefined properties=[] site=undefined timer-executor=undefined
> default-executor=undefined module=org.jgroups rack=undefined socket-binding=jgroups-udp type=undefined
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months