Configuration of subsystem webservices - ${jboss.bind.address}

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Configuration of subsystem webservices - ${jboss.bind.address}

Wolf-Dieter Fink
Because of the single point of configuration I would like to have the
<wdsl-host> as a reference to one of the <interfaces> declarations.
Is it possible or a JIRA enhancement?

And for a domain is it a bug?


I found this in 7.1.1.Final (standalone.xml and domain.xml)

<subsystem xmlns="urn:jboss:domain:webservices:1.1">
<modify-wsdl-address>true</modify-wsdl-address>
<wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>

_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Configuration of subsystem webservices - ${jboss.bind.address}

Brian Stansberry
I'd like to see an alternative for this and wsdl-port that uses a
socket-binding reference. IIRC part of the issue with these elements was
the value need not refer to a server socket opened by the AS process
itself; e.g. it could be the hostname/port of a front end load balancer.

However, a reference to an outbound-socket-binding (added in 7.1.0)
could handle that case.

On 3/13/12 3:55 PM, Wolf-Dieter Fink wrote:

> Because of the single point of configuration I would like to have the
> <wdsl-host>  as a reference to one of the<interfaces>  declarations.
> Is it possible or a JIRA enhancement?
>
> And for a domain is it a bug?
>
>
> I found this in 7.1.1.Final (standalone.xml and domain.xml)
>
> <subsystem xmlns="urn:jboss:domain:webservices:1.1">
> <modify-wsdl-address>true</modify-wsdl-address>
> <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
>
> _______________________________________________
> jboss-as7-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev


--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Configuration of subsystem webservices - ${jboss.bind.address}

Alessio Soldano
Hi,
the wsdl-host element value can't be a direct reference to an interface.
That element allows for providing any address, even unrelated to those
you can find in the AS domain. That value is used to tweak the published
wsdl contracts; in some scenarios (eg. JBoss AS living behind a load
balancer or firewall or such), the address specified in there might not
have anything to do with the AS interfaces and be e.g. the public IP of
the infrastructure.
Finally, there's a special value (jbossws.undefined.host) for having the
addresses in wsdls rewritten using the host specified by callers asking
for the wsdl contract. See
https://docs.jboss.org/author/display/AS71/Web+services+configuration

Cheers
Alessio


On 03/14/2012 04:19 PM, Brian Stansberry wrote:

> I'd like to see an alternative for this and wsdl-port that uses a
> socket-binding reference. IIRC part of the issue with these elements was
> the value need not refer to a server socket opened by the AS process
> itself; e.g. it could be the hostname/port of a front end load balancer.
>
> However, a reference to an outbound-socket-binding (added in 7.1.0)
> could handle that case.
>
> On 3/13/12 3:55 PM, Wolf-Dieter Fink wrote:
>> Because of the single point of configuration I would like to have the
>> <wdsl-host>  as a reference to one of the<interfaces>  declarations.
>> Is it possible or a JIRA enhancement?
>>
>> And for a domain is it a bug?
>>
>>
>> I found this in 7.1.1.Final (standalone.xml and domain.xml)
>>
>> <subsystem xmlns="urn:jboss:domain:webservices:1.1">
>> <modify-wsdl-address>true</modify-wsdl-address>
>> <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>


--
Alessio Soldano
Web Service Lead, JBoss
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: Configuration of subsystem webservices - ${jboss.bind.address}

Brian Stansberry
If you haven't seen it, have a look at the <xs:complexType
name="outbound-socket-bindingType"> in jboss-as-config_1_2.xsd. One of
the intended uses cases was for supporting this kind of thing.

TBH, I don't see that as being a huge advantage over what you're doing
now; it would just be more regularized.

The reason I'd like to see an alternative (not replacement) config to
what you have now is for the common case where the desired values are
the address/port of the JBoss Web connector in the AS process. The way
it is now, this can very easily fall out of sync, since setting
jboss.bind.address is just one of many ways to configure the JBoss Web
connector socket.

On 3/14/12 10:34 AM, Alessio Soldano wrote:

> Hi,
> the wsdl-host element value can't be a direct reference to an interface.
> That element allows for providing any address, even unrelated to those
> you can find in the AS domain. That value is used to tweak the published
> wsdl contracts; in some scenarios (eg. JBoss AS living behind a load
> balancer or firewall or such), the address specified in there might not
> have anything to do with the AS interfaces and be e.g. the public IP of
> the infrastructure.
> Finally, there's a special value (jbossws.undefined.host) for having the
> addresses in wsdls rewritten using the host specified by callers asking
> for the wsdl contract. See
> https://docs.jboss.org/author/display/AS71/Web+services+configuration
>
> Cheers
> Alessio
>
>
> On 03/14/2012 04:19 PM, Brian Stansberry wrote:
>> I'd like to see an alternative for this and wsdl-port that uses a
>> socket-binding reference. IIRC part of the issue with these elements was
>> the value need not refer to a server socket opened by the AS process
>> itself; e.g. it could be the hostname/port of a front end load balancer.
>>
>> However, a reference to an outbound-socket-binding (added in 7.1.0)
>> could handle that case.
>>
>> On 3/13/12 3:55 PM, Wolf-Dieter Fink wrote:
>>> Because of the single point of configuration I would like to have the
>>> <wdsl-host>   as a reference to one of the<interfaces>   declarations.
>>> Is it possible or a JIRA enhancement?
>>>
>>> And for a domain is it a bug?
>>>
>>>
>>> I found this in 7.1.1.Final (standalone.xml and domain.xml)
>>>
>>> <subsystem xmlns="urn:jboss:domain:webservices:1.1">
>>> <modify-wsdl-address>true</modify-wsdl-address>
>>> <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>
>


--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev