You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Ciaran <ci...@gmail.com> on 2009/04/02 08:22:02 UTC

'enableSharing' in deploy.xml

Hi folks,
I notice that Alexis references an 'enableSharing' element in deploy.xml in
this issue comment, but I can't find any definition in the documentation as
to what this element actually means, can anyone explain why I might want
this on or off for my deployments ?
Sorry folks! :)
 -cj.


On Wed, Apr 1, 2009 at 11:50 PM, Alexis Midon (JIRA) <ji...@apache.org>wrote:

>
>    [
> https://issues.apache.org/jira/browse/ODE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694809#action_12694809]
>
> Alexis Midon commented on ODE-568:
> ----------------------------------
>
> It appears we don't need the unique name introduced by ODE-345 as the key
> of the service map.
>
> Actually, if a service is shared by multiple processes (i.e.
> <enableSharing/> set in deploy.xml), only one single instance of ODEService
> is created. [1]
> In other cases, the assumption that different processes hava different
> service name/port name is valid.
>
> So {service name, port name} is a valid key for the service map.
>
>
> [1]
> http://fisheye6.atlassian.com/browse/ode/branches/APACHE_ODE_1.X/bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java?r=APACHE_ODE_1.X#l561
>
> > Undeploying a process does not remove corresponding service from ODE
> axis2
> >
> --------------------------------------------------------------------------
> >
> >                 Key: ODE-568
> >                 URL: https://issues.apache.org/jira/browse/ODE-568
> >             Project: ODE
> >          Issue Type: Bug
> >          Components: Axis2 Integration
> >    Affects Versions: 1.3
> >            Reporter: Alexis Midon
> >            Assignee: Alexis Midon
> >
> > Undeploying a process does not remove corresponding service from axis2
> > You can see that webservice in Axis2 service list view.
> > http://localhost:8080/ode/axis2-admin/listService
> > It requires login. Default login details: admin/axis2
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Re: 'enableSharing' in deploy.xml

Posted by Alex Boisvert <bo...@intalio.com>.
It relates to publish-subscribe semantic on endpoints.

https://issues.apache.org/jira/browse/ODE-364

Karthick, could you update the documentation at
http://ode.apache.org/user-guide.html#UserGuide-DeploymentDescriptor ?

thanks,
alex


On Wed, Apr 1, 2009 at 11:22 PM, Ciaran <ci...@gmail.com> wrote:

> Hi folks,
> I notice that Alexis references an 'enableSharing' element in deploy.xml in
> this issue comment, but I can't find any definition in the documentation as
> to what this element actually means, can anyone explain why I might want
> this on or off for my deployments ?
> Sorry folks! :)
>  -cj.
>
>
> On Wed, Apr 1, 2009 at 11:50 PM, Alexis Midon (JIRA) <jira@apache.org
> >wrote:
>
> >
> >    [
> >
> https://issues.apache.org/jira/browse/ODE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694809#action_12694809
> ]
> >
> > Alexis Midon commented on ODE-568:
> > ----------------------------------
> >
> > It appears we don't need the unique name introduced by ODE-345 as the key
> > of the service map.
> >
> > Actually, if a service is shared by multiple processes (i.e.
> > <enableSharing/> set in deploy.xml), only one single instance of
> ODEService
> > is created. [1]
> > In other cases, the assumption that different processes hava different
> > service name/port name is valid.
> >
> > So {service name, port name} is a valid key for the service map.
> >
> >
> > [1]
> >
> http://fisheye6.atlassian.com/browse/ode/branches/APACHE_ODE_1.X/bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java?r=APACHE_ODE_1.X#l561
> >
> > > Undeploying a process does not remove corresponding service from ODE
> > axis2
> > >
> >
> --------------------------------------------------------------------------
> > >
> > >                 Key: ODE-568
> > >                 URL: https://issues.apache.org/jira/browse/ODE-568
> > >             Project: ODE
> > >          Issue Type: Bug
> > >          Components: Axis2 Integration
> > >    Affects Versions: 1.3
> > >            Reporter: Alexis Midon
> > >            Assignee: Alexis Midon
> > >
> > > Undeploying a process does not remove corresponding service from axis2
> > > You can see that webservice in Axis2 service list view.
> > > http://localhost:8080/ode/axis2-admin/listService
> > > It requires login. Default login details: admin/axis2
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >
>

Re: 'enableSharing' in deploy.xml

Posted by Ciaran <ci...@gmail.com>.
Thanks chaps :)
- cj.



On Thu, Apr 2, 2009 at 6:05 PM, Karthick Sankarachary <
sankarachary@intalio.com> wrote:

> Hi Ciaran,
>
> For more details on 'enableSharing', please take a look at
> this<http://issues.apache.org/jira/browse/ODE-364>issue. I will update
> the user guide to reflect this feature.
>
> Best Regards,
> Karthick Sankarachary
>
>
> On Wed, Apr 1, 2009 at 11:22 PM, Ciaran <ci...@gmail.com> wrote:
>
> > Hi folks,
> > I notice that Alexis references an 'enableSharing' element in deploy.xml
> in
> > this issue comment, but I can't find any definition in the documentation
> as
> > to what this element actually means, can anyone explain why I might want
> > this on or off for my deployments ?
> > Sorry folks! :)
> >  -cj.
> >
> >
> > On Wed, Apr 1, 2009 at 11:50 PM, Alexis Midon (JIRA) <jira@apache.org
> > >wrote:
> >
> > >
> > >    [
> > >
> >
> https://issues.apache.org/jira/browse/ODE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694809#action_12694809
> > ]
> > >
> > > Alexis Midon commented on ODE-568:
> > > ----------------------------------
> > >
> > > It appears we don't need the unique name introduced by ODE-345 as the
> key
> > > of the service map.
> > >
> > > Actually, if a service is shared by multiple processes (i.e.
> > > <enableSharing/> set in deploy.xml), only one single instance of
> > ODEService
> > > is created. [1]
> > > In other cases, the assumption that different processes hava different
> > > service name/port name is valid.
> > >
> > > So {service name, port name} is a valid key for the service map.
> > >
> > >
> > > [1]
> > >
> >
> http://fisheye6.atlassian.com/browse/ode/branches/APACHE_ODE_1.X/bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java?r=APACHE_ODE_1.X#l561
> > >
> > > > Undeploying a process does not remove corresponding service from ODE
> > > axis2
> > > >
> > >
> >
> --------------------------------------------------------------------------
> > > >
> > > >                 Key: ODE-568
> > > >                 URL: https://issues.apache.org/jira/browse/ODE-568
> > > >             Project: ODE
> > > >          Issue Type: Bug
> > > >          Components: Axis2 Integration
> > > >    Affects Versions: 1.3
> > > >            Reporter: Alexis Midon
> > > >            Assignee: Alexis Midon
> > > >
> > > > Undeploying a process does not remove corresponding service from
> axis2
> > > > You can see that webservice in Axis2 service list view.
> > > > http://localhost:8080/ode/axis2-admin/listService
> > > > It requires login. Default login details: admin/axis2
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the issue online.
> > >
> > >
> >
>

Re: 'enableSharing' in deploy.xml

Posted by Karthick Sankarachary <sa...@intalio.com>.
Hi Ciaran,

For more details on 'enableSharing', please take a look at
this<http://issues.apache.org/jira/browse/ODE-364>issue. I will update
the user guide to reflect this feature.

Best Regards,
Karthick Sankarachary


On Wed, Apr 1, 2009 at 11:22 PM, Ciaran <ci...@gmail.com> wrote:

> Hi folks,
> I notice that Alexis references an 'enableSharing' element in deploy.xml in
> this issue comment, but I can't find any definition in the documentation as
> to what this element actually means, can anyone explain why I might want
> this on or off for my deployments ?
> Sorry folks! :)
>  -cj.
>
>
> On Wed, Apr 1, 2009 at 11:50 PM, Alexis Midon (JIRA) <jira@apache.org
> >wrote:
>
> >
> >    [
> >
> https://issues.apache.org/jira/browse/ODE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694809#action_12694809
> ]
> >
> > Alexis Midon commented on ODE-568:
> > ----------------------------------
> >
> > It appears we don't need the unique name introduced by ODE-345 as the key
> > of the service map.
> >
> > Actually, if a service is shared by multiple processes (i.e.
> > <enableSharing/> set in deploy.xml), only one single instance of
> ODEService
> > is created. [1]
> > In other cases, the assumption that different processes hava different
> > service name/port name is valid.
> >
> > So {service name, port name} is a valid key for the service map.
> >
> >
> > [1]
> >
> http://fisheye6.atlassian.com/browse/ode/branches/APACHE_ODE_1.X/bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java?r=APACHE_ODE_1.X#l561
> >
> > > Undeploying a process does not remove corresponding service from ODE
> > axis2
> > >
> >
> --------------------------------------------------------------------------
> > >
> > >                 Key: ODE-568
> > >                 URL: https://issues.apache.org/jira/browse/ODE-568
> > >             Project: ODE
> > >          Issue Type: Bug
> > >          Components: Axis2 Integration
> > >    Affects Versions: 1.3
> > >            Reporter: Alexis Midon
> > >            Assignee: Alexis Midon
> > >
> > > Undeploying a process does not remove corresponding service from axis2
> > > You can see that webservice in Axis2 service list view.
> > > http://localhost:8080/ode/axis2-admin/listService
> > > It requires login. Default login details: admin/axis2
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the issue online.
> >
> >
>