[JBoss JIRA] (WFLY-4779) Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-4779?page=com.atlassian.jira.plugin.... ]
Paul Ferraro updated WFLY-4779:
-------------------------------
Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/812, https://github.com/wildfly/wildfly-core/pull/815)
> Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4779
> URL: https://issues.jboss.org/browse/WFLY-4779
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 9.0.0.CR2, 10.0.0.Alpha2
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 10.0.0.Alpha4
>
>
> Affects at least infinispan aliases and modcluster proxies...
> (20:09:22) rhusar: pferraro: https://gist.github.com/rhusar/5eef22d7a6479f042a5d#file-gistfile1-txt-L23
> (20:09:34) rhusar: pferraro: if i write an empy list, read it back -> empty list
> (20:09:57) rhusar: pferraro: if i use the default writeAttribute, reload, read it back and i have a list of size 1 containing empty String..
> (20:23:23) rhusar: pferraro: alright, this is also "broken" in the infiinispan subsystem aliases
> (20:23:24) rhusar: pferraro: 20:22:55,775 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 40) WFLYCTL0013: Operation ("add") failed - address: ([
> (20:23:24) rhusar: ("subsystem" => "infinispan"),
> (20:23:24) rhusar: ("cache-container" => "hibernate")
> (20:23:24) rhusar: ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for infinispan
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.of(ServiceName.java:90)
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.append(ServiceName.java:117)
> (20:23:24) rhusar: at org.wildfly.clustering.infinispan.spi.service.CacheContainerServiceName$1.getServiceName(CacheContainerServiceName.java:35)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.build(CacheContainerBuilder.java:79)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.installRuntimeServices(CacheContainerAddHandler.java:165)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.performRuntime(CacheContainerAddHandler.java:82)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:309)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:130)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349)
> (20:23:24) rhusar: at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> (20:23:24) rhusar: at java.lang.Thread.run(Thread.java:745)
> (20:23:24) rhusar: at org.jboss.threads.JBossThread.run(JBossThread.java:320)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-2160) Allow Expression for datasource subsystem enabled property
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/WFLY-2160?page=com.atlassian.jira.plugin.... ]
Dimitris Andreadis commented on WFLY-2160:
------------------------------------------
Is this making it to WildFly 10 or not? See linked EAP7-330
> 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
>
> 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
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFCORE-759) Improve encapsulation of logic for handling ordered resource children
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFCORE-759?page=com.atlassian.jira.plugin... ]
Paul Ferraro updated WFCORE-759:
--------------------------------
Description:
Currently, a resource that has ordered child resources needs to define this logic in 3 places:
# The ResourceDefinition needs to indicate that it supports indexed adds (solely for adding the appropriate add-index description) by overwriting SimpleResourceDefinition.isOrderedChildResource()
# The add operation handler of the parent resource needs to override AbstractAddStepHandler.getResourceCreator() to provide an implementation of OrderedResourceCreator that dictates which child types will be ordered
# The add operation handler of the ordered child resource needs to override AbstractAddStepHandler.getResourceCreator() to provide an implementation of OrderedResourceCreator that indicates that the resource supports add-index.
IMO, this seems like poor encapsulation. If we added a ImmutableManagementResourceRegistration.isOrderedChildResource() method, then the AbstractAddStepHandler can query the resource registration to determine whether the current resource supports the add-index parameter, and to see which child types are ordered. This would eliminate the need for subsystems to do #2 and #3 - based solely on the information provided by #1.
Also, indicating this behavior (i.e. #1) via overriding a protected method also seems a little hacky/tacked-on. This method is only read by the SimpleResourceDefinition constructor - which means that this information is more appropriately provided by the constructor. I assume it was done this way since the SimpleResourceDefinition constructors are already overly polluted/complex. Why not instead define this behavior by:
ManagementResourceRegistration.registerOrderedSubModel(ResourceDefinition)
or
ManagementResourceRegistration.registerSubModel(ResourceDefinition).setOrdered(boolean)?
Thoughts?
was:
Currently, a resource that has ordered child resources needs to define this logic in 3 places:
# The ResourceDefinition needs to indicate that it supports indexed adds (solely for adding the appropriate add-index description) by overwriting SimpleResourceDefinition.isOrderedChildResource()
# The add operation handler of the parent resource needs to override AbstractAddStepHandler.getResourceCreator() to provide an implementation of OrderedResourceCreator that dictates which child types will be ordered
# The add operation handler of the ordered child resource needs to override AbstractAddStepHandler.getResourceCreator() to provide an implementation of OrderedResourceCreator that indicates that the resource supports add-index.
IMO, this seems like poor encapsulation. If we added a ImmutableManagementResourceRegistration.isOrderedChildResource() method, then the AbstractAddStepHandler can query the resource registration to determine whether the current resource supports the add-index parameter, and to see which child types are ordered. This would eliminate the need for subsystems to do #2 and #3 - based solely on the information provided by #1.
Also, indicating this behavior (i.e. #1) via overriding a protected method also seems a little hacky/tacked-on. This method is only read by the SimpleResourceDefinition constructor - which means that this information is more appropriately provided by the constructor. I assume it was done this way since the SimpleResourceDefinition constructors are already overly polluted/complex. Why not instead define this behavior by a ManagementResourceRegistration.registerOrderedSubModel(ResourceDefinition) method?
Thoughts?
> Improve encapsulation of logic for handling ordered resource children
> ---------------------------------------------------------------------
>
> Key: WFCORE-759
> URL: https://issues.jboss.org/browse/WFCORE-759
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 2.0.0.Alpha4
> Reporter: Paul Ferraro
> Assignee: Kabir Khan
>
> Currently, a resource that has ordered child resources needs to define this logic in 3 places:
> # The ResourceDefinition needs to indicate that it supports indexed adds (solely for adding the appropriate add-index description) by overwriting SimpleResourceDefinition.isOrderedChildResource()
> # The add operation handler of the parent resource needs to override AbstractAddStepHandler.getResourceCreator() to provide an implementation of OrderedResourceCreator that dictates which child types will be ordered
> # The add operation handler of the ordered child resource needs to override AbstractAddStepHandler.getResourceCreator() to provide an implementation of OrderedResourceCreator that indicates that the resource supports add-index.
> IMO, this seems like poor encapsulation. If we added a ImmutableManagementResourceRegistration.isOrderedChildResource() method, then the AbstractAddStepHandler can query the resource registration to determine whether the current resource supports the add-index parameter, and to see which child types are ordered. This would eliminate the need for subsystems to do #2 and #3 - based solely on the information provided by #1.
> Also, indicating this behavior (i.e. #1) via overriding a protected method also seems a little hacky/tacked-on. This method is only read by the SimpleResourceDefinition constructor - which means that this information is more appropriately provided by the constructor. I assume it was done this way since the SimpleResourceDefinition constructors are already overly polluted/complex. Why not instead define this behavior by:
> ManagementResourceRegistration.registerOrderedSubModel(ResourceDefinition)
> or
> ManagementResourceRegistration.registerSubModel(ResourceDefinition).setOrdered(boolean)?
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-4793) undertow load balancing dont work
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4793?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-4793:
------------------------------
Component/s: Web (Undertow)
(was: Server)
> undertow load balancing dont work
> ---------------------------------
>
> Key: WFLY-4793
> URL: https://issues.jboss.org/browse/WFLY-4793
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.CR1, 9.0.0.CR2
> Environment: Ubuntu 15.04 (x64): Java 1.7.0_79 (x32 and x64) and Java 1.8.0_45 (x32 and x64)
> Windows 7 Ultimate (x64): Java 1.8.0_45 (x32)
> Reporter: Gabriel Gaudina
> Assignee: Jason Greene
> Labels: high_availability, load-balancing, undertow
>
> After configuring two server groups and 3 servers for load balancing (1 balancer, 2 backends) using undertow (without apache mod_cluster), load balancing fails getting "404 - Not Found" or "unable to connect"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-4793) undertow load balancing dont work
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4793?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-4793:
---------------------------------
Assignee: Stuart Douglas (was: Jason Greene)
> undertow load balancing dont work
> ---------------------------------
>
> Key: WFLY-4793
> URL: https://issues.jboss.org/browse/WFLY-4793
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.CR1, 9.0.0.CR2
> Environment: Ubuntu 15.04 (x64): Java 1.7.0_79 (x32 and x64) and Java 1.8.0_45 (x32 and x64)
> Windows 7 Ultimate (x64): Java 1.8.0_45 (x32)
> Reporter: Gabriel Gaudina
> Assignee: Stuart Douglas
> Labels: high_availability, load-balancing, undertow
>
> After configuring two server groups and 3 servers for load balancing (1 balancer, 2 backends) using undertow (without apache mod_cluster), load balancing fails getting "404 - Not Found" or "unable to connect"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFCORE-763) Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-763?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-763:
-----------------------------------------
I was going to ask for a test case, but I like reassigning it to yourself even better!
> Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-763
> URL: https://issues.jboss.org/browse/WFCORE-763
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.Alpha4
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Minor
>
> In short, the default AttributeParser/AttributeMarshaller for list attributes do not handle empty lists in a symmetric fashion.
> e.g. if I persist an empty list to xml, and read it back again, using the default parser/marshaller, I should get back an empty list. Instead I get back a list of size 1 containing an empty string.
> Affects at least infinispan aliases and modcluster proxies...
> (20:09:22) rhusar: pferraro: https://gist.github.com/rhusar/5eef22d7a6479f042a5d#file-gistfile1-txt-L23
> (20:09:34) rhusar: pferraro: if i write an empy list, read it back -> empty list
> (20:09:57) rhusar: pferraro: if i use the default writeAttribute, reload, read it back and i have a list of size 1 containing empty String..
> (20:23:23) rhusar: pferraro: alright, this is also "broken" in the infiinispan subsystem aliases
> (20:23:24) rhusar: pferraro: 20:22:55,775 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 40) WFLYCTL0013: Operation ("add") failed - address: ([
> (20:23:24) rhusar: ("subsystem" => "infinispan"),
> (20:23:24) rhusar: ("cache-container" => "hibernate")
> (20:23:24) rhusar: ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for infinispan
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.of(ServiceName.java:90)
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.append(ServiceName.java:117)
> (20:23:24) rhusar: at org.wildfly.clustering.infinispan.spi.service.CacheContainerServiceName$1.getServiceName(CacheContainerServiceName.java:35)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.build(CacheContainerBuilder.java:79)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.installRuntimeServices(CacheContainerAddHandler.java:165)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.performRuntime(CacheContainerAddHandler.java:82)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:309)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:130)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349)
> (20:23:24) rhusar: at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> (20:23:24) rhusar: at java.lang.Thread.run(Thread.java:745)
> (20:23:24) rhusar: at org.jboss.threads.JBossThread.run(JBossThread.java:320)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-4793) undertow load balancing dont work
by Gabriel Gaudina (JIRA)
Gabriel Gaudina created WFLY-4793:
-------------------------------------
Summary: undertow load balancing dont work
Key: WFLY-4793
URL: https://issues.jboss.org/browse/WFLY-4793
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 9.0.0.CR2, 9.0.0.CR1
Environment: Ubuntu 15.04 (x64): Java 1.7.0_79 (x32 and x64) and Java 1.8.0_45 (x32 and x64)
Windows 7 Ultimate (x64): Java 1.8.0_45 (x32)
Reporter: Gabriel Gaudina
Assignee: Jason Greene
After configuring two server groups and 3 servers for load balancing (1 balancer, 2 backends) using undertow (without apache mod_cluster), load balancing fails getting "404 - Not Found" or "unable to connect"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFCORE-763) Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFCORE-763?page=com.atlassian.jira.plugin... ]
Paul Ferraro reassigned WFCORE-763:
-----------------------------------
Assignee: Paul Ferraro (was: Brian Stansberry)
> Persisting an empty list [] gets read as a list with empty string [""] resulting in IllegalArgumentException
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-763
> URL: https://issues.jboss.org/browse/WFCORE-763
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.Alpha4
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Minor
>
> In short, the default AttributeParser/AttributeMarshaller for list attributes do not handle empty lists in a symmetric fashion.
> e.g. if I persist an empty list to xml, and read it back again, using the default parser/marshaller, I should get back an empty list. Instead I get back a list of size 1 containing an empty string.
> Affects at least infinispan aliases and modcluster proxies...
> (20:09:22) rhusar: pferraro: https://gist.github.com/rhusar/5eef22d7a6479f042a5d#file-gistfile1-txt-L23
> (20:09:34) rhusar: pferraro: if i write an empy list, read it back -> empty list
> (20:09:57) rhusar: pferraro: if i use the default writeAttribute, reload, read it back and i have a list of size 1 containing empty String..
> (20:23:23) rhusar: pferraro: alright, this is also "broken" in the infiinispan subsystem aliases
> (20:23:24) rhusar: pferraro: 20:22:55,775 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 40) WFLYCTL0013: Operation ("add") failed - address: ([
> (20:23:24) rhusar: ("subsystem" => "infinispan"),
> (20:23:24) rhusar: ("cache-container" => "hibernate")
> (20:23:24) rhusar: ]): java.lang.IllegalArgumentException: Empty name segment is not allowed for infinispan
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.of(ServiceName.java:90)
> (20:23:24) rhusar: at org.jboss.msc.service.ServiceName.append(ServiceName.java:117)
> (20:23:24) rhusar: at org.wildfly.clustering.infinispan.spi.service.CacheContainerServiceName$1.getServiceName(CacheContainerServiceName.java:35)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.build(CacheContainerBuilder.java:79)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.installRuntimeServices(CacheContainerAddHandler.java:165)
> (20:23:24) rhusar: at org.jboss.as.clustering.infinispan.subsystem.CacheContainerAddHandler.performRuntime(CacheContainerAddHandler.java:82)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:309)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:130)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:822)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:620)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:373)
> (20:23:24) rhusar: at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:349)
> (20:23:24) rhusar: at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:359)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> (20:23:24) rhusar: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> (20:23:24) rhusar: at java.lang.Thread.run(Thread.java:745)
> (20:23:24) rhusar: at org.jboss.threads.JBossThread.run(JBossThread.java:320)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-4777) Multiple params not working properly in webservices tag
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/WFLY-4777?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on WFLY-4777:
---------------------------------------
AFAICS, the only actual issue here is that we're not supporting expressions for the wsdl-uri-scheme attribute, while we should. So I've provided PRs for fixing that on both 9.x and master branches.
Besides that, there's no real problem: the wsdl-port attribute is not used if you force https uri scheme; instead, the wsdl-secure-port is read in that case. You can specify both wsdl-port and wsdl-secure-port attributes if you want.
> Multiple params not working properly in webservices tag
> -------------------------------------------------------
>
> Key: WFLY-4777
> URL: https://issues.jboss.org/browse/WFLY-4777
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 9.0.0.CR2
> Reporter: John Ament
> Assignee: Alessio Soldano
>
> I configured webservices to use a rewrite of the soap endpoint. The following attributes don't seem to work correctly
> 1. Adding this entry does not work. I need the value for protocol to be configurable
> {code:xml}
> <wsdl-uri-scheme>${wsdl.protocol:http}</wsdl-uri-scheme>
> {code}
> With error
> {quote}
> Message: "WFLYCTL0248: Invalid value $\{wsdl.protocol:http} for wsdl-uri-scheme; legal values are [http, https]"
> {quote}
> 2. wsdl-port is not leveraged properly. I manually changed to https, based on the above limitation. I set this:
> {code:xml}
> <wsdl-uri-scheme>https</wsdl-uri-scheme>
> <wsdl-port>${wsdl.port:443}</wsdl-port>
> {code}
> However, the reported URL includes {{8443}} not my configured {{443}} value.
> In addition, if I manually set the values
> {code:xml}
> <wsdl-uri-scheme>https</wsdl-uri-scheme>
> <wsdl-port>443</wsdl-port>
> {code}
> I still get 8443.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months