On Wed, Sep 22, 2010 at 12:44 PM, Afkham Azeez <[email protected]> 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 <[email protected]>wrote: > >> Hi Azeez, >> >> On Wed, Sep 22, 2010 at 12:00 PM, Afkham Azeez <[email protected]> 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 <[email protected]> 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 <[email protected] >>>> > wrote: >>>> >>>>> >>>>> >>>>> On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez <[email protected]> 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/*<http://www.apache.org/> >>>>>> * >>>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>> twitter: >>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>> * >>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>> * >>>>>> * >>>>>> *Lean . Enterprise . Middleware* >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Stratos-dev mailing list >>>>>> [email protected] >>>>>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Hiranya Jayathilaka >>>>> Senior Software Engineer; >>>>> WSO2 Inc.; http://wso2.org >>>>> E-mail: [email protected]; 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/*<http://www.apache.org/> >>>> * >>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<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/*<http://www.apache.org/> >>> * >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<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: [email protected]; 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/*<http://www.apache.org/> > * > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<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: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
