Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Paul Fremantle]

Wouldn't it be multi-tenanted if we simply configure the scope and
Registry tenant for each correctly?

Paul

On 12 November 2010 16:05, Hiranya Jayathilaka  wrote:
> Hi Charitha,
>
> On Fri, Nov 12, 2010 at 4:21 PM, Charitha Kankanamge 
> wrote:
>>
>> On Fri, Nov 12, 2010 at 3:03 PM, Senaka Fernando  wrote:
>>>
>>>
>>> On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka 
>>> wrote:


 On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge
  wrote:
>
> Hiranya,
>
> AFAIK, there is no way for tenant admin to configure discovery proxy
> since the setting is in axis2.xml. I think this should be enabled by 
> default
> at the deployment time.

 I was told that this should be done by implementing some interface which
 will populate the tenant AxisConfig at startup.
>>>
>>> Correct, we decided to add this via an extension to the CarbonContext.
>>> Though this seem to work well locally, this was not tested on the EC2
>>> environment. Also, this is only a programmatic approach. Charitha, I wonder
>>> what aspect did you test to conclude that this doesn't work? Because it
>>> might be that the UIs are not properly updated to include these changes.
>>
>> No, Not only UI, but when we created a discovery proxy in ESB referring to
>> http://governance.cloud.private.wso2.com/t/tenant.com/services/DiscoveryProxy,
>> no target services were captured by ESB proxy.
>
> You need to first specify a discovery proxy for the app server. App server
> won't publish services to the proxy unless you do that. The way to specify a
> discovery proxy is by writing some code as Senaka has mentioned. Senaka, can
> you provide some more info on this? I'm also interested to know how it's
> done in Stratos. Do you have any sample code you have written earlier for
> testing?
> Thanks,
> Hiranya
>
>>
>>
>>>
>>> Thanks,
>>> Senaka.


>
> Shankar, Sanjaya, Is this available in current stratos deployments?

 No I don't think so.
 Thanks,
 Hiranya

>
> Regards
> Charitha
>
>
> On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka
>  wrote:
>>
>>
>> On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge
>>  wrote:
>>>
>>> Does not work. Services deployed on app server are not automatically
>>> discovered by governance service. Just tried in private cloud.
>>
>> Is there a discovery proxy configured for the app server?
>> Thanks,
>> Hiranya
>>
>>>
>>> Regards
>>> Charitha
>>>
>>> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera 
>>> wrote:

 no it also support well known address based protocol as well
 (AFAIK),
 should work in EC2. But we should try and see.
 --Srinath

 On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
 wrote:
 > Hi Charitha,
 >
 > I'm not 100% sure whether this works in EC2, since it seems to be
 > using a
 > multi cast protocol. But, it works fine on a ordinary setup.
 >
 > Thanks,
 > Senaka.
 >
 > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge
 > 
 > wrote:
 >>
 >> Hi Folks,
 >>
 >> Is WS-D support in a testable state in Stratos-1.0?
 >>
 >> Regards
 >> Charitha
 >>
 >>
 >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
 >> wrote:
 >>>
 >>>
 >>>
 >>>
 >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka
 >>> 
 >>> wrote:
 
 
  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
  wrote:
 >
 > Where can I find some sample code on how to use this?
 
  The DiscoveryMgtUtils class [1] uses the WS-D client API to
  discover
  endpoints and services. Take a look at the method
  probeDiscoveryProxy or
  resolveService.
  Thanks,
  Hiranya
  [1]
 
  - http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
 
 >>>
 >>> BTW, nice looking code. Its always a pleasure to look at well
 >>> written &
 >>> well commented code :)
 >
 > Azeez
 >
 >
 >
 > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
 > wrote:
 >>
 >> Where is the client library? We can make it part of the
 >> axis2-client
 >> component which we include in webapps.
 >> Azeez
 >>
 >>
 >>
 >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Charitha Kankanamge]

On Fri, Nov 12, 2010 at 4:21 PM, Charitha Kankanamge wrote:

>
> On Fri, Nov 12, 2010 at 3:03 PM, Senaka Fernando  wrote:
>
>>
>>
>> On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka 
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge >> > wrote:
>>>

 Hiranya,

 AFAIK, there is no way for tenant admin to configure discovery proxy
 since the setting is in axis2.xml. I think this should be enabled by 
 default
 at the deployment time.

>>>
>>> I was told that this should be done by implementing some interface which
>>> will populate the tenant AxisConfig at startup.
>>>
>>
>> Correct, we decided to add this via an extension to the CarbonContext.
>> Though this seem to work well locally, this was not tested on the EC2
>> environment. Also, this is only a programmatic approach. Charitha, I wonder
>> what aspect did you test to conclude that this doesn't work? Because it
>> might be that the UIs are not properly updated to include these changes.
>>
>
> No, Not only UI, but when we created a discovery proxy in ESB referring to
> http://governance.cloud.private.wso2.com/t/tenant.com/services/DiscoveryProxy,
> no target services were captured by ESB proxy.
>

And discovery proxy feature in ESB is not multi-tenanted [1]

[1]https://wso2.org/jira/browse/STRATOS-794

>
>
>>
>> Thanks,
>> Senaka.
>>
>>>
>>>

 Shankar, Sanjaya, Is this available in current stratos deployments?

>>>
>>> No I don't think so.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Regards
 Charitha



 On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka >>> > wrote:

>
>
> On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge <
> chari...@wso2.com> wrote:
>
>>
>> Does not work. Services deployed on app server are not automatically
>> discovered by governance service. Just tried in private cloud.
>>
>
> Is there a discovery proxy configured for the app server?
>
> Thanks,
> Hiranya
>
>
>>
>> Regards
>> Charitha
>>
>>
>> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera wrote:
>>
>>> no it also support well known address based protocol as well (AFAIK),
>>> should work in EC2. But we should try and see.
>>> --Srinath
>>>
>>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
>>> wrote:
>>> > Hi Charitha,
>>> >
>>> > I'm not 100% sure whether this works in EC2, since it seems to be
>>> using a
>>> > multi cast protocol. But, it works fine on a ordinary setup.
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >
>>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge <
>>> chari...@wso2.com>
>>> > wrote:
>>> >>
>>> >> Hi Folks,
>>> >>
>>> >> Is WS-D support in a testable state in Stratos-1.0?
>>> >>
>>> >> Regards
>>> >> Charitha
>>> >>
>>> >>
>>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
>>> wrote:
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com>
>>> >>> wrote:
>>> 
>>> 
>>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
>>> wrote:
>>> >
>>> > Where can I find some sample code on how to use this?
>>> 
>>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to
>>> discover
>>>  endpoints and services. Take a look at the method
>>> probeDiscoveryProxy or
>>>  resolveService.
>>>  Thanks,
>>>  Hiranya
>>>  [1]
>>>  -
>>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>>> 
>>> >>>
>>> >>> BTW, nice looking code. Its always a pleasure to look at well
>>> written &
>>> >>> well commented code :)
>>> >
>>> > Azeez
>>> >
>>> >
>>> >
>>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
>>> wrote:
>>> >>
>>> >> Where is the client library? We can make it part of the
>>> axis2-client
>>> >> component which we include in webapps.
>>> >> Azeez
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>>> >>  wrote:
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez <
>>> az...@wso2.com>
>>> >>> wrote:
>>> 
>>>  Yes we can do that. So the endpoints have to be published
>>> into the
>>>  tenants' Governace registry space. Adding parameters to
>>> tenants' AxisConfig
>>>  can be done by providing an implementation of
>>> 
>>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
>>> adding
>>>  the par

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Charitha Kankanamge]

On Fri, Nov 12, 2010 at 3:03 PM, Senaka Fernando  wrote:

>
>
> On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge 
>> wrote:
>>
>>>
>>> Hiranya,
>>>
>>> AFAIK, there is no way for tenant admin to configure discovery proxy
>>> since the setting is in axis2.xml. I think this should be enabled by default
>>> at the deployment time.
>>>
>>
>> I was told that this should be done by implementing some interface which
>> will populate the tenant AxisConfig at startup.
>>
>
> Correct, we decided to add this via an extension to the CarbonContext.
> Though this seem to work well locally, this was not tested on the EC2
> environment. Also, this is only a programmatic approach. Charitha, I wonder
> what aspect did you test to conclude that this doesn't work? Because it
> might be that the UIs are not properly updated to include these changes.
>

No, Not only UI, but when we created a discovery proxy in ESB referring to
http://governance.cloud.private.wso2.com/t/tenant.com/services/DiscoveryProxy,
no target services were captured by ESB proxy.


>
> Thanks,
> Senaka.
>
>>
>>
>>>
>>> Shankar, Sanjaya, Is this available in current stratos deployments?
>>>
>>
>> No I don't think so.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Regards
>>> Charitha
>>>
>>>
>>>
>>> On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge <
 chari...@wso2.com> wrote:

>
> Does not work. Services deployed on app server are not automatically
> discovered by governance service. Just tried in private cloud.
>

 Is there a discovery proxy configured for the app server?

 Thanks,
 Hiranya


>
> Regards
> Charitha
>
>
> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera wrote:
>
>> no it also support well known address based protocol as well (AFAIK),
>> should work in EC2. But we should try and see.
>> --Srinath
>>
>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
>> wrote:
>> > Hi Charitha,
>> >
>> > I'm not 100% sure whether this works in EC2, since it seems to be
>> using a
>> > multi cast protocol. But, it works fine on a ordinary setup.
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge <
>> chari...@wso2.com>
>> > wrote:
>> >>
>> >> Hi Folks,
>> >>
>> >> Is WS-D support in a testable state in Stratos-1.0?
>> >>
>> >> Regards
>> >> Charitha
>> >>
>> >>
>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
>> wrote:
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka <
>> hira...@wso2.com>
>> >>> wrote:
>> 
>> 
>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
>> wrote:
>> >
>> > Where can I find some sample code on how to use this?
>> 
>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to
>> discover
>>  endpoints and services. Take a look at the method
>> probeDiscoveryProxy or
>>  resolveService.
>>  Thanks,
>>  Hiranya
>>  [1]
>>  -
>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>> 
>> >>>
>> >>> BTW, nice looking code. Its always a pleasure to look at well
>> written &
>> >>> well commented code :)
>> >
>> > Azeez
>> >
>> >
>> >
>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
>> wrote:
>> >>
>> >> Where is the client library? We can make it part of the
>> axis2-client
>> >> component which we include in webapps.
>> >> Azeez
>> >>
>> >>
>> >>
>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>> >>  wrote:
>> >>>
>> >>>
>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez <
>> az...@wso2.com>
>> >>> wrote:
>> 
>>  Yes we can do that. So the endpoints have to be published
>> into the
>>  tenants' Governace registry space. Adding parameters to
>> tenants' AxisConfig
>>  can be done by providing an implementation of
>> 
>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
>> adding
>>  the parameter in the createdAxisConfiguration method.
>>  So, going back to our sample,
>>  1. How does the portal webapp find the service endpoints of
>> the
>>  Product & Purchasing proxy services?
>> >>>
>> >>> The webapp should use the WS-D client API to discover the
>> necessary
>> >>> endpoin

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Senaka Fernando]

On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka wrote:

>
>
> On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge 
> wrote:
>
>>
>> Hiranya,
>>
>> AFAIK, there is no way for tenant admin to configure discovery proxy since
>> the setting is in axis2.xml. I think this should be enabled by default at
>> the deployment time.
>>
>
> I was told that this should be done by implementing some interface which
> will populate the tenant AxisConfig at startup.
>

Correct, we decided to add this via an extension to the CarbonContext.
Though this seem to work well locally, this was not tested on the EC2
environment. Also, this is only a programmatic approach. Charitha, I wonder
what aspect did you test to conclude that this doesn't work? Because it
might be that the UIs are not properly updated to include these changes.

Thanks,
Senaka.

>
>
>>
>> Shankar, Sanjaya, Is this available in current stratos deployments?
>>
>
> No I don't think so.
>
> Thanks,
> Hiranya
>
>
>>
>> Regards
>> Charitha
>>
>>
>>
>> On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge >> > wrote:
>>>

 Does not work. Services deployed on app server are not automatically
 discovered by governance service. Just tried in private cloud.

>>>
>>> Is there a discovery proxy configured for the app server?
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Regards
 Charitha


 On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera wrote:

> no it also support well known address based protocol as well (AFAIK),
> should work in EC2. But we should try and see.
> --Srinath
>
> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
> wrote:
> > Hi Charitha,
> >
> > I'm not 100% sure whether this works in EC2, since it seems to be
> using a
> > multi cast protocol. But, it works fine on a ordinary setup.
> >
> > Thanks,
> > Senaka.
> >
> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge <
> chari...@wso2.com>
> > wrote:
> >>
> >> Hi Folks,
> >>
> >> Is WS-D support in a testable state in Stratos-1.0?
> >>
> >> Regards
> >> Charitha
> >>
> >>
> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
> wrote:
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka <
> hira...@wso2.com>
> >>> wrote:
> 
> 
>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
> wrote:
> >
> > Where can I find some sample code on how to use this?
> 
>  The DiscoveryMgtUtils class [1] uses the WS-D client API to
> discover
>  endpoints and services. Take a look at the method
> probeDiscoveryProxy or
>  resolveService.
>  Thanks,
>  Hiranya
>  [1]
>  -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
> 
> >>>
> >>> BTW, nice looking code. Its always a pleasure to look at well
> written &
> >>> well commented code :)
> >
> > Azeez
> >
> >
> >
> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
> wrote:
> >>
> >> Where is the client library? We can make it part of the
> axis2-client
> >> component which we include in webapps.
> >> Azeez
> >>
> >>
> >>
> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
> >>  wrote:
> >>>
> >>>
> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  >
> >>> wrote:
> 
>  Yes we can do that. So the endpoints have to be published into
> the
>  tenants' Governace registry space. Adding parameters to
> tenants' AxisConfig
>  can be done by providing an implementation of
> 
> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
> adding
>  the parameter in the createdAxisConfiguration method.
>  So, going back to our sample,
>  1. How does the portal webapp find the service endpoints of
> the
>  Product & Purchasing proxy services?
> >>>
> >>> The webapp should use the WS-D client API to discover the
> necessary
> >>> endpoints
> >>>
> 
>  2. How does the ESB task find out the endpoint of the BPEL
> service?
> >>>
> >>> Task implementation should also use the WS-D client API. Since
> tasks
> >>> are custom developed Java code, we cannot make WS-D support
> tasks. Instead,
> >>> tasks should be written in a WS-D aware manner.
> >>>
> 
>  3. How does the ESB find out the endpoint of the
> Fi

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Charitha Kankanamge]

Sometime back, I have written a blog post about how to configure WS-D [1].

[1]http://charithaka.blogspot.com/2010/04/ws-discovery-with-wso2-carbon.html

Regards
Charitha

On Fri, Nov 12, 2010 at 12:24 PM, Srinath Perera  wrote:

> do we have a OT article, KB entry, or some doc explaining how setup
> ws-discovery? if not, We should do that  when possible.
> --Srinath
>
> On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka 
> wrote:
> >
> >
> > On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge  >
> > wrote:
> >>
> >> Does not work. Services deployed on app server are not automatically
> >> discovered by governance service. Just tried in private cloud.
> >
> > Is there a discovery proxy configured for the app server?
> > Thanks,
> > Hiranya
> >
> >>
> >> Regards
> >> Charitha
> >>
> >> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera 
> wrote:
> >>>
> >>> no it also support well known address based protocol as well (AFAIK),
> >>> should work in EC2. But we should try and see.
> >>> --Srinath
> >>>
> >>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
> wrote:
> >>> > Hi Charitha,
> >>> >
> >>> > I'm not 100% sure whether this works in EC2, since it seems to be
> using
> >>> > a
> >>> > multi cast protocol. But, it works fine on a ordinary setup.
> >>> >
> >>> > Thanks,
> >>> > Senaka.
> >>> >
> >>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge
> >>> > 
> >>> > wrote:
> >>> >>
> >>> >> Hi Folks,
> >>> >>
> >>> >> Is WS-D support in a testable state in Stratos-1.0?
> >>> >>
> >>> >> Regards
> >>> >> Charitha
> >>> >>
> >>> >>
> >>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
> wrote:
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka
> >>> >>> 
> >>> >>> wrote:
> >>> 
> >>> 
> >>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
> >>>  wrote:
> >>> >
> >>> > Where can I find some sample code on how to use this?
> >>> 
> >>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to
> discover
> >>>  endpoints and services. Take a look at the method
> >>>  probeDiscoveryProxy or
> >>>  resolveService.
> >>>  Thanks,
> >>>  Hiranya
> >>>  [1]
> >>> 
> >>>  -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
> >>> 
> >>> >>>
> >>> >>> BTW, nice looking code. Its always a pleasure to look at well
> written
> >>> >>> &
> >>> >>> well commented code :)
> >>> >
> >>> > Azeez
> >>> >
> >>> >
> >>> >
> >>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
> >>> > wrote:
> >>> >>
> >>> >> Where is the client library? We can make it part of the
> >>> >> axis2-client
> >>> >> component which we include in webapps.
> >>> >> Azeez
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
> >>> >>  wrote:
> >>> >>>
> >>> >>>
> >>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  >
> >>> >>> wrote:
> >>> 
> >>>  Yes we can do that. So the endpoints have to be published into
> >>>  the
> >>>  tenants' Governace registry space. Adding parameters to
> tenants'
> >>>  AxisConfig
> >>>  can be done by providing an implementation of
> >>> 
> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver
> >>>  and adding
> >>>  the parameter in the createdAxisConfiguration method.
> >>>  So, going back to our sample,
> >>>  1. How does the portal webapp find the service endpoints of
> the
> >>>  Product & Purchasing proxy services?
> >>> >>>
> >>> >>> The webapp should use the WS-D client API to discover the
> >>> >>> necessary
> >>> >>> endpoints
> >>> >>>
> >>> 
> >>>  2. How does the ESB task find out the endpoint of the BPEL
> >>>  service?
> >>> >>>
> >>> >>> Task implementation should also use the WS-D client API. Since
> >>> >>> tasks
> >>> >>> are custom developed Java code, we cannot make WS-D support
> >>> >>> tasks. Instead,
> >>> >>> tasks should be written in a WS-D aware manner.
> >>> >>>
> >>> 
> >>>  3. How does the ESB find out the endpoint of the
> >>>  FinanceConnector
> >>>  service?
> >>> >>>
> >>> >>> ESB UI provides the necessary means to discover endpoints and
> >>> >>> create
> >>> >>> proxy services on them
> >>> >>>
> >>> 
> >>>  4. How do the Gadgets find out the endpoints of the
> ShoppingCart
> >>>  data service?
> >>> >>>
> >>> >>> We don't support WS-D in gadgets yet. This is something I
> >>> >>> discussed
> >>> >>> with Jonathan a few weeks back. We should be able to discover
> >>> >>> gadgets using
> >>> >>> WS-D and gadgets should be able to discover other en

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Fri, Nov 12, 2010 at 12:24 PM, Srinath Perera  wrote:

> do we have a OT article, KB entry, or some doc explaining how setup
> ws-discovery? if not, We should do that  when possible.
>

I'm working on one. Will take some time to finish though.

Thanks,
Hiranya


> --Srinath
>
> On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka 
> wrote:
> >
> >
> > On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge  >
> > wrote:
> >>
> >> Does not work. Services deployed on app server are not automatically
> >> discovered by governance service. Just tried in private cloud.
> >
> > Is there a discovery proxy configured for the app server?
> > Thanks,
> > Hiranya
> >
> >>
> >> Regards
> >> Charitha
> >>
> >> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera 
> wrote:
> >>>
> >>> no it also support well known address based protocol as well (AFAIK),
> >>> should work in EC2. But we should try and see.
> >>> --Srinath
> >>>
> >>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
> wrote:
> >>> > Hi Charitha,
> >>> >
> >>> > I'm not 100% sure whether this works in EC2, since it seems to be
> using
> >>> > a
> >>> > multi cast protocol. But, it works fine on a ordinary setup.
> >>> >
> >>> > Thanks,
> >>> > Senaka.
> >>> >
> >>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge
> >>> > 
> >>> > wrote:
> >>> >>
> >>> >> Hi Folks,
> >>> >>
> >>> >> Is WS-D support in a testable state in Stratos-1.0?
> >>> >>
> >>> >> Regards
> >>> >> Charitha
> >>> >>
> >>> >>
> >>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
> wrote:
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>>
> >>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka
> >>> >>> 
> >>> >>> wrote:
> >>> 
> >>> 
> >>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
> >>>  wrote:
> >>> >
> >>> > Where can I find some sample code on how to use this?
> >>> 
> >>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to
> discover
> >>>  endpoints and services. Take a look at the method
> >>>  probeDiscoveryProxy or
> >>>  resolveService.
> >>>  Thanks,
> >>>  Hiranya
> >>>  [1]
> >>> 
> >>>  -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
> >>> 
> >>> >>>
> >>> >>> BTW, nice looking code. Its always a pleasure to look at well
> written
> >>> >>> &
> >>> >>> well commented code :)
> >>> >
> >>> > Azeez
> >>> >
> >>> >
> >>> >
> >>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
> >>> > wrote:
> >>> >>
> >>> >> Where is the client library? We can make it part of the
> >>> >> axis2-client
> >>> >> component which we include in webapps.
> >>> >> Azeez
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
> >>> >>  wrote:
> >>> >>>
> >>> >>>
> >>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  >
> >>> >>> wrote:
> >>> 
> >>>  Yes we can do that. So the endpoints have to be published into
> >>>  the
> >>>  tenants' Governace registry space. Adding parameters to
> tenants'
> >>>  AxisConfig
> >>>  can be done by providing an implementation of
> >>> 
> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver
> >>>  and adding
> >>>  the parameter in the createdAxisConfiguration method.
> >>>  So, going back to our sample,
> >>>  1. How does the portal webapp find the service endpoints of
> the
> >>>  Product & Purchasing proxy services?
> >>> >>>
> >>> >>> The webapp should use the WS-D client API to discover the
> >>> >>> necessary
> >>> >>> endpoints
> >>> >>>
> >>> 
> >>>  2. How does the ESB task find out the endpoint of the BPEL
> >>>  service?
> >>> >>>
> >>> >>> Task implementation should also use the WS-D client API. Since
> >>> >>> tasks
> >>> >>> are custom developed Java code, we cannot make WS-D support
> >>> >>> tasks. Instead,
> >>> >>> tasks should be written in a WS-D aware manner.
> >>> >>>
> >>> 
> >>>  3. How does the ESB find out the endpoint of the
> >>>  FinanceConnector
> >>>  service?
> >>> >>>
> >>> >>> ESB UI provides the necessary means to discover endpoints and
> >>> >>> create
> >>> >>> proxy services on them
> >>> >>>
> >>> 
> >>>  4. How do the Gadgets find out the endpoints of the
> ShoppingCart
> >>>  data service?
> >>> >>>
> >>> >>> We don't support WS-D in gadgets yet. This is something I
> >>> >>> discussed
> >>> >>> with Jonathan a few weeks back. We should be able to discover
> >>> >>> gadgets using
> >>> >>> WS-D and gadgets should be able to discover other endpoints and
> >>> >>> gadgets
> >>> >>> using WS-D. We'll probably have to write som

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge wrote:

>
> Hiranya,
>
> AFAIK, there is no way for tenant admin to configure discovery proxy since
> the setting is in axis2.xml. I think this should be enabled by default at
> the deployment time.
>

I was told that this should be done by implementing some interface which
will populate the tenant AxisConfig at startup.


>
> Shankar, Sanjaya, Is this available in current stratos deployments?
>

No I don't think so.

Thanks,
Hiranya


>
> Regards
> Charitha
>
>
>
> On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge 
>> wrote:
>>
>>>
>>> Does not work. Services deployed on app server are not automatically
>>> discovered by governance service. Just tried in private cloud.
>>>
>>
>> Is there a discovery proxy configured for the app server?
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Regards
>>> Charitha
>>>
>>>
>>> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera wrote:
>>>
 no it also support well known address based protocol as well (AFAIK),
 should work in EC2. But we should try and see.
 --Srinath

 On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
 wrote:
 > Hi Charitha,
 >
 > I'm not 100% sure whether this works in EC2, since it seems to be
 using a
 > multi cast protocol. But, it works fine on a ordinary setup.
 >
 > Thanks,
 > Senaka.
 >
 > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge <
 chari...@wso2.com>
 > wrote:
 >>
 >> Hi Folks,
 >>
 >> Is WS-D support in a testable state in Stratos-1.0?
 >>
 >> Regards
 >> Charitha
 >>
 >>
 >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez 
 wrote:
 >>>
 >>>
 >>>
 >>>
 >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka <
 hira...@wso2.com>
 >>> wrote:
 
 
  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
 wrote:
 >
 > Where can I find some sample code on how to use this?
 
  The DiscoveryMgtUtils class [1] uses the WS-D client API to
 discover
  endpoints and services. Take a look at the method
 probeDiscoveryProxy or
  resolveService.
  Thanks,
  Hiranya
  [1]
  -
 http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
 
 >>>
 >>> BTW, nice looking code. Its always a pleasure to look at well
 written &
 >>> well commented code :)
 >
 > Azeez
 >
 >
 >
 > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
 wrote:
 >>
 >> Where is the client library? We can make it part of the
 axis2-client
 >> component which we include in webapps.
 >> Azeez
 >>
 >>
 >>
 >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
 >>  wrote:
 >>>
 >>>
 >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez 
 >>> wrote:
 
  Yes we can do that. So the endpoints have to be published into
 the
  tenants' Governace registry space. Adding parameters to
 tenants' AxisConfig
  can be done by providing an implementation of
 
 the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
  the parameter in the createdAxisConfiguration method.
  So, going back to our sample,
  1. How does the portal webapp find the service endpoints of the
  Product & Purchasing proxy services?
 >>>
 >>> The webapp should use the WS-D client API to discover the
 necessary
 >>> endpoints
 >>>
 
  2. How does the ESB task find out the endpoint of the BPEL
 service?
 >>>
 >>> Task implementation should also use the WS-D client API. Since
 tasks
 >>> are custom developed Java code, we cannot make WS-D support
 tasks. Instead,
 >>> tasks should be written in a WS-D aware manner.
 >>>
 
  3. How does the ESB find out the endpoint of the
 FinanceConnector
  service?
 >>>
 >>> ESB UI provides the necessary means to discover endpoints and
 create
 >>> proxy services on them
 >>>
 
  4. How do the Gadgets find out the endpoints of the
 ShoppingCart
  data service?
 >>>
 >>> We don't support WS-D in gadgets yet. This is something I
 discussed
 >>> with Jonathan a few weeks back. We should be able to discover
 gadgets using
 >>> WS-D and gadgets should be able to discover other endpoints and
 gadgets
 >>> using WS-D. We'll probably have to w

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Charitha Kankanamge]

Hiranya,

AFAIK, there is no way for tenant admin to configure discovery proxy since
the setting is in axis2.xml. I think this should be enabled by default at
the deployment time.

Shankar, Sanjaya, Is this available in current stratos deployments?

Regards
Charitha


On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka wrote:

>
>
> On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge 
> wrote:
>
>>
>> Does not work. Services deployed on app server are not automatically
>> discovered by governance service. Just tried in private cloud.
>>
>
> Is there a discovery proxy configured for the app server?
>
> Thanks,
> Hiranya
>
>
>>
>> Regards
>> Charitha
>>
>>
>> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera  wrote:
>>
>>> no it also support well known address based protocol as well (AFAIK),
>>> should work in EC2. But we should try and see.
>>> --Srinath
>>>
>>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando 
>>> wrote:
>>> > Hi Charitha,
>>> >
>>> > I'm not 100% sure whether this works in EC2, since it seems to be using
>>> a
>>> > multi cast protocol. But, it works fine on a ordinary setup.
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >
>>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge <
>>> chari...@wso2.com>
>>> > wrote:
>>> >>
>>> >> Hi Folks,
>>> >>
>>> >> Is WS-D support in a testable state in Stratos-1.0?
>>> >>
>>> >> Regards
>>> >> Charitha
>>> >>
>>> >>
>>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com>
>>> >>> wrote:
>>> 
>>> 
>>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
>>> wrote:
>>> >
>>> > Where can I find some sample code on how to use this?
>>> 
>>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>>>  endpoints and services. Take a look at the method
>>> probeDiscoveryProxy or
>>>  resolveService.
>>>  Thanks,
>>>  Hiranya
>>>  [1]
>>>  -
>>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>>> 
>>> >>>
>>> >>> BTW, nice looking code. Its always a pleasure to look at well written
>>> &
>>> >>> well commented code :)
>>> >
>>> > Azeez
>>> >
>>> >
>>> >
>>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
>>> wrote:
>>> >>
>>> >> Where is the client library? We can make it part of the
>>> axis2-client
>>> >> component which we include in webapps.
>>> >> Azeez
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>>> >>  wrote:
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez 
>>> >>> wrote:
>>> 
>>>  Yes we can do that. So the endpoints have to be published into
>>> the
>>>  tenants' Governace registry space. Adding parameters to tenants'
>>> AxisConfig
>>>  can be done by providing an implementation of
>>>  the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver
>>> and adding
>>>  the parameter in the createdAxisConfiguration method.
>>>  So, going back to our sample,
>>>  1. How does the portal webapp find the service endpoints of the
>>>  Product & Purchasing proxy services?
>>> >>>
>>> >>> The webapp should use the WS-D client API to discover the
>>> necessary
>>> >>> endpoints
>>> >>>
>>> 
>>>  2. How does the ESB task find out the endpoint of the BPEL
>>> service?
>>> >>>
>>> >>> Task implementation should also use the WS-D client API. Since
>>> tasks
>>> >>> are custom developed Java code, we cannot make WS-D support
>>> tasks. Instead,
>>> >>> tasks should be written in a WS-D aware manner.
>>> >>>
>>> 
>>>  3. How does the ESB find out the endpoint of the
>>> FinanceConnector
>>>  service?
>>> >>>
>>> >>> ESB UI provides the necessary means to discover endpoints and
>>> create
>>> >>> proxy services on them
>>> >>>
>>> 
>>>  4. How do the Gadgets find out the endpoints of the ShoppingCart
>>>  data service?
>>> >>>
>>> >>> We don't support WS-D in gadgets yet. This is something I
>>> discussed
>>> >>> with Jonathan a few weeks back. We should be able to discover
>>> gadgets using
>>> >>> WS-D and gadgets should be able to discover other endpoints and
>>> gadgets
>>> >>> using WS-D. We'll probably have to write some JavaScript library
>>> wrapping
>>> >>> the WS-D client API. Anyway this is for the future. I need to
>>> talk this
>>> >>> through with the GS team.
>>> >>>
>>> 
>>>  5. How does the BPEL process find out the endpoints of
>>>  the ShoppingCart data service?
>>> >>>
>>> >>> We don't support BPEL yet either. And to be honest I'm not very
>>> >>> familiar with

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Srinath Perera]

do we have a OT article, KB entry, or some doc explaining how setup
ws-discovery? if not, We should do that  when possible.
--Srinath

On Fri, Nov 12, 2010 at 11:54 AM, Hiranya Jayathilaka  wrote:
>
>
> On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge 
> wrote:
>>
>> Does not work. Services deployed on app server are not automatically
>> discovered by governance service. Just tried in private cloud.
>
> Is there a discovery proxy configured for the app server?
> Thanks,
> Hiranya
>
>>
>> Regards
>> Charitha
>>
>> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera  wrote:
>>>
>>> no it also support well known address based protocol as well (AFAIK),
>>> should work in EC2. But we should try and see.
>>> --Srinath
>>>
>>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando  wrote:
>>> > Hi Charitha,
>>> >
>>> > I'm not 100% sure whether this works in EC2, since it seems to be using
>>> > a
>>> > multi cast protocol. But, it works fine on a ordinary setup.
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >
>>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge
>>> > 
>>> > wrote:
>>> >>
>>> >> Hi Folks,
>>> >>
>>> >> Is WS-D support in a testable state in Stratos-1.0?
>>> >>
>>> >> Regards
>>> >> Charitha
>>> >>
>>> >>
>>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka
>>> >>> 
>>> >>> wrote:
>>> 
>>> 
>>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
>>>  wrote:
>>> >
>>> > Where can I find some sample code on how to use this?
>>> 
>>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>>>  endpoints and services. Take a look at the method
>>>  probeDiscoveryProxy or
>>>  resolveService.
>>>  Thanks,
>>>  Hiranya
>>>  [1]
>>> 
>>>  - http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>>> 
>>> >>>
>>> >>> BTW, nice looking code. Its always a pleasure to look at well written
>>> >>> &
>>> >>> well commented code :)
>>> >
>>> > Azeez
>>> >
>>> >
>>> >
>>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
>>> > wrote:
>>> >>
>>> >> Where is the client library? We can make it part of the
>>> >> axis2-client
>>> >> component which we include in webapps.
>>> >> Azeez
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>>> >>  wrote:
>>> >>>
>>> >>>
>>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez 
>>> >>> wrote:
>>> 
>>>  Yes we can do that. So the endpoints have to be published into
>>>  the
>>>  tenants' Governace registry space. Adding parameters to tenants'
>>>  AxisConfig
>>>  can be done by providing an implementation of
>>>  the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver
>>>  and adding
>>>  the parameter in the createdAxisConfiguration method.
>>>  So, going back to our sample,
>>>  1. How does the portal webapp find the service endpoints of the
>>>  Product & Purchasing proxy services?
>>> >>>
>>> >>> The webapp should use the WS-D client API to discover the
>>> >>> necessary
>>> >>> endpoints
>>> >>>
>>> 
>>>  2. How does the ESB task find out the endpoint of the BPEL
>>>  service?
>>> >>>
>>> >>> Task implementation should also use the WS-D client API. Since
>>> >>> tasks
>>> >>> are custom developed Java code, we cannot make WS-D support
>>> >>> tasks. Instead,
>>> >>> tasks should be written in a WS-D aware manner.
>>> >>>
>>> 
>>>  3. How does the ESB find out the endpoint of the
>>>  FinanceConnector
>>>  service?
>>> >>>
>>> >>> ESB UI provides the necessary means to discover endpoints and
>>> >>> create
>>> >>> proxy services on them
>>> >>>
>>> 
>>>  4. How do the Gadgets find out the endpoints of the ShoppingCart
>>>  data service?
>>> >>>
>>> >>> We don't support WS-D in gadgets yet. This is something I
>>> >>> discussed
>>> >>> with Jonathan a few weeks back. We should be able to discover
>>> >>> gadgets using
>>> >>> WS-D and gadgets should be able to discover other endpoints and
>>> >>> gadgets
>>> >>> using WS-D. We'll probably have to write some JavaScript library
>>> >>> wrapping
>>> >>> the WS-D client API. Anyway this is for the future. I need to
>>> >>> talk this
>>> >>> through with the GS team.
>>> >>>
>>> 
>>>  5. How does the BPEL process find out the endpoints of
>>>  the ShoppingCart data service?
>>> >>>
>>> >>> We don't support BPEL yet either. And to be honest I'm not very
>>> >>> familiar with BPEL to think about a way to s

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Fri, Nov 12, 2010 at 11:35 AM, Charitha Kankanamge wrote:

>
> Does not work. Services deployed on app server are not automatically
> discovered by governance service. Just tried in private cloud.
>

Is there a discovery proxy configured for the app server?

Thanks,
Hiranya


>
> Regards
> Charitha
>
>
> On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera  wrote:
>
>> no it also support well known address based protocol as well (AFAIK),
>> should work in EC2. But we should try and see.
>> --Srinath
>>
>> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando  wrote:
>> > Hi Charitha,
>> >
>> > I'm not 100% sure whether this works in EC2, since it seems to be using
>> a
>> > multi cast protocol. But, it works fine on a ordinary setup.
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge <
>> chari...@wso2.com>
>> > wrote:
>> >>
>> >> Hi Folks,
>> >>
>> >> Is WS-D support in a testable state in Stratos-1.0?
>> >>
>> >> Regards
>> >> Charitha
>> >>
>> >>
>> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka <
>> hira...@wso2.com>
>> >>> wrote:
>> 
>> 
>>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez 
>> wrote:
>> >
>> > Where can I find some sample code on how to use this?
>> 
>>  The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>>  endpoints and services. Take a look at the method probeDiscoveryProxy
>> or
>>  resolveService.
>>  Thanks,
>>  Hiranya
>>  [1]
>>  -
>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>> 
>> >>>
>> >>> BTW, nice looking code. Its always a pleasure to look at well written
>> &
>> >>> well commented code :)
>> >
>> > Azeez
>> >
>> >
>> >
>> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
>> wrote:
>> >>
>> >> Where is the client library? We can make it part of the
>> axis2-client
>> >> component which we include in webapps.
>> >> Azeez
>> >>
>> >>
>> >>
>> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>> >>  wrote:
>> >>>
>> >>>
>> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez 
>> >>> wrote:
>> 
>>  Yes we can do that. So the endpoints have to be published into
>> the
>>  tenants' Governace registry space. Adding parameters to tenants'
>> AxisConfig
>>  can be done by providing an implementation of
>>  the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver
>> and adding
>>  the parameter in the createdAxisConfiguration method.
>>  So, going back to our sample,
>>  1. How does the portal webapp find the service endpoints of the
>>  Product & Purchasing proxy services?
>> >>>
>> >>> The webapp should use the WS-D client API to discover the
>> necessary
>> >>> endpoints
>> >>>
>> 
>>  2. How does the ESB task find out the endpoint of the BPEL
>> service?
>> >>>
>> >>> Task implementation should also use the WS-D client API. Since
>> tasks
>> >>> are custom developed Java code, we cannot make WS-D support tasks.
>> Instead,
>> >>> tasks should be written in a WS-D aware manner.
>> >>>
>> 
>>  3. How does the ESB find out the endpoint of the FinanceConnector
>>  service?
>> >>>
>> >>> ESB UI provides the necessary means to discover endpoints and
>> create
>> >>> proxy services on them
>> >>>
>> 
>>  4. How do the Gadgets find out the endpoints of the ShoppingCart
>>  data service?
>> >>>
>> >>> We don't support WS-D in gadgets yet. This is something I
>> discussed
>> >>> with Jonathan a few weeks back. We should be able to discover
>> gadgets using
>> >>> WS-D and gadgets should be able to discover other endpoints and
>> gadgets
>> >>> using WS-D. We'll probably have to write some JavaScript library
>> wrapping
>> >>> the WS-D client API. Anyway this is for the future. I need to talk
>> this
>> >>> through with the GS team.
>> >>>
>> 
>>  5. How does the BPEL process find out the endpoints of
>>  the ShoppingCart data service?
>> >>>
>> >>> We don't support BPEL yet either. And to be honest I'm not very
>> >>> familiar with BPEL to think about a way to support WS-D in BPS.
>> May be
>> >>> Waruna can help me out here. Does BPS use any Axis2 client stuff
>> to talk to
>> >>> the service endpoints? If so we may be able to use the Axis2
>> client module
>> >>> for WS-D (or the client API depending on how it's done).
>> 
>>  I think there should be a way to have logical references to
>>  endpoints. Does your implementation provide this?
>> >>>
>> >>> This is provided by the WS-

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando  wrote:

> Hi Charitha,
>
> I'm not 100% sure whether this works in EC2, since it seems to be using a
> multi cast protocol. But, it works fine on a ordinary setup.
>

We don't support that model yet. We only support the managed mode which runs
on HTTP.

Thanks,
Hiranya


>
> Thanks,
> Senaka.
>
>
> On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge 
> wrote:
>
>>
>> Hi Folks,
>>
>> Is WS-D support in a testable state in Stratos-1.0?
>>
>> Regards
>> Charitha
>>
>>
>>
>> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
>>
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:

> Where can I find some sample code on how to use this?


 The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
 endpoints and services. Take a look at the method probeDiscoveryProxy or
 resolveService.

 Thanks,
 Hiranya

 [1] -
 http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java


>>>
>>> BTW, nice looking code. Its always a pleasure to look at well written &
>>> well commented code :)
>>>

> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>
>> Where is the client library? We can make it part of the axis2-client
>> component which we include in webapps.
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez wrote:
>>>
 Yes we can do that. So the endpoints have to be published into the
 tenants' Governace registry space. Adding parameters to tenants' 
 AxisConfig
 can be done by providing an implementation of
 the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
 adding
 the parameter in the createdAxisConfiguration method.

 So, going back to our sample,

 1. How does the portal webapp find the service endpoints of the
 Product & Purchasing proxy services?

>>>
>>> The webapp should use the WS-D client API to discover the necessary
>>> endpoints
>>>
>>>
 2. How does the ESB task find out the endpoint of the BPEL service?

>>>
>>> Task implementation should also use the WS-D client API. Since tasks
>>> are custom developed Java code, we cannot make WS-D support tasks. 
>>> Instead,
>>> tasks should be written in a WS-D aware manner.
>>>
>>>
 3. How does the ESB find out the endpoint of the FinanceConnector
 service?

>>>
>>> ESB UI provides the necessary means to discover endpoints and create
>>> proxy services on them
>>>
>>>
 4. How do the Gadgets find out the endpoints of the ShoppingCart
 data service?

>>>
>>> We don't support WS-D in gadgets yet. This is something I discussed
>>> with Jonathan a few weeks back. We should be able to discover gadgets 
>>> using
>>> WS-D and gadgets should be able to discover other endpoints and gadgets
>>> using WS-D. We'll probably have to write some JavaScript library 
>>> wrapping
>>> the WS-D client API. Anyway this is for the future. I need to talk this
>>> through with the GS team.
>>>
>>>
 5. How does the BPEL process find out the endpoints of
 the ShoppingCart data service?

>>>
>>> We don't support BPEL yet either. And to be honest I'm not very
>>> familiar with BPEL to think about a way to support WS-D in BPS. May be
>>> Waruna can help me out here. Does BPS use any Axis2 client stuff to 
>>> talk to
>>> the service endpoints? If so we may be able to use the Axis2 client 
>>> module
>>> for WS-D (or the client API depending on how it's done).
>>>
>>>
 I think there should be a way to have logical references to
 endpoints. Does your implementation provide this?

>>>
>>> This is provided by the WS-D specs. An endpoint is identified by a
>>> platform-wide unique identifier. Each endpoint is also associated with 
>>> a set
>>> of user defined scopes and types that can be used to index and search
>>> endpoints.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Azeez



 On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka <
 hira...@wso2.com> wrote:

> Hi Azeez,
>
> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez wrote:
>
>> It would be great if you could show us how to use WS-Discovery in
>> our sam

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Charitha Kankanamge]

Does not work. Services deployed on app server are not automatically
discovered by governance service. Just tried in private cloud.

Regards
Charitha

On Thu, Nov 11, 2010 at 5:12 PM, Srinath Perera  wrote:

> no it also support well known address based protocol as well (AFAIK),
> should work in EC2. But we should try and see.
> --Srinath
>
> On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando  wrote:
> > Hi Charitha,
> >
> > I'm not 100% sure whether this works in EC2, since it seems to be using a
> > multi cast protocol. But, it works fine on a ordinary setup.
> >
> > Thanks,
> > Senaka.
> >
> > On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge  >
> > wrote:
> >>
> >> Hi Folks,
> >>
> >> Is WS-D support in a testable state in Stratos-1.0?
> >>
> >> Regards
> >> Charitha
> >>
> >>
> >> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka  >
> >>> wrote:
> 
> 
>  On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
> >
> > Where can I find some sample code on how to use this?
> 
>  The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>  endpoints and services. Take a look at the method probeDiscoveryProxy
> or
>  resolveService.
>  Thanks,
>  Hiranya
>  [1]
>  -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
> 
> >>>
> >>> BTW, nice looking code. Its always a pleasure to look at well written &
> >>> well commented code :)
> >
> > Azeez
> >
> >
> >
> > On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez 
> wrote:
> >>
> >> Where is the client library? We can make it part of the axis2-client
> >> component which we include in webapps.
> >> Azeez
> >>
> >>
> >>
> >> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
> >>  wrote:
> >>>
> >>>
> >>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez 
> >>> wrote:
> 
>  Yes we can do that. So the endpoints have to be published into the
>  tenants' Governace registry space. Adding parameters to tenants'
> AxisConfig
>  can be done by providing an implementation of
>  the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver
> and adding
>  the parameter in the createdAxisConfiguration method.
>  So, going back to our sample,
>  1. How does the portal webapp find the service endpoints of the
>  Product & Purchasing proxy services?
> >>>
> >>> The webapp should use the WS-D client API to discover the necessary
> >>> endpoints
> >>>
> 
>  2. How does the ESB task find out the endpoint of the BPEL
> service?
> >>>
> >>> Task implementation should also use the WS-D client API. Since
> tasks
> >>> are custom developed Java code, we cannot make WS-D support tasks.
> Instead,
> >>> tasks should be written in a WS-D aware manner.
> >>>
> 
>  3. How does the ESB find out the endpoint of the FinanceConnector
>  service?
> >>>
> >>> ESB UI provides the necessary means to discover endpoints and
> create
> >>> proxy services on them
> >>>
> 
>  4. How do the Gadgets find out the endpoints of the ShoppingCart
>  data service?
> >>>
> >>> We don't support WS-D in gadgets yet. This is something I discussed
> >>> with Jonathan a few weeks back. We should be able to discover
> gadgets using
> >>> WS-D and gadgets should be able to discover other endpoints and
> gadgets
> >>> using WS-D. We'll probably have to write some JavaScript library
> wrapping
> >>> the WS-D client API. Anyway this is for the future. I need to talk
> this
> >>> through with the GS team.
> >>>
> 
>  5. How does the BPEL process find out the endpoints of
>  the ShoppingCart data service?
> >>>
> >>> We don't support BPEL yet either. And to be honest I'm not very
> >>> familiar with BPEL to think about a way to support WS-D in BPS. May
> be
> >>> Waruna can help me out here. Does BPS use any Axis2 client stuff to
> talk to
> >>> the service endpoints? If so we may be able to use the Axis2 client
> module
> >>> for WS-D (or the client API depending on how it's done).
> 
>  I think there should be a way to have logical references to
>  endpoints. Does your implementation provide this?
> >>>
> >>> This is provided by the WS-D specs. An endpoint is identified by a
> >>> platform-wide unique identifier. Each endpoint is also associated
> with a set
> >>> of user defined scopes and types that can be used to index and
> search
> >>> endpoints.
> >>> Thanks,
> >>> Hiranya
> >>>
> 
>  Azeez
> 
> 
>  On Wed, Sep 22, 2

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Srinath Perera]

no it also support well known address based protocol as well (AFAIK),
should work in EC2. But we should try and see.
--Srinath

On Thu, Nov 11, 2010 at 5:05 PM, Senaka Fernando  wrote:
> Hi Charitha,
>
> I'm not 100% sure whether this works in EC2, since it seems to be using a
> multi cast protocol. But, it works fine on a ordinary setup.
>
> Thanks,
> Senaka.
>
> On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge 
> wrote:
>>
>> Hi Folks,
>>
>> Is WS-D support in a testable state in Stratos-1.0?
>>
>> Regards
>> Charitha
>>
>>
>> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka 
>>> wrote:


 On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
>
> Where can I find some sample code on how to use this?

 The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
 endpoints and services. Take a look at the method probeDiscoveryProxy or
 resolveService.
 Thanks,
 Hiranya
 [1]
 - http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java

>>>
>>> BTW, nice looking code. Its always a pleasure to look at well written &
>>> well commented code :)
>
> Azeez
>
>
>
> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>>
>> Where is the client library? We can make it part of the axis2-client
>> component which we include in webapps.
>> Azeez
>>
>>
>>
>> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka
>>  wrote:
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez 
>>> wrote:

 Yes we can do that. So the endpoints have to be published into the
 tenants' Governace registry space. Adding parameters to tenants' 
 AxisConfig
 can be done by providing an implementation of
 the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
 adding
 the parameter in the createdAxisConfiguration method.
 So, going back to our sample,
 1. How does the portal webapp find the service endpoints of the
 Product & Purchasing proxy services?
>>>
>>> The webapp should use the WS-D client API to discover the necessary
>>> endpoints
>>>

 2. How does the ESB task find out the endpoint of the BPEL service?
>>>
>>> Task implementation should also use the WS-D client API. Since tasks
>>> are custom developed Java code, we cannot make WS-D support tasks. 
>>> Instead,
>>> tasks should be written in a WS-D aware manner.
>>>

 3. How does the ESB find out the endpoint of the FinanceConnector
 service?
>>>
>>> ESB UI provides the necessary means to discover endpoints and create
>>> proxy services on them
>>>

 4. How do the Gadgets find out the endpoints of the ShoppingCart
 data service?
>>>
>>> We don't support WS-D in gadgets yet. This is something I discussed
>>> with Jonathan a few weeks back. We should be able to discover gadgets 
>>> using
>>> WS-D and gadgets should be able to discover other endpoints and gadgets
>>> using WS-D. We'll probably have to write some JavaScript library 
>>> wrapping
>>> the WS-D client API. Anyway this is for the future. I need to talk this
>>> through with the GS team.
>>>

 5. How does the BPEL process find out the endpoints of
 the ShoppingCart data service?
>>>
>>> We don't support BPEL yet either. And to be honest I'm not very
>>> familiar with BPEL to think about a way to support WS-D in BPS. May be
>>> Waruna can help me out here. Does BPS use any Axis2 client stuff to 
>>> talk to
>>> the service endpoints? If so we may be able to use the Axis2 client 
>>> module
>>> for WS-D (or the client API depending on how it's done).

 I think there should be a way to have logical references to
 endpoints. Does your implementation provide this?
>>>
>>> This is provided by the WS-D specs. An endpoint is identified by a
>>> platform-wide unique identifier. Each endpoint is also associated with 
>>> a set
>>> of user defined scopes and types that can be used to index and search
>>> endpoints.
>>> Thanks,
>>> Hiranya
>>>

 Azeez


 On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka
  wrote:
>
> Hi Azeez,
>
> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez 
> wrote:
>>
>> It would be great if you could show us how to use WS-Discovery in
>> our sample.
>
> Can we set parameters on the tenant AxisConfiguration? In a
> standalone Carbon we could edit the axis2.xml to do that. Is th

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Senaka Fernando]

Hi Charitha,

I'm not 100% sure whether this works in EC2, since it seems to be using a
multi cast protocol. But, it works fine on a ordinary setup.

Thanks,
Senaka.

On Thu, Nov 11, 2010 at 11:23 AM, Charitha Kankanamge wrote:

>
> Hi Folks,
>
> Is WS-D support in a testable state in Stratos-1.0?
>
> Regards
> Charitha
>
>
>
> On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:
>
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
>>>
 Where can I find some sample code on how to use this?
>>>
>>>
>>> The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>>> endpoints and services. Take a look at the method probeDiscoveryProxy or
>>> resolveService.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>> [1] -
>>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>>>
>>>
>>
>> BTW, nice looking code. Its always a pleasure to look at well written &
>> well commented code :)
>>
>>>
 Azeez




 On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:

> Where is the client library? We can make it part of the axis2-client
> component which we include in webapps.
>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez wrote:
>>
>>> Yes we can do that. So the endpoints have to be published into the
>>> tenants' Governace registry space. Adding parameters to tenants' 
>>> AxisConfig
>>> can be done by providing an implementation of
>>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
>>> adding
>>> the parameter in the createdAxisConfiguration method.
>>>
>>> So, going back to our sample,
>>>
>>> 1. How does the portal webapp find the service endpoints of the
>>> Product & Purchasing proxy services?
>>>
>>
>> The webapp should use the WS-D client API to discover the necessary
>> endpoints
>>
>>
>>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>>
>>
>> Task implementation should also use the WS-D client API. Since tasks
>> are custom developed Java code, we cannot make WS-D support tasks. 
>> Instead,
>> tasks should be written in a WS-D aware manner.
>>
>>
>>> 3. How does the ESB find out the endpoint of the FinanceConnector
>>> service?
>>>
>>
>> ESB UI provides the necessary means to discover endpoints and create
>> proxy services on them
>>
>>
>>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>>> service?
>>>
>>
>> We don't support WS-D in gadgets yet. This is something I discussed
>> with Jonathan a few weeks back. We should be able to discover gadgets 
>> using
>> WS-D and gadgets should be able to discover other endpoints and gadgets
>> using WS-D. We'll probably have to write some JavaScript library wrapping
>> the WS-D client API. Anyway this is for the future. I need to talk this
>> through with the GS team.
>>
>>
>>> 5. How does the BPEL process find out the endpoints of
>>> the ShoppingCart data service?
>>>
>>
>> We don't support BPEL yet either. And to be honest I'm not very
>> familiar with BPEL to think about a way to support WS-D in BPS. May be
>> Waruna can help me out here. Does BPS use any Axis2 client stuff to talk 
>> to
>> the service endpoints? If so we may be able to use the Axis2 client 
>> module
>> for WS-D (or the client API depending on how it's done).
>>
>>
>>> I think there should be a way to have logical references to
>>> endpoints. Does your implementation provide this?
>>>
>>
>> This is provided by the WS-D specs. An endpoint is identified by a
>> platform-wide unique identifier. Each endpoint is also associated with a 
>> set
>> of user defined scopes and types that can be used to index and search
>> endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Azeez
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>
 Hi Azeez,

 On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez wrote:

> It would be great if you could show us how to use WS-Discovery in
> our sample.


 Can we set parameters on the tenant AxisConfiguration? In a
 standalone Carbon we could edit the axis2.xml to do that. Is there 
 some way
 to do the equivalent in Stratos?

 If we can get that done, then it's just a matter of enabling
 WS-Discovery in Stratos app server. It will start publi

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Charitha Kankanamge]

Hi Folks,

Is WS-D support in a testable state in Stratos-1.0?

Regards
Charitha


On Wed, Sep 22, 2010 at 2:20 PM, Afkham Azeez  wrote:

>
>
>
>
> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
>>
>>> Where can I find some sample code on how to use this?
>>
>>
>> The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>> endpoints and services. Take a look at the method probeDiscoveryProxy or
>> resolveService.
>>
>> Thanks,
>> Hiranya
>>
>> [1] -
>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>>
>>
>
> BTW, nice looking code. Its always a pleasure to look at well written &
> well commented code :)
>
>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>>>
 Where is the client library? We can make it part of the axis2-client
 component which we include in webapps.

 Azeez




 On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>
>> Yes we can do that. So the endpoints have to be published into the
>> tenants' Governace registry space. Adding parameters to tenants' 
>> AxisConfig
>> can be done by providing an implementation of
>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
>> adding
>> the parameter in the createdAxisConfiguration method.
>>
>> So, going back to our sample,
>>
>> 1. How does the portal webapp find the service endpoints of the
>> Product & Purchasing proxy services?
>>
>
> The webapp should use the WS-D client API to discover the necessary
> endpoints
>
>
>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>
>
> Task implementation should also use the WS-D client API. Since tasks
> are custom developed Java code, we cannot make WS-D support tasks. 
> Instead,
> tasks should be written in a WS-D aware manner.
>
>
>> 3. How does the ESB find out the endpoint of the FinanceConnector
>> service?
>>
>
> ESB UI provides the necessary means to discover endpoints and create
> proxy services on them
>
>
>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>> service?
>>
>
> We don't support WS-D in gadgets yet. This is something I discussed
> with Jonathan a few weeks back. We should be able to discover gadgets 
> using
> WS-D and gadgets should be able to discover other endpoints and gadgets
> using WS-D. We'll probably have to write some JavaScript library wrapping
> the WS-D client API. Anyway this is for the future. I need to talk this
> through with the GS team.
>
>
>> 5. How does the BPEL process find out the endpoints of
>> the ShoppingCart data service?
>>
>
> We don't support BPEL yet either. And to be honest I'm not very
> familiar with BPEL to think about a way to support WS-D in BPS. May be
> Waruna can help me out here. Does BPS use any Axis2 client stuff to talk 
> to
> the service endpoints? If so we may be able to use the Axis2 client module
> for WS-D (or the client API depending on how it's done).
>
>
>> I think there should be a way to have logical references to endpoints.
>> Does your implementation provide this?
>>
>
> This is provided by the WS-D specs. An endpoint is identified by a
> platform-wide unique identifier. Each endpoint is also associated with a 
> set
> of user defined scopes and types that can be used to index and search
> endpoints.
>
> Thanks,
> Hiranya
>
>
>>
>> Azeez
>>
>>
>>
>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>> Hi Azeez,
>>>
>>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez wrote:
>>>
 It would be great if you could show us how to use WS-Discovery in
 our sample.
>>>
>>>
>>> Can we set parameters on the tenant AxisConfiguration? In a
>>> standalone Carbon we could edit the axis2.xml to do that. Is there some 
>>> way
>>> to do the equivalent in Stratos?
>>>
>>> If we can get that done, then it's just a matter of enabling
>>> WS-Discovery in Stratos app server. It will start publishing service
>>> endpoints to GReg. Then the ESB can probe the registry to discover the
>>> endpoints.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
 Azeez




 On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez wrote:

> I'm more concerned about getting this to work on Stratos. UDP will
> not work in that case. So

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka wrote:

>
>
> On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
>
>> Where can I find some sample code on how to use this?
>
>
> The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
> endpoints and services. Take a look at the method probeDiscoveryProxy or
> resolveService.
>
> Thanks,
> Hiranya
>
> [1] -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>
>

BTW, nice looking code. Its always a pleasure to look at well written & well
commented code :)

>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>>
>>> Where is the client library? We can make it part of the axis2-client
>>> component which we include in webapps.
>>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:

> Yes we can do that. So the endpoints have to be published into the
> tenants' Governace registry space. Adding parameters to tenants' 
> AxisConfig
> can be done by providing an implementation of
> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
> adding
> the parameter in the createdAxisConfiguration method.
>
> So, going back to our sample,
>
> 1. How does the portal webapp find the service endpoints of the Product
> & Purchasing proxy services?
>

 The webapp should use the WS-D client API to discover the necessary
 endpoints


> 2. How does the ESB task find out the endpoint of the BPEL service?
>

 Task implementation should also use the WS-D client API. Since tasks are
 custom developed Java code, we cannot make WS-D support tasks. Instead,
 tasks should be written in a WS-D aware manner.


> 3. How does the ESB find out the endpoint of the FinanceConnector
> service?
>

 ESB UI provides the necessary means to discover endpoints and create
 proxy services on them


> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
> service?
>

 We don't support WS-D in gadgets yet. This is something I discussed with
 Jonathan a few weeks back. We should be able to discover gadgets using WS-D
 and gadgets should be able to discover other endpoints and gadgets using
 WS-D. We'll probably have to write some JavaScript library wrapping the 
 WS-D
 client API. Anyway this is for the future. I need to talk this through with
 the GS team.


> 5. How does the BPEL process find out the endpoints of the ShoppingCart
> data service?
>

 We don't support BPEL yet either. And to be honest I'm not very familiar
 with BPEL to think about a way to support WS-D in BPS. May be Waruna can
 help me out here. Does BPS use any Axis2 client stuff to talk to the 
 service
 endpoints? If so we may be able to use the Axis2 client module for WS-D (or
 the client API depending on how it's done).


> I think there should be a way to have logical references to endpoints.
> Does your implementation provide this?
>

 This is provided by the WS-D specs. An endpoint is identified by a
 platform-wide unique identifier. Each endpoint is also associated with a 
 set
 of user defined scopes and types that can be used to index and search
 endpoints.

 Thanks,
 Hiranya


>
> Azeez
>
>
>
> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>> Hi Azeez,
>>
>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez wrote:
>>
>>> It would be great if you could show us how to use WS-Discovery in our
>>> sample.
>>
>>
>> Can we set parameters on the tenant AxisConfiguration? In a standalone
>> Carbon we could edit the axis2.xml to do that. Is there some way to do 
>> the
>> equivalent in Stratos?
>>
>> If we can get that done, then it's just a matter of enabling
>> WS-Discovery in Stratos app server. It will start publishing service
>> endpoints to GReg. Then the ESB can probe the registry to discover the
>> endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez wrote:
>>>
 I'm more concerned about getting this to work on Stratos. UDP will
 not work in that case. So, managed mode should be sufficient for us. 
 Can you
 advice us on how to set this up on Stratos?

 Azeez




 On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
 hira...@wso2.com> wrote:

>
>
> On

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

+1

We should update the shopping cart sample to work with WS-Discovery. I think
providing a nice API through CarbonContext will be useful and make life
easier for the developers.

Azeez



On Wed, Sep 22, 2010 at 2:08 PM, Hiranya Jayathilaka wrote:

> Hi Azeez,
>
> If you are interested I can give a short walk-through on how to use the
> WS-D APIs when writing services, webapps etc tomorrow. Just let me know.
> Also when using WS-D there are some design time concerns that we should
> think of as well; such as grouping services into appropriate scopes etc.
>
> Thanks,
> Hiranya
>
>
> On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
>>
>>> Where can I find some sample code on how to use this?
>>
>>
>> The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
>> endpoints and services. Take a look at the method probeDiscoveryProxy or
>> resolveService.
>>
>> Thanks,
>> Hiranya
>>
>> [1] -
>> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>>
>>
>>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>>>
 Where is the client library? We can make it part of the axis2-client
 component which we include in webapps.

 Azeez




 On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>
>> Yes we can do that. So the endpoints have to be published into the
>> tenants' Governace registry space. Adding parameters to tenants' 
>> AxisConfig
>> can be done by providing an implementation of
>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
>> adding
>> the parameter in the createdAxisConfiguration method.
>>
>> So, going back to our sample,
>>
>> 1. How does the portal webapp find the service endpoints of the
>> Product & Purchasing proxy services?
>>
>
> The webapp should use the WS-D client API to discover the necessary
> endpoints
>
>
>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>
>
> Task implementation should also use the WS-D client API. Since tasks
> are custom developed Java code, we cannot make WS-D support tasks. 
> Instead,
> tasks should be written in a WS-D aware manner.
>
>
>> 3. How does the ESB find out the endpoint of the FinanceConnector
>> service?
>>
>
> ESB UI provides the necessary means to discover endpoints and create
> proxy services on them
>
>
>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>> service?
>>
>
> We don't support WS-D in gadgets yet. This is something I discussed
> with Jonathan a few weeks back. We should be able to discover gadgets 
> using
> WS-D and gadgets should be able to discover other endpoints and gadgets
> using WS-D. We'll probably have to write some JavaScript library wrapping
> the WS-D client API. Anyway this is for the future. I need to talk this
> through with the GS team.
>
>
>> 5. How does the BPEL process find out the endpoints of
>> the ShoppingCart data service?
>>
>
> We don't support BPEL yet either. And to be honest I'm not very
> familiar with BPEL to think about a way to support WS-D in BPS. May be
> Waruna can help me out here. Does BPS use any Axis2 client stuff to talk 
> to
> the service endpoints? If so we may be able to use the Axis2 client module
> for WS-D (or the client API depending on how it's done).
>
>
>> I think there should be a way to have logical references to endpoints.
>> Does your implementation provide this?
>>
>
> This is provided by the WS-D specs. An endpoint is identified by a
> platform-wide unique identifier. Each endpoint is also associated with a 
> set
> of user defined scopes and types that can be used to index and search
> endpoints.
>
> Thanks,
> Hiranya
>
>
>>
>> Azeez
>>
>>
>>
>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>> Hi Azeez,
>>>
>>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez wrote:
>>>
 It would be great if you could show us how to use WS-Discovery in
 our sample.
>>>
>>>
>>> Can we set parameters on the tenant AxisConfiguration? In a
>>> standalone Carbon we could edit the axis2.xml to do that. Is there some 
>>> way
>>> to do the equivalent in Stratos?
>>>
>>> If we can get that done, then it's just a matter of enabling
>>> WS-Discovery in Stratos app server. It will start publishing service
>>> endpoints to GReg. Then the ESB can prob

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

Hi Azeez,

If you are interested I can give a short walk-through on how to use the WS-D
APIs when writing services, webapps etc tomorrow. Just let me know. Also
when using WS-D there are some design time concerns that we should think of
as well; such as grouping services into appropriate scopes etc.

Thanks,
Hiranya

On Wed, Sep 22, 2010 at 2:02 PM, Hiranya Jayathilaka wrote:

>
>
> On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:
>
>> Where can I find some sample code on how to use this?
>
>
> The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
> endpoints and services. Take a look at the method probeDiscoveryProxy or
> resolveService.
>
> Thanks,
> Hiranya
>
> [1] -
> http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java
>
>
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>>
>>> Where is the client library? We can make it part of the axis2-client
>>> component which we include in webapps.
>>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:

> Yes we can do that. So the endpoints have to be published into the
> tenants' Governace registry space. Adding parameters to tenants' 
> AxisConfig
> can be done by providing an implementation of
> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and 
> adding
> the parameter in the createdAxisConfiguration method.
>
> So, going back to our sample,
>
> 1. How does the portal webapp find the service endpoints of the Product
> & Purchasing proxy services?
>

 The webapp should use the WS-D client API to discover the necessary
 endpoints


> 2. How does the ESB task find out the endpoint of the BPEL service?
>

 Task implementation should also use the WS-D client API. Since tasks are
 custom developed Java code, we cannot make WS-D support tasks. Instead,
 tasks should be written in a WS-D aware manner.


> 3. How does the ESB find out the endpoint of the FinanceConnector
> service?
>

 ESB UI provides the necessary means to discover endpoints and create
 proxy services on them


> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
> service?
>

 We don't support WS-D in gadgets yet. This is something I discussed with
 Jonathan a few weeks back. We should be able to discover gadgets using WS-D
 and gadgets should be able to discover other endpoints and gadgets using
 WS-D. We'll probably have to write some JavaScript library wrapping the 
 WS-D
 client API. Anyway this is for the future. I need to talk this through with
 the GS team.


> 5. How does the BPEL process find out the endpoints of the ShoppingCart
> data service?
>

 We don't support BPEL yet either. And to be honest I'm not very familiar
 with BPEL to think about a way to support WS-D in BPS. May be Waruna can
 help me out here. Does BPS use any Axis2 client stuff to talk to the 
 service
 endpoints? If so we may be able to use the Axis2 client module for WS-D (or
 the client API depending on how it's done).


> I think there should be a way to have logical references to endpoints.
> Does your implementation provide this?
>

 This is provided by the WS-D specs. An endpoint is identified by a
 platform-wide unique identifier. Each endpoint is also associated with a 
 set
 of user defined scopes and types that can be used to index and search
 endpoints.

 Thanks,
 Hiranya


>
> Azeez
>
>
>
> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>> Hi Azeez,
>>
>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez wrote:
>>
>>> It would be great if you could show us how to use WS-Discovery in our
>>> sample.
>>
>>
>> Can we set parameters on the tenant AxisConfiguration? In a standalone
>> Carbon we could edit the axis2.xml to do that. Is there some way to do 
>> the
>> equivalent in Stratos?
>>
>> If we can get that done, then it's just a matter of enabling
>> WS-Discovery in Stratos app server. It will start publishing service
>> endpoints to GReg. Then the ESB can probe the registry to discover the
>> endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez wrote:
>>>
 I'm more concerned about getting this to work on Stratos. UDP will
 not work in that case. So, managed mode should be sufficient for us. 
 Can you
 advice us on how to s

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Wed, Sep 22, 2010 at 1:30 PM, Afkham Azeez  wrote:

> Where can I find some sample code on how to use this?


The DiscoveryMgtUtils class [1] uses the WS-D client API to discover
endpoints and services. Take a look at the method probeDiscoveryProxy or
resolveService.

Thanks,
Hiranya

[1] -
http://svn.wso2.org/repos/wso2/trunk/carbon/components/ws-discovery/org.wso2.carbon.discovery.core/src/main/java/org/wso2/carbon/discovery/util/DiscoveryMgtUtils.java


>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>
>> Where is the client library? We can make it part of the axis2-client
>> component which we include in webapps.
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>>>
 Yes we can do that. So the endpoints have to be published into the
 tenants' Governace registry space. Adding parameters to tenants' AxisConfig
 can be done by providing an implementation of
 the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
 the parameter in the createdAxisConfiguration method.

 So, going back to our sample,

 1. How does the portal webapp find the service endpoints of the Product
 & Purchasing proxy services?

>>>
>>> The webapp should use the WS-D client API to discover the necessary
>>> endpoints
>>>
>>>
 2. How does the ESB task find out the endpoint of the BPEL service?

>>>
>>> Task implementation should also use the WS-D client API. Since tasks are
>>> custom developed Java code, we cannot make WS-D support tasks. Instead,
>>> tasks should be written in a WS-D aware manner.
>>>
>>>
 3. How does the ESB find out the endpoint of the FinanceConnector
 service?

>>>
>>> ESB UI provides the necessary means to discover endpoints and create
>>> proxy services on them
>>>
>>>
 4. How do the Gadgets find out the endpoints of the ShoppingCart data
 service?

>>>
>>> We don't support WS-D in gadgets yet. This is something I discussed with
>>> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
>>> and gadgets should be able to discover other endpoints and gadgets using
>>> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
>>> client API. Anyway this is for the future. I need to talk this through with
>>> the GS team.
>>>
>>>
 5. How does the BPEL process find out the endpoints of the ShoppingCart
 data service?

>>>
>>> We don't support BPEL yet either. And to be honest I'm not very familiar
>>> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
>>> help me out here. Does BPS use any Axis2 client stuff to talk to the service
>>> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
>>> the client API depending on how it's done).
>>>
>>>
 I think there should be a way to have logical references to endpoints.
 Does your implementation provide this?

>>>
>>> This is provided by the WS-D specs. An endpoint is identified by a
>>> platform-wide unique identifier. Each endpoint is also associated with a set
>>> of user defined scopes and types that can be used to index and search
>>> endpoints.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Azeez



 On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka >>> > wrote:

> Hi Azeez,
>
> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:
>
>> It would be great if you could show us how to use WS-Discovery in our
>> sample.
>
>
> Can we set parameters on the tenant AxisConfiguration? In a standalone
> Carbon we could edit the axis2.xml to do that. Is there some way to do the
> equivalent in Stratos?
>
> If we can get that done, then it's just a matter of enabling
> WS-Discovery in Stratos app server. It will start publishing service
> endpoints to GReg. Then the ESB can probe the registry to discover the
> endpoints.
>
> Thanks,
> Hiranya
>
>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez wrote:
>>
>>> I'm more concerned about getting this to work on Stratos. UDP will
>>> not work in that case. So, managed mode should be sufficient for us. 
>>> Can you
>>> advice us on how to set this up on Stratos?
>>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>


 On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:

> Hi folks,
> $subject
>
> Can we use this to run our sample Acme shopping cart application on
> Stratos? Please note that we need to have this running before the 
> Stratos
> 1.0 release.
>

 In WSAS and DS this should be enabled by setting an

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

Senaka,
Can we bridge this into CarbonContext so that tenants get a clean API to
work with?

Azeez



On Wed, Sep 22, 2010 at 1:54 PM, Hiranya Jayathilaka wrote:

>
>
> On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:
>
>> Where is the client library? We can make it part of the axis2-client
>> component which we include in webapps.
>
>
> Client API is available in the org.wso2.carbon.discovery.core component.
> This component is shipped with WSAS, ESB, GReg and DS by default. I think MS
> also ships it out.
>
> Thanks,
> Hiranya
>
>
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>>>
 Yes we can do that. So the endpoints have to be published into the
 tenants' Governace registry space. Adding parameters to tenants' AxisConfig
 can be done by providing an implementation of
 the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
 the parameter in the createdAxisConfiguration method.

 So, going back to our sample,

 1. How does the portal webapp find the service endpoints of the Product
 & Purchasing proxy services?

>>>
>>> The webapp should use the WS-D client API to discover the necessary
>>> endpoints
>>>
>>>
 2. How does the ESB task find out the endpoint of the BPEL service?

>>>
>>> Task implementation should also use the WS-D client API. Since tasks are
>>> custom developed Java code, we cannot make WS-D support tasks. Instead,
>>> tasks should be written in a WS-D aware manner.
>>>
>>>
 3. How does the ESB find out the endpoint of the FinanceConnector
 service?

>>>
>>> ESB UI provides the necessary means to discover endpoints and create
>>> proxy services on them
>>>
>>>
 4. How do the Gadgets find out the endpoints of the ShoppingCart data
 service?

>>>
>>> We don't support WS-D in gadgets yet. This is something I discussed with
>>> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
>>> and gadgets should be able to discover other endpoints and gadgets using
>>> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
>>> client API. Anyway this is for the future. I need to talk this through with
>>> the GS team.
>>>
>>>
 5. How does the BPEL process find out the endpoints of the ShoppingCart
 data service?

>>>
>>> We don't support BPEL yet either. And to be honest I'm not very familiar
>>> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
>>> help me out here. Does BPS use any Axis2 client stuff to talk to the service
>>> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
>>> the client API depending on how it's done).
>>>
>>>
 I think there should be a way to have logical references to endpoints.
 Does your implementation provide this?

>>>
>>> This is provided by the WS-D specs. An endpoint is identified by a
>>> platform-wide unique identifier. Each endpoint is also associated with a set
>>> of user defined scopes and types that can be used to index and search
>>> endpoints.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Azeez



 On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka >>> > wrote:

> Hi Azeez,
>
> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:
>
>> It would be great if you could show us how to use WS-Discovery in our
>> sample.
>
>
> Can we set parameters on the tenant AxisConfiguration? In a standalone
> Carbon we could edit the axis2.xml to do that. Is there some way to do the
> equivalent in Stratos?
>
> If we can get that done, then it's just a matter of enabling
> WS-Discovery in Stratos app server. It will start publishing service
> endpoints to GReg. Then the ESB can probe the registry to discover the
> endpoints.
>
> Thanks,
> Hiranya
>
>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez wrote:
>>
>>> I'm more concerned about getting this to work on Stratos. UDP will
>>> not work in that case. So, managed mode should be sufficient for us. 
>>> Can you
>>> advice us on how to set this up on Stratos?
>>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>


 On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:

> Hi folks,
> $subject
>
> Can we use this to run our sample Acme shopping cart application on
> Stratos? Please note that we need to have this running before the 
> Stratos
> 1.0 release.
>

 In WSAS and DS this should be enabled by setting an
 AxisConfiguration parameter. Does Stratos allow that? If not we need to
 develop some sort of a U

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

Hi Waruna,

On Wed, Sep 22, 2010 at 1:54 PM, Waruna Ranasinghe  wrote:

>
>
> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>>
>>> Yes we can do that. So the endpoints have to be published into the
>>> tenants' Governace registry space. Adding parameters to tenants' AxisConfig
>>> can be done by providing an implementation of
>>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
>>> the parameter in the createdAxisConfiguration method.
>>>
>>> So, going back to our sample,
>>>
>>> 1. How does the portal webapp find the service endpoints of the Product &
>>> Purchasing proxy services?
>>>
>>
>> The webapp should use the WS-D client API to discover the necessary
>> endpoints
>>
>>
>>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>>
>>
>> Task implementation should also use the WS-D client API. Since tasks are
>> custom developed Java code, we cannot make WS-D support tasks. Instead,
>> tasks should be written in a WS-D aware manner.
>>
>>
>>> 3. How does the ESB find out the endpoint of the FinanceConnector
>>> service?
>>>
>>
>> ESB UI provides the necessary means to discover endpoints and create proxy
>> services on them
>>
>>
>>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>>> service?
>>>
>>
>> We don't support WS-D in gadgets yet. This is something I discussed with
>> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
>> and gadgets should be able to discover other endpoints and gadgets using
>> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
>> client API. Anyway this is for the future. I need to talk this through with
>> the GS team.
>>
>>
>>> 5. How does the BPEL process find out the endpoints of the ShoppingCart
>>> data service?
>>>
>>
>> We don't support BPEL yet either. And to be honest I'm not very familiar
>> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
>> help me out here. Does BPS use any Axis2 client stuff to talk to the service
>> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
>> the client API depending on how it's done).
>>
> Yes, We use OperationClient to invoke external services.
>

That's great. Then we should be able to use the existing WS-D APIs to
discover endpoints from within a BPEL. Le't meet up soon and see how we can
actually implement it.

Thanks,
Hiranya


>
> Thanks,
> Waruna
>
>>
>>
>>> I think there should be a way to have logical references to endpoints.
>>> Does your implementation provide this?
>>>
>>
>> This is provided by the WS-D specs. An endpoint is identified by a
>> platform-wide unique identifier. Each endpoint is also associated with a set
>> of user defined scopes and types that can be used to index and search
>> endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Azeez
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka 
>>> wrote:
>>>
 Hi Azeez,

 On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:

> It would be great if you could show us how to use WS-Discovery in our
> sample.


 Can we set parameters on the tenant AxisConfiguration? In a standalone
 Carbon we could edit the axis2.xml to do that. Is there some way to do the
 equivalent in Stratos?

 If we can get that done, then it's just a matter of enabling
 WS-Discovery in Stratos app server. It will start publishing service
 endpoints to GReg. Then the ESB can probe the registry to discover the
 endpoints.

 Thanks,
 Hiranya


> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:
>
>> I'm more concerned about getting this to work on Stratos. UDP will not
>> work in that case. So, managed mode should be sufficient for us. Can you
>> advice us on how to set this up on Stratos?
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:
>>>
 Hi folks,
 $subject

 Can we use this to run our sample Acme shopping cart application on
 Stratos? Please note that we need to have this running before the 
 Stratos
 1.0 release.

>>>
>>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>>> parameter. Does Stratos allow that? If not we need to develop some sort 
>>> of a
>>> UI to enable the user to do that. In GReg and ESB it's pretty much 
>>> enabled
>>> out of the box.
>>>
>>> Also please note that we only support the managed mode as of now.
>>> Work for the adhoc mode is now underway. Adhoc mode requires UDP 
>>> multicast
>>> capabilities. So as a first step I have modified the UDP transpo

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:

> Where is the client library? We can make it part of the axis2-client
> component which we include in webapps.


Client API is available in the org.wso2.carbon.discovery.core component.
This component is shipped with WSAS, ESB, GReg and DS by default. I think MS
also ships it out.

Thanks,
Hiranya


>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>>
>>> Yes we can do that. So the endpoints have to be published into the
>>> tenants' Governace registry space. Adding parameters to tenants' AxisConfig
>>> can be done by providing an implementation of
>>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
>>> the parameter in the createdAxisConfiguration method.
>>>
>>> So, going back to our sample,
>>>
>>> 1. How does the portal webapp find the service endpoints of the Product &
>>> Purchasing proxy services?
>>>
>>
>> The webapp should use the WS-D client API to discover the necessary
>> endpoints
>>
>>
>>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>>
>>
>> Task implementation should also use the WS-D client API. Since tasks are
>> custom developed Java code, we cannot make WS-D support tasks. Instead,
>> tasks should be written in a WS-D aware manner.
>>
>>
>>> 3. How does the ESB find out the endpoint of the FinanceConnector
>>> service?
>>>
>>
>> ESB UI provides the necessary means to discover endpoints and create proxy
>> services on them
>>
>>
>>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>>> service?
>>>
>>
>> We don't support WS-D in gadgets yet. This is something I discussed with
>> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
>> and gadgets should be able to discover other endpoints and gadgets using
>> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
>> client API. Anyway this is for the future. I need to talk this through with
>> the GS team.
>>
>>
>>> 5. How does the BPEL process find out the endpoints of the ShoppingCart
>>> data service?
>>>
>>
>> We don't support BPEL yet either. And to be honest I'm not very familiar
>> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
>> help me out here. Does BPS use any Axis2 client stuff to talk to the service
>> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
>> the client API depending on how it's done).
>>
>>
>>> I think there should be a way to have logical references to endpoints.
>>> Does your implementation provide this?
>>>
>>
>> This is provided by the WS-D specs. An endpoint is identified by a
>> platform-wide unique identifier. Each endpoint is also associated with a set
>> of user defined scopes and types that can be used to index and search
>> endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Azeez
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka 
>>> wrote:
>>>
 Hi Azeez,

 On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:

> It would be great if you could show us how to use WS-Discovery in our
> sample.


 Can we set parameters on the tenant AxisConfiguration? In a standalone
 Carbon we could edit the axis2.xml to do that. Is there some way to do the
 equivalent in Stratos?

 If we can get that done, then it's just a matter of enabling
 WS-Discovery in Stratos app server. It will start publishing service
 endpoints to GReg. Then the ESB can probe the registry to discover the
 endpoints.

 Thanks,
 Hiranya


> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:
>
>> I'm more concerned about getting this to work on Stratos. UDP will not
>> work in that case. So, managed mode should be sufficient for us. Can you
>> advice us on how to set this up on Stratos?
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:
>>>
 Hi folks,
 $subject

 Can we use this to run our sample Acme shopping cart application on
 Stratos? Please note that we need to have this running before the 
 Stratos
 1.0 release.

>>>
>>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>>> parameter. Does Stratos allow that? If not we need to develop some sort 
>>> of a
>>> UI to enable the user to do that. In GReg and ESB it's pretty much 
>>> enabled
>>> out of the box.
>>>
>>> Also please note that we only support the managed mode as of now.
>>> Work for the adhoc mode is now underway. Adhoc mode requires UDP 
>>> multicast
>>> capabilities. So as a first step I have m

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Waruna Ranasinghe]

On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:

>
>
> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>
>> Yes we can do that. So the endpoints have to be published into the
>> tenants' Governace registry space. Adding parameters to tenants' AxisConfig
>> can be done by providing an implementation of
>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
>> the parameter in the createdAxisConfiguration method.
>>
>> So, going back to our sample,
>>
>> 1. How does the portal webapp find the service endpoints of the Product &
>> Purchasing proxy services?
>>
>
> The webapp should use the WS-D client API to discover the necessary
> endpoints
>
>
>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>
>
> Task implementation should also use the WS-D client API. Since tasks are
> custom developed Java code, we cannot make WS-D support tasks. Instead,
> tasks should be written in a WS-D aware manner.
>
>
>> 3. How does the ESB find out the endpoint of the FinanceConnector service?
>>
>
> ESB UI provides the necessary means to discover endpoints and create proxy
> services on them
>
>
>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>> service?
>>
>
> We don't support WS-D in gadgets yet. This is something I discussed with
> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
> and gadgets should be able to discover other endpoints and gadgets using
> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
> client API. Anyway this is for the future. I need to talk this through with
> the GS team.
>
>
>> 5. How does the BPEL process find out the endpoints of the ShoppingCart
>> data service?
>>
>
> We don't support BPEL yet either. And to be honest I'm not very familiar
> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
> help me out here. Does BPS use any Axis2 client stuff to talk to the service
> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
> the client API depending on how it's done).
>
Yes, We use OperationClient to invoke external services.

Thanks,
Waruna

>
>
>> I think there should be a way to have logical references to endpoints.
>> Does your implementation provide this?
>>
>
> This is provided by the WS-D specs. An endpoint is identified by a
> platform-wide unique identifier. Each endpoint is also associated with a set
> of user defined scopes and types that can be used to index and search
> endpoints.
>
> Thanks,
> Hiranya
>
>
>>
>> Azeez
>>
>>
>>
>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka 
>> wrote:
>>
>>> Hi Azeez,
>>>
>>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:
>>>
 It would be great if you could show us how to use WS-Discovery in our
 sample.
>>>
>>>
>>> Can we set parameters on the tenant AxisConfiguration? In a standalone
>>> Carbon we could edit the axis2.xml to do that. Is there some way to do the
>>> equivalent in Stratos?
>>>
>>> If we can get that done, then it's just a matter of enabling WS-Discovery
>>> in Stratos app server. It will start publishing service endpoints to GReg.
>>> Then the ESB can probe the registry to discover the endpoints.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
 Azeez




 On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:

> I'm more concerned about getting this to work on Stratos. UDP will not
> work in that case. So, managed mode should be sufficient for us. Can you
> advice us on how to set this up on Stratos?
>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:
>>
>>> Hi folks,
>>> $subject
>>>
>>> Can we use this to run our sample Acme shopping cart application on
>>> Stratos? Please note that we need to have this running before the 
>>> Stratos
>>> 1.0 release.
>>>
>>
>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>> parameter. Does Stratos allow that? If not we need to develop some sort 
>> of a
>> UI to enable the user to do that. In GReg and ESB it's pretty much 
>> enabled
>> out of the box.
>>
>> Also please note that we only support the managed mode as of now. Work
>> for the adhoc mode is now underway. Adhoc mode requires UDP multicast
>> capabilities. So as a first step I have modified the UDP transport and
>> provided patches for that.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>
>>> Thanks
>>> --
>>> *Afkham Azeez*
>>> Senior Software Architect & Senior Manager; WSO2, Inc.;
>>> http://wso2.com,
>>> *
>>> *
>>> *Member; Apache Software Foundation; 
>>> **http://www.apache.org/*
>>> *
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

Where can I find some sample code on how to use this?

Azeez



On Wed, Sep 22, 2010 at 1:24 PM, Afkham Azeez  wrote:

> Where is the client library? We can make it part of the axis2-client
> component which we include in webapps.
>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>>
>>> Yes we can do that. So the endpoints have to be published into the
>>> tenants' Governace registry space. Adding parameters to tenants' AxisConfig
>>> can be done by providing an implementation of
>>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
>>> the parameter in the createdAxisConfiguration method.
>>>
>>> So, going back to our sample,
>>>
>>> 1. How does the portal webapp find the service endpoints of the Product &
>>> Purchasing proxy services?
>>>
>>
>> The webapp should use the WS-D client API to discover the necessary
>> endpoints
>>
>>
>>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>>
>>
>> Task implementation should also use the WS-D client API. Since tasks are
>> custom developed Java code, we cannot make WS-D support tasks. Instead,
>> tasks should be written in a WS-D aware manner.
>>
>>
>>> 3. How does the ESB find out the endpoint of the FinanceConnector
>>> service?
>>>
>>
>> ESB UI provides the necessary means to discover endpoints and create proxy
>> services on them
>>
>>
>>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>>> service?
>>>
>>
>> We don't support WS-D in gadgets yet. This is something I discussed with
>> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
>> and gadgets should be able to discover other endpoints and gadgets using
>> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
>> client API. Anyway this is for the future. I need to talk this through with
>> the GS team.
>>
>>
>>> 5. How does the BPEL process find out the endpoints of the ShoppingCart
>>> data service?
>>>
>>
>> We don't support BPEL yet either. And to be honest I'm not very familiar
>> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
>> help me out here. Does BPS use any Axis2 client stuff to talk to the service
>> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
>> the client API depending on how it's done).
>>
>>
>>> I think there should be a way to have logical references to endpoints.
>>> Does your implementation provide this?
>>>
>>
>> This is provided by the WS-D specs. An endpoint is identified by a
>> platform-wide unique identifier. Each endpoint is also associated with a set
>> of user defined scopes and types that can be used to index and search
>> endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Azeez
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka 
>>> wrote:
>>>
 Hi Azeez,

 On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:

> It would be great if you could show us how to use WS-Discovery in our
> sample.


 Can we set parameters on the tenant AxisConfiguration? In a standalone
 Carbon we could edit the axis2.xml to do that. Is there some way to do the
 equivalent in Stratos?

 If we can get that done, then it's just a matter of enabling
 WS-Discovery in Stratos app server. It will start publishing service
 endpoints to GReg. Then the ESB can probe the registry to discover the
 endpoints.

 Thanks,
 Hiranya


> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:
>
>> I'm more concerned about getting this to work on Stratos. UDP will not
>> work in that case. So, managed mode should be sufficient for us. Can you
>> advice us on how to set this up on Stratos?
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:
>>>
 Hi folks,
 $subject

 Can we use this to run our sample Acme shopping cart application on
 Stratos? Please note that we need to have this running before the 
 Stratos
 1.0 release.

>>>
>>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>>> parameter. Does Stratos allow that? If not we need to develop some sort 
>>> of a
>>> UI to enable the user to do that. In GReg and ESB it's pretty much 
>>> enabled
>>> out of the box.
>>>
>>> Also please note that we only support the managed mode as of now.
>>> Work for the adhoc mode is now underway. Adhoc mode requires UDP 
>>> multicast
>>> capabilities. So as a first step I have modified the UDP transport and
>>> provided patches for that.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

Where is the client library? We can make it part of the axis2-client
component which we include in webapps.

Azeez



On Wed, Sep 22, 2010 at 1:18 PM, Hiranya Jayathilaka wrote:

>
>
> On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:
>
>> Yes we can do that. So the endpoints have to be published into the
>> tenants' Governace registry space. Adding parameters to tenants' AxisConfig
>> can be done by providing an implementation of
>> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
>> the parameter in the createdAxisConfiguration method.
>>
>> So, going back to our sample,
>>
>> 1. How does the portal webapp find the service endpoints of the Product &
>> Purchasing proxy services?
>>
>
> The webapp should use the WS-D client API to discover the necessary
> endpoints
>
>
>> 2. How does the ESB task find out the endpoint of the BPEL service?
>>
>
> Task implementation should also use the WS-D client API. Since tasks are
> custom developed Java code, we cannot make WS-D support tasks. Instead,
> tasks should be written in a WS-D aware manner.
>
>
>> 3. How does the ESB find out the endpoint of the FinanceConnector service?
>>
>
> ESB UI provides the necessary means to discover endpoints and create proxy
> services on them
>
>
>> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
>> service?
>>
>
> We don't support WS-D in gadgets yet. This is something I discussed with
> Jonathan a few weeks back. We should be able to discover gadgets using WS-D
> and gadgets should be able to discover other endpoints and gadgets using
> WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
> client API. Anyway this is for the future. I need to talk this through with
> the GS team.
>
>
>> 5. How does the BPEL process find out the endpoints of the ShoppingCart
>> data service?
>>
>
> We don't support BPEL yet either. And to be honest I'm not very familiar
> with BPEL to think about a way to support WS-D in BPS. May be Waruna can
> help me out here. Does BPS use any Axis2 client stuff to talk to the service
> endpoints? If so we may be able to use the Axis2 client module for WS-D (or
> the client API depending on how it's done).
>
>
>> I think there should be a way to have logical references to endpoints.
>> Does your implementation provide this?
>>
>
> This is provided by the WS-D specs. An endpoint is identified by a
> platform-wide unique identifier. Each endpoint is also associated with a set
> of user defined scopes and types that can be used to index and search
> endpoints.
>
> Thanks,
> Hiranya
>
>
>>
>> Azeez
>>
>>
>>
>> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka 
>> wrote:
>>
>>> Hi Azeez,
>>>
>>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:
>>>
 It would be great if you could show us how to use WS-Discovery in our
 sample.
>>>
>>>
>>> Can we set parameters on the tenant AxisConfiguration? In a standalone
>>> Carbon we could edit the axis2.xml to do that. Is there some way to do the
>>> equivalent in Stratos?
>>>
>>> If we can get that done, then it's just a matter of enabling WS-Discovery
>>> in Stratos app server. It will start publishing service endpoints to GReg.
>>> Then the ESB can probe the registry to discover the endpoints.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>
 Azeez




 On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:

> I'm more concerned about getting this to work on Stratos. UDP will not
> work in that case. So, managed mode should be sufficient for us. Can you
> advice us on how to set this up on Stratos?
>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez wrote:
>>
>>> Hi folks,
>>> $subject
>>>
>>> Can we use this to run our sample Acme shopping cart application on
>>> Stratos? Please note that we need to have this running before the 
>>> Stratos
>>> 1.0 release.
>>>
>>
>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>> parameter. Does Stratos allow that? If not we need to develop some sort 
>> of a
>> UI to enable the user to do that. In GReg and ESB it's pretty much 
>> enabled
>> out of the box.
>>
>> Also please note that we only support the managed mode as of now. Work
>> for the adhoc mode is now underway. Adhoc mode requires UDP multicast
>> capabilities. So as a first step I have modified the UDP transport and
>> provided patches for that.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>
>>> Thanks
>>> --
>>> *Afkham Azeez*
>>> Senior Software Architect & Senior Manager; WSO2, Inc.;
>>> http://wso2.com,
>>> *
>>> *
>>> *Member; Apache Software Foundation; 
>>> **http://www.apache.org/*
>>> *
>>> email: *

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez  wrote:

> Yes we can do that. So the endpoints have to be published into the tenants'
> Governace registry space. Adding parameters to tenants' AxisConfig can be
> done by providing an implementation of
> the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
> the parameter in the createdAxisConfiguration method.
>
> So, going back to our sample,
>
> 1. How does the portal webapp find the service endpoints of the Product &
> Purchasing proxy services?
>

The webapp should use the WS-D client API to discover the necessary
endpoints


> 2. How does the ESB task find out the endpoint of the BPEL service?
>

Task implementation should also use the WS-D client API. Since tasks are
custom developed Java code, we cannot make WS-D support tasks. Instead,
tasks should be written in a WS-D aware manner.


> 3. How does the ESB find out the endpoint of the FinanceConnector service?
>

ESB UI provides the necessary means to discover endpoints and create proxy
services on them


> 4. How do the Gadgets find out the endpoints of the ShoppingCart data
> service?
>

We don't support WS-D in gadgets yet. This is something I discussed with
Jonathan a few weeks back. We should be able to discover gadgets using WS-D
and gadgets should be able to discover other endpoints and gadgets using
WS-D. We'll probably have to write some JavaScript library wrapping the WS-D
client API. Anyway this is for the future. I need to talk this through with
the GS team.


> 5. How does the BPEL process find out the endpoints of the ShoppingCart
> data service?
>

We don't support BPEL yet either. And to be honest I'm not very familiar
with BPEL to think about a way to support WS-D in BPS. May be Waruna can
help me out here. Does BPS use any Axis2 client stuff to talk to the service
endpoints? If so we may be able to use the Axis2 client module for WS-D (or
the client API depending on how it's done).


> I think there should be a way to have logical references to endpoints. Does
> your implementation provide this?
>

This is provided by the WS-D specs. An endpoint is identified by a
platform-wide unique identifier. Each endpoint is also associated with a set
of user defined scopes and types that can be used to index and search
endpoints.

Thanks,
Hiranya


>
> Azeez
>
>
>
> On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka wrote:
>
>> Hi Azeez,
>>
>> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:
>>
>>> It would be great if you could show us how to use WS-Discovery in our
>>> sample.
>>
>>
>> Can we set parameters on the tenant AxisConfiguration? In a standalone
>> Carbon we could edit the axis2.xml to do that. Is there some way to do the
>> equivalent in Stratos?
>>
>> If we can get that done, then it's just a matter of enabling WS-Discovery
>> in Stratos app server. It will start publishing service endpoints to GReg.
>> Then the ESB can probe the registry to discover the endpoints.
>>
>> Thanks,
>> Hiranya
>>
>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:
>>>
 I'm more concerned about getting this to work on Stratos. UDP will not
 work in that case. So, managed mode should be sufficient for us. Can you
 advice us on how to set this up on Stratos?

 Azeez




 On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka >>> > wrote:

>
>
> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:
>
>> Hi folks,
>> $subject
>>
>> Can we use this to run our sample Acme shopping cart application on
>> Stratos? Please note that we need to have this running before the Stratos
>> 1.0 release.
>>
>
> In WSAS and DS this should be enabled by setting an AxisConfiguration
> parameter. Does Stratos allow that? If not we need to develop some sort 
> of a
> UI to enable the user to do that. In GReg and ESB it's pretty much enabled
> out of the box.
>
> Also please note that we only support the managed mode as of now. Work
> for the adhoc mode is now underway. Adhoc mode requires UDP multicast
> capabilities. So as a first step I have modified the UDP transport and
> provided patches for that.
>
> Thanks,
> Hiranya
>
>
>>
>>
>> Thanks
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.;
>> http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>>
>> ___
>>>

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

Yes we can do that. So the endpoints have to be published into the tenants'
Governace registry space. Adding parameters to tenants' AxisConfig can be
done by providing an implementation of
the org.wso2.carbon.utils.PreAxisConfigurationPopulationObserver and adding
the parameter in the createdAxisConfiguration method.

So, going back to our sample,

1. How does the portal webapp find the service endpoints of the Product &
Purchasing proxy services?
2. How does the ESB task find out the endpoint of the BPEL service?
3. How does the ESB find out the endpoint of the FinanceConnector service?
4. How do the Gadgets find out the endpoints of the ShoppingCart data
service?
5. How does the BPEL process find out the endpoints of the ShoppingCart data
service?

I think there should be a way to have logical references to endpoints. Does
your implementation provide this?

Azeez


On Wed, Sep 22, 2010 at 12:14 PM, Hiranya Jayathilaka wrote:

> Hi Azeez,
>
> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:
>
>> It would be great if you could show us how to use WS-Discovery in our
>> sample.
>
>
> Can we set parameters on the tenant AxisConfiguration? In a standalone
> Carbon we could edit the axis2.xml to do that. Is there some way to do the
> equivalent in Stratos?
>
> If we can get that done, then it's just a matter of enabling WS-Discovery
> in Stratos app server. It will start publishing service endpoints to GReg.
> Then the ESB can probe the registry to discover the endpoints.
>
> Thanks,
> Hiranya
>
>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:
>>
>>> I'm more concerned about getting this to work on Stratos. UDP will not
>>> work in that case. So, managed mode should be sufficient for us. Can you
>>> advice us on how to set this up on Stratos?
>>>
>>> Azeez
>>>
>>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:

> Hi folks,
> $subject
>
> Can we use this to run our sample Acme shopping cart application on
> Stratos? Please note that we need to have this running before the Stratos
> 1.0 release.
>

 In WSAS and DS this should be enabled by setting an AxisConfiguration
 parameter. Does Stratos allow that? If not we need to develop some sort of 
 a
 UI to enable the user to do that. In GReg and ESB it's pretty much enabled
 out of the box.

 Also please note that we only support the managed mode as of now. Work
 for the adhoc mode is now underway. Adhoc mode requires UDP multicast
 capabilities. So as a first step I have modified the UDP transport and
 provided patches for that.

 Thanks,
 Hiranya


>
>
> Thanks
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.;
> http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
>
> ___
> Stratos-dev mailing list
> stratos-...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
>


 --
 Hiranya Jayathilaka
 Senior Software Engineer;
 WSO2 Inc.;  http://wso2.org
 E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
 Blog: http://techfeast-hiranya.blogspot.com

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
>>> ,
>>> *
>>> *
>>> *Member; Apache Software Foundation; 
>>> **http://www.apache.org/*
>>> *
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> B

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

Hi Azeez,

On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez  wrote:

> It would be great if you could show us how to use WS-Discovery in our
> sample.


Can we set parameters on the tenant AxisConfiguration? In a standalone
Carbon we could edit the axis2.xml to do that. Is there some way to do the
equivalent in Stratos?

If we can get that done, then it's just a matter of enabling WS-Discovery in
Stratos app server. It will start publishing service endpoints to GReg. Then
the ESB can probe the registry to discover the endpoints.

Thanks,
Hiranya


> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:
>
>> I'm more concerned about getting this to work on Stratos. UDP will not
>> work in that case. So, managed mode should be sufficient for us. Can you
>> advice us on how to set this up on Stratos?
>>
>> Azeez
>>
>>
>>
>>
>> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:
>>>
 Hi folks,
 $subject

 Can we use this to run our sample Acme shopping cart application on
 Stratos? Please note that we need to have this running before the Stratos
 1.0 release.

>>>
>>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>>> parameter. Does Stratos allow that? If not we need to develop some sort of a
>>> UI to enable the user to do that. In GReg and ESB it's pretty much enabled
>>> out of the box.
>>>
>>> Also please note that we only support the managed mode as of now. Work
>>> for the adhoc mode is now underway. Adhoc mode requires UDP multicast
>>> capabilities. So as a first step I have modified the UDP transport and
>>> provided patches for that.
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>


 Thanks
 --
 *Afkham Azeez*
 Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
 ,
 *
 *
 *Member; Apache Software Foundation; 
 **http://www.apache.org/*
 *
 email: **az...@wso2.com* * cell: +94 77 3320919
 blog: **http://blog.afkham.org* *
 twitter: 
 **http://twitter.com/afkham_azeez*
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*



 ___
 Stratos-dev mailing list
 stratos-...@wso2.org
 https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev


>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Senior Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

It would be great if you could show us how to use WS-Discovery in our
sample.

Azeez



On Wed, Sep 22, 2010 at 11:38 AM, Afkham Azeez  wrote:

> I'm more concerned about getting this to work on Stratos. UDP will not work
> in that case. So, managed mode should be sufficient for us. Can you advice
> us on how to set this up on Stratos?
>
> Azeez
>
>
>
>
> On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:
>>
>>> Hi folks,
>>> $subject
>>>
>>> Can we use this to run our sample Acme shopping cart application on
>>> Stratos? Please note that we need to have this running before the Stratos
>>> 1.0 release.
>>>
>>
>> In WSAS and DS this should be enabled by setting an AxisConfiguration
>> parameter. Does Stratos allow that? If not we need to develop some sort of a
>> UI to enable the user to do that. In GReg and ESB it's pretty much enabled
>> out of the box.
>>
>> Also please note that we only support the managed mode as of now. Work for
>> the adhoc mode is now underway. Adhoc mode requires UDP multicast
>> capabilities. So as a first step I have modified the UDP transport and
>> provided patches for that.
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>
>>> Thanks
>>> --
>>> *Afkham Azeez*
>>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
>>> ,
>>> *
>>> *
>>> *Member; Apache Software Foundation; 
>>> **http://www.apache.org/*
>>> *
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>>
>>> ___
>>> Stratos-dev mailing list
>>> stratos-...@wso2.org
>>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

I'm more concerned about getting this to work on Stratos. UDP will not work
in that case. So, managed mode should be sufficient for us. Can you advice
us on how to set this up on Stratos?

Azeez



On Wed, Sep 22, 2010 at 11:36 AM, Hiranya Jayathilaka wrote:

>
>
> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:
>
>> Hi folks,
>> $subject
>>
>> Can we use this to run our sample Acme shopping cart application on
>> Stratos? Please note that we need to have this running before the Stratos
>> 1.0 release.
>>
>
> In WSAS and DS this should be enabled by setting an AxisConfiguration
> parameter. Does Stratos allow that? If not we need to develop some sort of a
> UI to enable the user to do that. In GReg and ESB it's pretty much enabled
> out of the box.
>
> Also please note that we only support the managed mode as of now. Work for
> the adhoc mode is now underway. Adhoc mode requires UDP multicast
> capabilities. So as a first step I have modified the UDP transport and
> provided patches for that.
>
> Thanks,
> Hiranya
>
>
>>
>>
>> Thanks
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>>
>> ___
>> Stratos-dev mailing list
>> stratos-...@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Hiranya Jayathilaka]

On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:

> Hi folks,
> $subject
>
> Can we use this to run our sample Acme shopping cart application on
> Stratos? Please note that we need to have this running before the Stratos
> 1.0 release.
>

In WSAS and DS this should be enabled by setting an AxisConfiguration
parameter. Does Stratos allow that? If not we need to develop some sort of a
UI to enable the user to do that. In GReg and ESB it's pretty much enabled
out of the box.

Also please note that we only support the managed mode as of now. Work for
the adhoc mode is now underway. Adhoc mode requires UDP multicast
capabilities. So as a first step I have modified the UDP transport and
provided patches for that.

Thanks,
Hiranya


>
>
> Thanks
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
>
> ___
> Stratos-dev mailing list
> stratos-...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
>


-- 
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Afkham Azeez]

Yeah, one problem we noticed during the Acme shopping cart sample
development was that the endpoints need to be configured in multiple places.
It would have been great if endpoints were referred to using a logical
identifier, and they could be configured in the Governance registry.

Azeez



On Wed, Sep 22, 2010 at 11:25 AM, Samisa Abeysinghe  wrote:

> Also, what are the  relationships between discovery endpoint unification?
> How much of that we plan to have by Stratos 1.0?
>
> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:
>
>> Hi folks,
>> $subject
>>
>> Can we use this to run our sample Acme shopping cart application on
>> Stratos? Please note that we need to have this running before the Stratos
>> 1.0 release.
>>
>>
>> Thanks
>> --
>> *Afkham Azeez*
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> *
>> *
>> *Member; Apache Software Foundation; 
>> **http://www.apache.org/*
>> *
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>>
>> ___
>> Stratos-dev mailing list
>> stratos-...@wso2.org
>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>>
>> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>
>


-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*
*
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?

[Samisa Abeysinghe]

Also, what are the  relationships between discovery endpoint unification?
How much of that we plan to have by Stratos 1.0?

On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez  wrote:

> Hi folks,
> $subject
>
> Can we use this to run our sample Acme shopping cart application on
> Stratos? Please note that we need to have this running before the Stratos
> 1.0 release.
>
>
> Thanks
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; 
> **http://www.apache.org/*
> *
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
>
> ___
> Stratos-dev mailing list
> stratos-...@wso2.org
> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev