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
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Alessio Soldano
Web Service Lead, JBoss