avalon-phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexis Agahi <a...@users.sourceforge.net>
Subject Re: three improvements to avalon/phoenix
Date Tue, 20 Aug 2002 21:46:43 GMT
Peter Donald wrote:
> On Tue, 20 Aug 2002 00:59, Igor Fedorenko wrote:
>>Not exactly. Soap does not have to be java, so getting "all remote
>>interfaces" of none-java service would be tricky. Of course, one could
>>write a factory that is smart enough to map soap urls into java
>>interfaces, but this sounds like hiding problems instead of solving them.
> If that is the case you could still use the same interface with a slight 
> modification
> <block name="my-block-remote"
>   impl="resource:/my/soap/descriptor.xml"
>   factory="org.apache.avalon.factorys.SoapFactory"> 
> </block>
> And then /my/soap/descriptor.xml would contain all the information you needed 
> to assemble a particular soap service. ie it could contain something like
> <soap>
>   <uri>htts://..."</uri>
>   <wsdl location="..."/>
>   <security-credentials>
>   ...
>   </security-credentials>
> </soap>
> Or whatever is most apporpriate for soap. I expect there is some standard 
> format in which you define a service offering in soap? You could use that or 
> decorate it as appropriate.

Why not using Web Services Description Language?
WSDL4J http://www-124.ibm.com/developerworks/projects/wsdl4j/
provided by http://xml.apache.org/axis/index.html

Web Services Invocation Framework
Web Services Inspection Language

To unsubscribe, e-mail:   <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-phoenix-dev-help@jakarta.apache.org>

View raw message