Pasquale

In order to link Synapse and jUDDI, you need to implement this API:
http://synapse.apache.org/apidocs/org/apache/synapse/registry/Registry.html
http://synapse.apache.org/apidocs/org/apache/synapse/registry/RegistryEntry.html

This implements read-only access to a Registry to read XML data. I
would be happy to help. I think the first thing is to define some
simple usecase like reading an endpoint out of UDDI.

Paul

On Tue, Oct 14, 2008 at 8:43 PM, Pasquale Campitiello
<[EMAIL PROTECTED]> wrote:
> Hi,
> i came back here for another proposal!
>
> Are there some specific documentation about configuration of Synapse as ESB
> and jUDDI?
> Now i'm tryng to create this "connection" for my purposes (publishing,
> importing and almost everything you can do with UDDI registries).
>
> Are there some particular basic problems? Now I'm configuring jUDDI on my PC
> and I'm searching for other documentation.
>
> Thanks
>
> 2008/10/10 Pasquale Campitiello <[EMAIL PROTECTED]>
>
>> Ok Paul. I knew that Synapse is only on console mode and it cannot read the
>> graphical user interface.
>> When I was talking about the grafical interface of Aqualogic Service
>> Registry, I was looking for a way to create a logical connection (obviously
>> by the console) between that UDDI and Synapse.
>> Really, I believe that you understood my problem, indeed you said that
>> "what you are looking for is not yet implemented" ... OK.
>>
>> Thank you very much for information!
>> I will try WSO2 Registry or something else.
>>
>>
>> Pasquale
>>
>>
>> 2008/10/9 Paul Fremantle <[EMAIL PROTECTED]>
>>
>>> Pasquale
>>>
>>> Synapse cannot read the graphical user interface!!!
>>>
>>> All Synapse is doing is looking for XML files at a given URL. It does
>>> HTTP GET URL and then uses that XML file.
>>> I think what you are looking for is not yet implemented.
>>>
>>> Paul
>>>
>>> On Thu, Oct 9, 2008 at 8:26 PM, Pasquale Campitiello
>>> <[EMAIL PROTECTED]> wrote:
>>> > Ok Paul.
>>> >
>>> > Now using UDDI v3 BEA Aqualogic Service Registry I have a grafical
>>> interface
>>> > via-browser with which I can do almost everything with UDDI (read XML,
>>> WSDL,
>>> > configure, publish, import... everthing).
>>> > You said that "if you can read XML files from UDDI using HTTP then the
>>> > SimpleURLRegistry can do that", ok... but how I can tell this in the
>>> Synapse
>>> > XML configuration files?
>>> >
>>> > In the official documentation I tried this tags:
>>> >
>>> > <registry provider="org.apache.synapse.registry.url.SimpleURLRegistry">
>>> >  <parameter
>>> name="root">file:./repository/conf/sample/resources/</parameter>
>>> >  <parameter name="cachableDuration">15000</parameter>
>>> > </registry>
>>> >
>>> > I don't know how to configure them. Now when I start the UDDI v3 BEA
>>> > Aqualogic Service Registry I can access to the console with "
>>> > http://localhost:8080/uddi/web": this link is not necessary in the
>>> > configuration?
>>> >
>>> > Moreover, I don't understand if now with Synapse 1.2 is it possibile to
>>> > publish or import services (ecc.) in external UDDI (like Aqualogic
>>> Service
>>> > Registry).
>>> >
>>> > Pasquale
>>> >
>>> >
>>> > 2008/10/9 Paul Fremantle <[EMAIL PROTECTED]>
>>> >
>>> >> Pasquale
>>> >>
>>> >> We don't have a UDDI Registry client in Synapse, that talks SOAP to
>>> >> the UDDI server. Now UDDIv3 has a HTTP interface (as I understand), so
>>> >> if you can read XML files from UDDI using HTTP then the
>>> >> SimpleURLRegistry can do that. Otherwise, if you want to help write a
>>> >> UDDI client, we can discuss that as an option.
>>> >>
>>> >> Alternatively, the WSO2 Registry (http://wso2.org/projects/registry)
>>> >> is an Apache Licensed HTTP-based Registry/Repository that has been
>>> >> tested with Synapse.
>>> >>
>>> >> Paul
>>> >>
>>> >> On Thu, Oct 9, 2008 at 2:30 PM, Pasquale Campitiello
>>> >> <[EMAIL PROTECTED]> wrote:
>>> >> > Hi,
>>> >> >
>>> >> > for a university study I used BEA Aqualogic Service Bus as ESB and
>>> >> Aqualogic
>>> >> > Service Registry as UDDI registry.
>>> >> >
>>> >> > Now I have to use Apache Synapse as ESB and Aqualogic Service
>>> Registry as
>>> >> > UDDI registry, but I don't understand how to configure Synapse for
>>> this
>>> >> > purpose.
>>> >> > In this official page
>>> >> > http://synapse.apache.org/Synapse_Configuration_Language.html I
>>> could
>>> >> guess
>>> >> > UDDI like ALSR are "remote registry" for Synapse architecture. To
>>> include
>>> >> a
>>> >> > registry I have to modifiy the synapse.xml configuration file adding
>>> >> > something like that:
>>> >> >
>>> >> > <registry
>>> provider="org.apache.synapse.registry.url.SimpleURLRegistry">
>>> >> > <parameter
>>> >> name="root">file:./repository/conf/sample/resources/</parameter>
>>> >> > <parameter name="cachableDuration">15000</parameter>
>>> >> > </registry>
>>> >> >
>>> >> > But I don't understand if and where I have to insert "
>>> >> > http://localhost:8080/uddi/web"; (I think this link is necessary).
>>> >> >
>>> >> > I tried this:
>>> >> >
>>> >> > <registry provider="ALSR">
>>> >> > <parameter name="root" value="http://localhost:8080/uddi/web
>>> >> "></parameter>
>>> >> > </registry>
>>> >> >
>>> >> > But I get no significative results.
>>> >> >
>>> >> > Where can I find documentation?
>>> >> > Someone can help me for this configuration???
>>> >> >
>>> >> > Thanks
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Paul Fremantle
>>> >> Co-Founder and CTO, WSO2
>>> >> Apache Synapse PMC Chair
>>> >> OASIS WS-RX TC Co-chair
>>> >>
>>> >> blog: http://pzf.fremantle.org
>>> >> [EMAIL PROTECTED]
>>> >>
>>> >> "Oxygenating the Web Service Platform", www.wso2.com
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Paul Fremantle
>>> Co-Founder and CTO, WSO2
>>> Apache Synapse PMC Chair
>>> OASIS WS-RX TC Co-chair
>>>
>>> blog: http://pzf.fremantle.org
>>> [EMAIL PROTECTED]
>>>
>>> "Oxygenating the Web Service Platform", www.wso2.com
>>>
>>
>>
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

Reply via email to