You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by do...@yahoo.de on 2006/02/07 13:07:56 UTC
[Axis2] application scope
Hello,
trying to deploy some services under the use of the
attribute scope="application" at the <service>-tag in
services.xml, I noticed that this setting of the scope
doesn't work in Axis2 0.94. The only correct working
scope is the scope="transport". Are there any knows
bugs? I thought that this application scope setting
worked well, using release 0.93...
Thanks Ted
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [Axis2] application scope
Posted by do...@yahoo.de.
... so please have a look to this failure as well (see
attachement for details), this appears after excluding
the perf tests and running 'maven war' (maven 1.02,
jdk1.5)
Thanks Ted
--- Davanum Srinivas <da...@gmail.com> schrieb:
> Guys!! i'll fix this today. Patience please :)
>
> -- dims
>
> On 2/8/06, Ajith Ranabahu <aj...@gmail.com>
> wrote:
> > oooops - You seem to use JDK 1.5 !, We've been
> told about this problem
> > in JDK 1.5 and still trying to find a solution.
> > For the build, exclude the perf tests in the
> integration module.
> > (look for the project.xml inside the integration
> folder and edit the
> > excludes under build/unittests/excludes)
> >
> > On 2/8/06, donnerdrummel2000-mailing@yahoo.de
> > <do...@yahoo.de> wrote:
> > > Hi Deepal,
> > >
> > > sorry to say that, but the build failed even
> today
> > > (using maven war). For more detail see
> attachement,
> > > maybe this will help you to fix an other bug or
> giving
> > > me a hint what i did wrong.
> > >
> > > Thank you,
> > > Ted
> > > --- Deepal Jayasinghe <de...@opensource.lk>
> schrieb:
> > >
> > > > Hi Ted;
> > > >
> > > > I dont think maven war goal will fail now ,
> there
> > > > was a bug and we have
> > > > fixed that , try and see :)
> > > >
> > > > donnerdrummel2000-mailing@yahoo.de wrote:
> > > >
> > > > >Wow, Deepal this was realy one of the
> quickest
> > > > replys
> > > > >I got! So I'll try to build the source but
> since
> > > > some
> > > > >days I've problems to do this successfuly.
> Can you
> > > > >please give me a hint to build the *.war
> without
> > > > >running into an build failure.
> > > > >
> > > > >Thanks a lot
> > > > >Ted
> > > > >--- Deepal Jayasinghe <de...@opensource.lk>
> > > > schrieb:
> > > > >
> > > > >
> > > > >
> > > > >>I understood the problem , and I just fixed
> that
> > > > :)
> > > > >>
> > > > >>if you can get Axis2 source update , then
> you will
> > > > >>be able to get the
> > > > >>correct behavior , and you do not need to
> send the
> > > > >>service group id , if
> > > > >>you deploy the service in application scope.
> > > > >>
> > > > >>donnerdrummel2000-mailing@yahoo.de wrote:
> > > > >>
> > > > >>
> > > > >>
> > > > >>>Hi Deepal,
> > > > >>>
> > > > >>>first at all, thanks for your reply. Okay,
> I'll
> > > > try
> > > > >>>
> > > > >>>
> > > > >>to
> > > > >>
> > > > >>
> > > > >>>clarify the 'it does not work'. To test
> this
> > > > >>>
> > > > >>>
> > > > >>scoping
> > > > >>
> > > > >>
> > > > >>>feature for the 0.94 release I used a
> simple
> > > > >>>
> > > > >>>
> > > > >>Service
> > > > >>
> > > > >>
> > > > >>>which increases an integer value at every
> call
> > > > and
> > > > >>>returns this value. After deployment under
> the
> > > > >>><service scope="application">-setting it
> does not
> > > > >>>
> > > > >>>
> > > > >>work
> > > > >>
> > > > >>
> > > > >>>wich means it returns for every request a
> '1' but
> > > > >>>
> > > > >>>
> > > > >>it
> > > > >>
> > > > >>
> > > > >>>should be for 3 request '1','2','3'...
> > > > >>>The only way to get this behavior is to
> deploy
> > > > the
> > > > >>>service with the scope="transport" setting.
> > > > >>>
> > > > >>>You said that there is a usage of a service
> group
> > > > >>>
> > > > >>>
> > > > >>ID
> > > > >>
> > > > >>
> > > > >>>for the intern handling of some of this
> scope
> > > > >>>
> > > > >>>
> > > > >>types.
> > > > >>
> > > > >>
> > > > >>>Does this mean, that I've to deploy my
> single
> > > > >>>Countservice as a service group to get all
> the
> > > > >>>
> > > > >>>
> > > > >>scoping
> > > > >>
> > > > >>
> > > > >>>features to work?
> > > > >>>
> > > > >>>Thanks Ted
> > > > >>>
> > > > >>>--- Deepal Jayasinghe
> <de...@opensource.lk>
> > > > wrote:
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>Hi Ted;
> > > > >>>
> > > > >>>what do u mean by that does not work ? , I
> > > > >>>
> > > > >>>
> > > > >>recently
> > > > >>
> > > > >>
> > > > >>>changed scope
> > > > >>>handling , and I hope that should work.
> > > > >>>
> > > > >>>and that work as follows ,
> > > > >>> 1. If you deploy a service under the
> scope
> > > > >>>"request" , then there
> > > > >>>wont be any sessions management even if you
> send
> > > > >>>
> > > > >>>
> > > > >>the
> > > > >>
> > > > >>
> > > > >>>service group ID
> > > > >>>back (we mange session using ServiceGroup
> ID)
> > > > >>> 2. If you deploy a service in the
> transport
> > > > >>>session scope , then the
> > > > >>>there will be session management using
> transport
> > > > >>>cookies and there
> > > > >>>will be only one instance of service impl
> class
> > > > >>>
> > > > >>>
> > > > >>for
> > > > >>
> > > > >>
> > > > >>>that transport
> > > > >>>session.
> > > > >>> 3. If you deploy a service in scope of
> SOAP
> > > > >>>
>
=== message truncated ===
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [Axis2] application scope
Posted by Davanum Srinivas <da...@gmail.com>.
Guys!! i'll fix this today. Patience please :)
-- dims
On 2/8/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> oooops - You seem to use JDK 1.5 !, We've been told about this problem
> in JDK 1.5 and still trying to find a solution.
> For the build, exclude the perf tests in the integration module.
> (look for the project.xml inside the integration folder and edit the
> excludes under build/unittests/excludes)
>
> On 2/8/06, donnerdrummel2000-mailing@yahoo.de
> <do...@yahoo.de> wrote:
> > Hi Deepal,
> >
> > sorry to say that, but the build failed even today
> > (using maven war). For more detail see attachement,
> > maybe this will help you to fix an other bug or giving
> > me a hint what i did wrong.
> >
> > Thank you,
> > Ted
> > --- Deepal Jayasinghe <de...@opensource.lk> schrieb:
> >
> > > Hi Ted;
> > >
> > > I dont think maven war goal will fail now , there
> > > was a bug and we have
> > > fixed that , try and see :)
> > >
> > > donnerdrummel2000-mailing@yahoo.de wrote:
> > >
> > > >Wow, Deepal this was realy one of the quickest
> > > replys
> > > >I got! So I'll try to build the source but since
> > > some
> > > >days I've problems to do this successfuly. Can you
> > > >please give me a hint to build the *.war without
> > > >running into an build failure.
> > > >
> > > >Thanks a lot
> > > >Ted
> > > >--- Deepal Jayasinghe <de...@opensource.lk>
> > > schrieb:
> > > >
> > > >
> > > >
> > > >>I understood the problem , and I just fixed that
> > > :)
> > > >>
> > > >>if you can get Axis2 source update , then you will
> > > >>be able to get the
> > > >>correct behavior , and you do not need to send the
> > > >>service group id , if
> > > >>you deploy the service in application scope.
> > > >>
> > > >>donnerdrummel2000-mailing@yahoo.de wrote:
> > > >>
> > > >>
> > > >>
> > > >>>Hi Deepal,
> > > >>>
> > > >>>first at all, thanks for your reply. Okay, I'll
> > > try
> > > >>>
> > > >>>
> > > >>to
> > > >>
> > > >>
> > > >>>clarify the 'it does not work'. To test this
> > > >>>
> > > >>>
> > > >>scoping
> > > >>
> > > >>
> > > >>>feature for the 0.94 release I used a simple
> > > >>>
> > > >>>
> > > >>Service
> > > >>
> > > >>
> > > >>>which increases an integer value at every call
> > > and
> > > >>>returns this value. After deployment under the
> > > >>><service scope="application">-setting it does not
> > > >>>
> > > >>>
> > > >>work
> > > >>
> > > >>
> > > >>>wich means it returns for every request a '1' but
> > > >>>
> > > >>>
> > > >>it
> > > >>
> > > >>
> > > >>>should be for 3 request '1','2','3'...
> > > >>>The only way to get this behavior is to deploy
> > > the
> > > >>>service with the scope="transport" setting.
> > > >>>
> > > >>>You said that there is a usage of a service group
> > > >>>
> > > >>>
> > > >>ID
> > > >>
> > > >>
> > > >>>for the intern handling of some of this scope
> > > >>>
> > > >>>
> > > >>types.
> > > >>
> > > >>
> > > >>>Does this mean, that I've to deploy my single
> > > >>>Countservice as a service group to get all the
> > > >>>
> > > >>>
> > > >>scoping
> > > >>
> > > >>
> > > >>>features to work?
> > > >>>
> > > >>>Thanks Ted
> > > >>>
> > > >>>--- Deepal Jayasinghe <de...@opensource.lk>
> > > wrote:
> > > >>>
> > > >>>
> > > >>>
> > > >>>Hi Ted;
> > > >>>
> > > >>>what do u mean by that does not work ? , I
> > > >>>
> > > >>>
> > > >>recently
> > > >>
> > > >>
> > > >>>changed scope
> > > >>>handling , and I hope that should work.
> > > >>>
> > > >>>and that work as follows ,
> > > >>> 1. If you deploy a service under the scope
> > > >>>"request" , then there
> > > >>>wont be any sessions management even if you send
> > > >>>
> > > >>>
> > > >>the
> > > >>
> > > >>
> > > >>>service group ID
> > > >>>back (we mange session using ServiceGroup ID)
> > > >>> 2. If you deploy a service in the transport
> > > >>>session scope , then the
> > > >>>there will be session management using transport
> > > >>>cookies and there
> > > >>>will be only one instance of service impl class
> > > >>>
> > > >>>
> > > >>for
> > > >>
> > > >>
> > > >>>that transport
> > > >>>session.
> > > >>> 3. If you deploy a service in scope of SOAP
> > > >>>
> > > >>>
> > > >>session
> > > >>
> > > >>
> > > >>>then you can
> > > >>>manage session using ServiceGroupID , but that
> > > >>>session will be removed
> > > >>>from the system if you did not touch the session
> > > >>>
> > > >>>
> > > >>for
> > > >>
> > > >>
> > > >>>about 30s. (there
> > > >>>will be only one instance of the service impl for
> > > >>>that session)
> > > >>>4. If you deploy service in application scope
> > > then
> > > >>>one can manage a
> > > >>>session using servicegroupID throughout the life
> > > >>>time of the
> > > >>>system.(there will be only one instance of the
> > > >>>service impl for that
> > > >>>session)
> > > >>>
> > > >>>and can you pls clarify what do you mean by it
> > > >>>
> > > >>>
> > > >>does
> > > >>
> > > >>
> > > >>>not work , so that
> > > >>>I can fix that
> > > >>>
> > > >>>donnerdrummel2000-mailing@yahoo.de wrote:
> > > >>>
> > > >>>
> > > >>>
> > > >>>>Hello,
> > > >>>>
> > > >>>>
> > > >>>>trying to deploy some services under the use of
> > > >>>>
> > > >>>>
> > > >>the
> > > >>
> > > >>
> > > >>>>attribute scope="application" at the
> > > >>>>
> > > >>>>
> > > >><service>-tag
> > > >>
> > > >>
> > > >>>in
> > > >>>
> > > >>>
> > > >>>
> > > >>>>services.xml, I noticed that this setting of the
> > > >>>>
> > > >>>>
> > >
> > === message truncated ===
> >
> >
> >
> >
> >
> >
> > ___________________________________________________________
> > Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
> >
> > BUILD FAILED
> > File...... C:\Dokumente und Einstellungen\t.israel\.maven\cache\maven-multiproje
> > ct-plugin-1.3.1\plugin.jelly
> > Element... maven:reactor
> > Line...... 217
> > Column.... 9
> > Unable to obtain goal [multiproject:install-callback] -- C:\axis2_nightly\module
> > s\integration\maven.xml:40:38: <ant:ant> Unexpected attribute "xmlns:xalan"
> > Total time: 12 minutes 10 seconds
> > Finished at: Wed Feb 08 11:35:24 CET 2006
> >
> >
>
>
> --
> Ajith Ranabahu
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] application scope
Posted by Ajith Ranabahu <aj...@gmail.com>.
oooops - You seem to use JDK 1.5 !, We've been told about this problem
in JDK 1.5 and still trying to find a solution.
For the build, exclude the perf tests in the integration module.
(look for the project.xml inside the integration folder and edit the
excludes under build/unittests/excludes)
On 2/8/06, donnerdrummel2000-mailing@yahoo.de
<do...@yahoo.de> wrote:
> Hi Deepal,
>
> sorry to say that, but the build failed even today
> (using maven war). For more detail see attachement,
> maybe this will help you to fix an other bug or giving
> me a hint what i did wrong.
>
> Thank you,
> Ted
> --- Deepal Jayasinghe <de...@opensource.lk> schrieb:
>
> > Hi Ted;
> >
> > I dont think maven war goal will fail now , there
> > was a bug and we have
> > fixed that , try and see :)
> >
> > donnerdrummel2000-mailing@yahoo.de wrote:
> >
> > >Wow, Deepal this was realy one of the quickest
> > replys
> > >I got! So I'll try to build the source but since
> > some
> > >days I've problems to do this successfuly. Can you
> > >please give me a hint to build the *.war without
> > >running into an build failure.
> > >
> > >Thanks a lot
> > >Ted
> > >--- Deepal Jayasinghe <de...@opensource.lk>
> > schrieb:
> > >
> > >
> > >
> > >>I understood the problem , and I just fixed that
> > :)
> > >>
> > >>if you can get Axis2 source update , then you will
> > >>be able to get the
> > >>correct behavior , and you do not need to send the
> > >>service group id , if
> > >>you deploy the service in application scope.
> > >>
> > >>donnerdrummel2000-mailing@yahoo.de wrote:
> > >>
> > >>
> > >>
> > >>>Hi Deepal,
> > >>>
> > >>>first at all, thanks for your reply. Okay, I'll
> > try
> > >>>
> > >>>
> > >>to
> > >>
> > >>
> > >>>clarify the 'it does not work'. To test this
> > >>>
> > >>>
> > >>scoping
> > >>
> > >>
> > >>>feature for the 0.94 release I used a simple
> > >>>
> > >>>
> > >>Service
> > >>
> > >>
> > >>>which increases an integer value at every call
> > and
> > >>>returns this value. After deployment under the
> > >>><service scope="application">-setting it does not
> > >>>
> > >>>
> > >>work
> > >>
> > >>
> > >>>wich means it returns for every request a '1' but
> > >>>
> > >>>
> > >>it
> > >>
> > >>
> > >>>should be for 3 request '1','2','3'...
> > >>>The only way to get this behavior is to deploy
> > the
> > >>>service with the scope="transport" setting.
> > >>>
> > >>>You said that there is a usage of a service group
> > >>>
> > >>>
> > >>ID
> > >>
> > >>
> > >>>for the intern handling of some of this scope
> > >>>
> > >>>
> > >>types.
> > >>
> > >>
> > >>>Does this mean, that I've to deploy my single
> > >>>Countservice as a service group to get all the
> > >>>
> > >>>
> > >>scoping
> > >>
> > >>
> > >>>features to work?
> > >>>
> > >>>Thanks Ted
> > >>>
> > >>>--- Deepal Jayasinghe <de...@opensource.lk>
> > wrote:
> > >>>
> > >>>
> > >>>
> > >>>Hi Ted;
> > >>>
> > >>>what do u mean by that does not work ? , I
> > >>>
> > >>>
> > >>recently
> > >>
> > >>
> > >>>changed scope
> > >>>handling , and I hope that should work.
> > >>>
> > >>>and that work as follows ,
> > >>> 1. If you deploy a service under the scope
> > >>>"request" , then there
> > >>>wont be any sessions management even if you send
> > >>>
> > >>>
> > >>the
> > >>
> > >>
> > >>>service group ID
> > >>>back (we mange session using ServiceGroup ID)
> > >>> 2. If you deploy a service in the transport
> > >>>session scope , then the
> > >>>there will be session management using transport
> > >>>cookies and there
> > >>>will be only one instance of service impl class
> > >>>
> > >>>
> > >>for
> > >>
> > >>
> > >>>that transport
> > >>>session.
> > >>> 3. If you deploy a service in scope of SOAP
> > >>>
> > >>>
> > >>session
> > >>
> > >>
> > >>>then you can
> > >>>manage session using ServiceGroupID , but that
> > >>>session will be removed
> > >>>from the system if you did not touch the session
> > >>>
> > >>>
> > >>for
> > >>
> > >>
> > >>>about 30s. (there
> > >>>will be only one instance of the service impl for
> > >>>that session)
> > >>>4. If you deploy service in application scope
> > then
> > >>>one can manage a
> > >>>session using servicegroupID throughout the life
> > >>>time of the
> > >>>system.(there will be only one instance of the
> > >>>service impl for that
> > >>>session)
> > >>>
> > >>>and can you pls clarify what do you mean by it
> > >>>
> > >>>
> > >>does
> > >>
> > >>
> > >>>not work , so that
> > >>>I can fix that
> > >>>
> > >>>donnerdrummel2000-mailing@yahoo.de wrote:
> > >>>
> > >>>
> > >>>
> > >>>>Hello,
> > >>>>
> > >>>>
> > >>>>trying to deploy some services under the use of
> > >>>>
> > >>>>
> > >>the
> > >>
> > >>
> > >>>>attribute scope="application" at the
> > >>>>
> > >>>>
> > >><service>-tag
> > >>
> > >>
> > >>>in
> > >>>
> > >>>
> > >>>
> > >>>>services.xml, I noticed that this setting of the
> > >>>>
> > >>>>
> >
> === message truncated ===
>
>
>
>
>
>
> ___________________________________________________________
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
> BUILD FAILED
> File...... C:\Dokumente und Einstellungen\t.israel\.maven\cache\maven-multiproje
> ct-plugin-1.3.1\plugin.jelly
> Element... maven:reactor
> Line...... 217
> Column.... 9
> Unable to obtain goal [multiproject:install-callback] -- C:\axis2_nightly\module
> s\integration\maven.xml:40:38: <ant:ant> Unexpected attribute "xmlns:xalan"
> Total time: 12 minutes 10 seconds
> Finished at: Wed Feb 08 11:35:24 CET 2006
>
>
--
Ajith Ranabahu
Re: [Axis2] application scope
Posted by do...@yahoo.de.
Hi Deepal,
sorry to say that, but the build failed even today
(using maven war). For more detail see attachement,
maybe this will help you to fix an other bug or giving
me a hint what i did wrong.
Thank you,
Ted
--- Deepal Jayasinghe <de...@opensource.lk> schrieb:
> Hi Ted;
>
> I dont think maven war goal will fail now , there
> was a bug and we have
> fixed that , try and see :)
>
> donnerdrummel2000-mailing@yahoo.de wrote:
>
> >Wow, Deepal this was realy one of the quickest
> replys
> >I got! So I'll try to build the source but since
> some
> >days I've problems to do this successfuly. Can you
> >please give me a hint to build the *.war without
> >running into an build failure.
> >
> >Thanks a lot
> >Ted
> >--- Deepal Jayasinghe <de...@opensource.lk>
> schrieb:
> >
> >
> >
> >>I understood the problem , and I just fixed that
> :)
> >>
> >>if you can get Axis2 source update , then you will
> >>be able to get the
> >>correct behavior , and you do not need to send the
> >>service group id , if
> >>you deploy the service in application scope.
> >>
> >>donnerdrummel2000-mailing@yahoo.de wrote:
> >>
> >>
> >>
> >>>Hi Deepal,
> >>>
> >>>first at all, thanks for your reply. Okay, I'll
> try
> >>>
> >>>
> >>to
> >>
> >>
> >>>clarify the 'it does not work'. To test this
> >>>
> >>>
> >>scoping
> >>
> >>
> >>>feature for the 0.94 release I used a simple
> >>>
> >>>
> >>Service
> >>
> >>
> >>>which increases an integer value at every call
> and
> >>>returns this value. After deployment under the
> >>><service scope="application">-setting it does not
> >>>
> >>>
> >>work
> >>
> >>
> >>>wich means it returns for every request a '1' but
> >>>
> >>>
> >>it
> >>
> >>
> >>>should be for 3 request '1','2','3'...
> >>>The only way to get this behavior is to deploy
> the
> >>>service with the scope="transport" setting.
> >>>
> >>>You said that there is a usage of a service group
> >>>
> >>>
> >>ID
> >>
> >>
> >>>for the intern handling of some of this scope
> >>>
> >>>
> >>types.
> >>
> >>
> >>>Does this mean, that I've to deploy my single
> >>>Countservice as a service group to get all the
> >>>
> >>>
> >>scoping
> >>
> >>
> >>>features to work?
> >>>
> >>>Thanks Ted
> >>>
> >>>--- Deepal Jayasinghe <de...@opensource.lk>
> wrote:
> >>>
> >>>
> >>>
> >>>Hi Ted;
> >>>
> >>>what do u mean by that does not work ? , I
> >>>
> >>>
> >>recently
> >>
> >>
> >>>changed scope
> >>>handling , and I hope that should work.
> >>>
> >>>and that work as follows ,
> >>> 1. If you deploy a service under the scope
> >>>"request" , then there
> >>>wont be any sessions management even if you send
> >>>
> >>>
> >>the
> >>
> >>
> >>>service group ID
> >>>back (we mange session using ServiceGroup ID)
> >>> 2. If you deploy a service in the transport
> >>>session scope , then the
> >>>there will be session management using transport
> >>>cookies and there
> >>>will be only one instance of service impl class
> >>>
> >>>
> >>for
> >>
> >>
> >>>that transport
> >>>session.
> >>> 3. If you deploy a service in scope of SOAP
> >>>
> >>>
> >>session
> >>
> >>
> >>>then you can
> >>>manage session using ServiceGroupID , but that
> >>>session will be removed
> >>>from the system if you did not touch the session
> >>>
> >>>
> >>for
> >>
> >>
> >>>about 30s. (there
> >>>will be only one instance of the service impl for
> >>>that session)
> >>>4. If you deploy service in application scope
> then
> >>>one can manage a
> >>>session using servicegroupID throughout the life
> >>>time of the
> >>>system.(there will be only one instance of the
> >>>service impl for that
> >>>session)
> >>>
> >>>and can you pls clarify what do you mean by it
> >>>
> >>>
> >>does
> >>
> >>
> >>>not work , so that
> >>>I can fix that
> >>>
> >>>donnerdrummel2000-mailing@yahoo.de wrote:
> >>>
> >>>
> >>>
> >>>>Hello,
> >>>>
> >>>>
> >>>>trying to deploy some services under the use of
> >>>>
> >>>>
> >>the
> >>
> >>
> >>>>attribute scope="application" at the
> >>>>
> >>>>
> >><service>-tag
> >>
> >>
> >>>in
> >>>
> >>>
> >>>
> >>>>services.xml, I noticed that this setting of the
> >>>>
> >>>>
>
=== message truncated ===
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [Axis2] application scope
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Ted;
I dont think maven war goal will fail now , there was a bug and we have
fixed that , try and see :)
donnerdrummel2000-mailing@yahoo.de wrote:
>Wow, Deepal this was realy one of the quickest replys
>I got! So I'll try to build the source but since some
>days I've problems to do this successfuly. Can you
>please give me a hint to build the *.war without
>running into an build failure.
>
>Thanks a lot
>Ted
>--- Deepal Jayasinghe <de...@opensource.lk> schrieb:
>
>
>
>>I understood the problem , and I just fixed that :)
>>
>>if you can get Axis2 source update , then you will
>>be able to get the
>>correct behavior , and you do not need to send the
>>service group id , if
>>you deploy the service in application scope.
>>
>>donnerdrummel2000-mailing@yahoo.de wrote:
>>
>>
>>
>>>Hi Deepal,
>>>
>>>first at all, thanks for your reply. Okay, I'll try
>>>
>>>
>>to
>>
>>
>>>clarify the 'it does not work'. To test this
>>>
>>>
>>scoping
>>
>>
>>>feature for the 0.94 release I used a simple
>>>
>>>
>>Service
>>
>>
>>>which increases an integer value at every call and
>>>returns this value. After deployment under the
>>><service scope="application">-setting it does not
>>>
>>>
>>work
>>
>>
>>>wich means it returns for every request a '1' but
>>>
>>>
>>it
>>
>>
>>>should be for 3 request '1','2','3'...
>>>The only way to get this behavior is to deploy the
>>>service with the scope="transport" setting.
>>>
>>>You said that there is a usage of a service group
>>>
>>>
>>ID
>>
>>
>>>for the intern handling of some of this scope
>>>
>>>
>>types.
>>
>>
>>>Does this mean, that I've to deploy my single
>>>Countservice as a service group to get all the
>>>
>>>
>>scoping
>>
>>
>>>features to work?
>>>
>>>Thanks Ted
>>>
>>>--- Deepal Jayasinghe <de...@opensource.lk> wrote:
>>>
>>>
>>>
>>>Hi Ted;
>>>
>>>what do u mean by that does not work ? , I
>>>
>>>
>>recently
>>
>>
>>>changed scope
>>>handling , and I hope that should work.
>>>
>>>and that work as follows ,
>>> 1. If you deploy a service under the scope
>>>"request" , then there
>>>wont be any sessions management even if you send
>>>
>>>
>>the
>>
>>
>>>service group ID
>>>back (we mange session using ServiceGroup ID)
>>> 2. If you deploy a service in the transport
>>>session scope , then the
>>>there will be session management using transport
>>>cookies and there
>>>will be only one instance of service impl class
>>>
>>>
>>for
>>
>>
>>>that transport
>>>session.
>>> 3. If you deploy a service in scope of SOAP
>>>
>>>
>>session
>>
>>
>>>then you can
>>>manage session using ServiceGroupID , but that
>>>session will be removed
>>>from the system if you did not touch the session
>>>
>>>
>>for
>>
>>
>>>about 30s. (there
>>>will be only one instance of the service impl for
>>>that session)
>>>4. If you deploy service in application scope then
>>>one can manage a
>>>session using servicegroupID throughout the life
>>>time of the
>>>system.(there will be only one instance of the
>>>service impl for that
>>>session)
>>>
>>>and can you pls clarify what do you mean by it
>>>
>>>
>>does
>>
>>
>>>not work , so that
>>>I can fix that
>>>
>>>donnerdrummel2000-mailing@yahoo.de wrote:
>>>
>>>
>>>
>>>>Hello,
>>>>
>>>>
>>>>trying to deploy some services under the use of
>>>>
>>>>
>>the
>>
>>
>>>>attribute scope="application" at the
>>>>
>>>>
>><service>-tag
>>
>>
>>>in
>>>
>>>
>>>
>>>>services.xml, I noticed that this setting of the
>>>>
>>>>
>>>scope
>>>
>>>
>>>
>>>>doesn't work in Axis2 0.94. The only correct
>>>>
>>>>
>>>working
>>>
>>>
>>>
>>>>scope is the scope="transport". Are there any
>>>>
>>>>
>>knows
>>
>>
>>>>bugs? I thought that this application scope
>>>>
>>>>
>>setting
>>
>>
>>>>worked well, using release 0.93...
>>>>
>>>>
>>>>Thanks Ted
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>___________________________________________________________
>
>
>>>>Telefonate ohne weitere Kosten vom PC zum PC:
>>>>
>>>>
>>>http://messenger.yahoo.de
>>>
>>>
>>>--
>>>Thanks,
>>>Deepal
>>>
>>>
>>>
>>>
>>................................................................
>>
>>
>>>~Future is Open~
>>>
>>>
>>
>>___________________________________________________________
>>
>>
>>>Telefonate ohne weitere Kosten vom PC zum PC:
>>>
>>>
>>http://messenger.yahoo.de
>>
>>
>>
>>--
>>Thanks,
>>Deepal
>>
>>
>>
>................................................................
>
>
>>~Future is Open~
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>___________________________________________________________
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [Axis2] application scope
Posted by do...@yahoo.de.
Wow, Deepal this was realy one of the quickest replys
I got! So I'll try to build the source but since some
days I've problems to do this successfuly. Can you
please give me a hint to build the *.war without
running into an build failure.
Thanks a lot
Ted
--- Deepal Jayasinghe <de...@opensource.lk> schrieb:
>
> I understood the problem , and I just fixed that :)
>
> if you can get Axis2 source update , then you will
> be able to get the
> correct behavior , and you do not need to send the
> service group id , if
> you deploy the service in application scope.
>
> donnerdrummel2000-mailing@yahoo.de wrote:
>
> >Hi Deepal,
> >
> >first at all, thanks for your reply. Okay, I'll try
> to
> >clarify the 'it does not work'. To test this
> scoping
> >feature for the 0.94 release I used a simple
> Service
> >which increases an integer value at every call and
> >returns this value. After deployment under the
> ><service scope="application">-setting it does not
> work
> >wich means it returns for every request a '1' but
> it
> >should be for 3 request '1','2','3'...
> >The only way to get this behavior is to deploy the
> >service with the scope="transport" setting.
> >
> >You said that there is a usage of a service group
> ID
> >for the intern handling of some of this scope
> types.
> >Does this mean, that I've to deploy my single
> >Countservice as a service group to get all the
> scoping
> >features to work?
> >
> >Thanks Ted
> >
> >--- Deepal Jayasinghe <de...@opensource.lk> wrote:
> >
>
> > Hi Ted;
> >
> > what do u mean by that does not work ? , I
> recently
> > changed scope
> > handling , and I hope that should work.
> >
> > and that work as follows ,
> > 1. If you deploy a service under the scope
> > "request" , then there
> > wont be any sessions management even if you send
> the
> > service group ID
> > back (we mange session using ServiceGroup ID)
> > 2. If you deploy a service in the transport
> > session scope , then the
> > there will be session management using transport
> > cookies and there
> > will be only one instance of service impl class
> for
> > that transport
> > session.
> > 3. If you deploy a service in scope of SOAP
> session
> > then you can
> > manage session using ServiceGroupID , but that
> > session will be removed
> > from the system if you did not touch the session
> for
> > about 30s. (there
> > will be only one instance of the service impl for
> > that session)
> > 4. If you deploy service in application scope then
> > one can manage a
> > session using servicegroupID throughout the life
> > time of the
> > system.(there will be only one instance of the
> > service impl for that
> > session)
> >
> > and can you pls clarify what do you mean by it
> does
> > not work , so that
> > I can fix that
> >
> > donnerdrummel2000-mailing@yahoo.de wrote:
> >
> > >Hello,
> >
> > >trying to deploy some services under the use of
> the
> > >attribute scope="application" at the
> <service>-tag
> >
> > in
> >
> > >services.xml, I noticed that this setting of the
> >
> > scope
> >
> > >doesn't work in Axis2 0.94. The only correct
> >
> > working
> >
> > >scope is the scope="transport". Are there any
> knows
> > >bugs? I thought that this application scope
> setting
> > >worked well, using release 0.93...
> >
> > >Thanks Ted
> >
> >
> >
> >
> >
> >
> >
>
___________________________________________________________
> >
> > >Telefonate ohne weitere Kosten vom PC zum PC:
> >
> > http://messenger.yahoo.de
> >
> >
> > --
> > Thanks,
> > Deepal
> >
> >
>
>................................................................
> >
> > ~Future is Open~
>
>
>
>___________________________________________________________
> >Telefonate ohne weitere Kosten vom PC zum PC:
> http://messenger.yahoo.de
>
>
>
> --
> Thanks,
> Deepal
>
................................................................
> ~Future is Open~
>
>
>
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [Axis2] application scope
Posted by Deepal Jayasinghe <de...@opensource.lk>.
I understood the problem , and I just fixed that :)
if you can get Axis2 source update , then you will be able to get the
correct behavior , and you do not need to send the service group id , if
you deploy the service in application scope.
donnerdrummel2000-mailing@yahoo.de wrote:
>Hi Deepal,
>
>first at all, thanks for your reply. Okay, I'll try to
>clarify the 'it does not work'. To test this scoping
>feature for the 0.94 release I used a simple Service
>which increases an integer value at every call and
>returns this value. After deployment under the
><service scope="application">-setting it does not work
>wich means it returns for every request a '1' but it
>should be for 3 request '1','2','3'...
>The only way to get this behavior is to deploy the
>service with the scope="transport" setting.
>
>You said that there is a usage of a service group ID
>for the intern handling of some of this scope types.
>Does this mean, that I've to deploy my single
>Countservice as a service group to get all the scoping
>features to work?
>
>Thanks Ted
>
>--- Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> Hi Ted;
>
> what do u mean by that does not work ? , I recently
> changed scope
> handling , and I hope that should work.
>
> and that work as follows ,
> 1. If you deploy a service under the scope
> "request" , then there
> wont be any sessions management even if you send the
> service group ID
> back (we mange session using ServiceGroup ID)
> 2. If you deploy a service in the transport
> session scope , then the
> there will be session management using transport
> cookies and there
> will be only one instance of service impl class for
> that transport
> session.
> 3. If you deploy a service in scope of SOAP session
> then you can
> manage session using ServiceGroupID , but that
> session will be removed
> from the system if you did not touch the session for
> about 30s. (there
> will be only one instance of the service impl for
> that session)
> 4. If you deploy service in application scope then
> one can manage a
> session using servicegroupID throughout the life
> time of the
> system.(there will be only one instance of the
> service impl for that
> session)
>
> and can you pls clarify what do you mean by it does
> not work , so that
> I can fix that
>
> donnerdrummel2000-mailing@yahoo.de wrote:
>
> >Hello,
>
> >trying to deploy some services under the use of the
> >attribute scope="application" at the <service>-tag
>
> in
>
> >services.xml, I noticed that this setting of the
>
> scope
>
> >doesn't work in Axis2 0.94. The only correct
>
> working
>
> >scope is the scope="transport". Are there any knows
> >bugs? I thought that this application scope setting
> >worked well, using release 0.93...
>
> >Thanks Ted
>
>
>
>
>
>
> ___________________________________________________________
>
> >Telefonate ohne weitere Kosten vom PC zum PC:
>
> http://messenger.yahoo.de
>
>
> --
> Thanks,
> Deepal
>
> >................................................................
>
> ~Future is Open~
>___________________________________________________________
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [Axis2] application scope
Posted by do...@yahoo.de.
Hi Deepal,
first at all, thanks for your reply. Okay, I'll try to
clarify the 'it does not work'. To test this scoping
feature for the 0.94 release I used a simple Service
which increases an integer value at every call and
returns this value. After deployment under the
<service scope="application">-setting it does not work
wich means it returns for every request a '1' but it
should be for 3 request '1','2','3'...
The only way to get this behavior is to deploy the
service with the scope="transport" setting.
You said that there is a usage of a service group ID
for the intern handling of some of this scope types.
Does this mean, that I've to deploy my single
Countservice as a service group to get all the scoping
features to work?
Thanks Ted
--- Deepal Jayasinghe <de...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Ted;
>
> what do u mean by that does not work ? , I recently
> changed scope
> handling , and I hope that should work.
>
> and that work as follows ,
> 1. If you deploy a service under the scope
> "request" , then there
> wont be any sessions management even if you send the
> service group ID
> back (we mange session using ServiceGroup ID)
> 2. If you deploy a service in the transport
> session scope , then the
> there will be session management using transport
> cookies and there
> will be only one instance of service impl class for
> that transport
> session.
> 3. If you deploy a service in scope of SOAP session
> then you can
> manage session using ServiceGroupID , but that
> session will be removed
> from the system if you did not touch the session for
> about 30s. (there
> will be only one instance of the service impl for
> that session)
> 4. If you deploy service in application scope then
> one can manage a
> session using servicegroupID throughout the life
> time of the
> system.(there will be only one instance of the
> service impl for that
> session)
>
> and can you pls clarify what do you mean by it does
> not work , so that
> I can fix that
>
> donnerdrummel2000-mailing@yahoo.de wrote:
>
> >Hello,
> >
> >trying to deploy some services under the use of the
> >attribute scope="application" at the <service>-tag
> in
> >services.xml, I noticed that this setting of the
> scope
> >doesn't work in Axis2 0.94. The only correct
> working
> >scope is the scope="transport". Are there any knows
> >bugs? I thought that this application scope setting
> >worked well, using release 0.93...
> >
> >Thanks Ted
> >
> >
> >
> >
> >
> >
>
>___________________________________________________________
> >Telefonate ohne weitere Kosten vom PC zum PC:
> http://messenger.yahoo.de
> >
> >
>
> - --
> Thanks,
> Deepal
>
................................................................
> ~Future is Open~
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird -
> http://enigmail.mozdev.org
>
>
iD8DBQFD6Z/ajOGcXNDx0CARAnxlAJ9QWwpSlj7guWeZnwvpCrCjulPJDQCfTC6c
> T47YjD9rTeMWqwUQrT/IhG8=
> =XjMa
> -----END PGP SIGNATURE-----
>
>
>
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [Axis2] application scope
Posted by Deepal Jayasinghe <de...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ted;
what do u mean by that does not work ? , I recently changed scope
handling , and I hope that should work.
and that work as follows ,
1. If you deploy a service under the scope "request" , then there
wont be any sessions management even if you send the service group ID
back (we mange session using ServiceGroup ID)
2. If you deploy a service in the transport session scope , then the
there will be session management using transport cookies and there
will be only one instance of service impl class for that transport
session.
3. If you deploy a service in scope of SOAP session then you can
manage session using ServiceGroupID , but that session will be removed
from the system if you did not touch the session for about 30s. (there
will be only one instance of the service impl for that session)
4. If you deploy service in application scope then one can manage a
session using servicegroupID throughout the life time of the
system.(there will be only one instance of the service impl for that
session)
and can you pls clarify what do you mean by it does not work , so that
I can fix that
donnerdrummel2000-mailing@yahoo.de wrote:
>Hello,
>
>trying to deploy some services under the use of the
>attribute scope="application" at the <service>-tag in
>services.xml, I noticed that this setting of the scope
>doesn't work in Axis2 0.94. The only correct working
>scope is the scope="transport". Are there any knows
>bugs? I thought that this application scope setting
>worked well, using release 0.93...
>
>Thanks Ted
>
>
>
>
>
>
>___________________________________________________________
>Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
- --
Thanks,
Deepal
................................................................
~Future is Open~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD6Z/ajOGcXNDx0CARAnxlAJ9QWwpSlj7guWeZnwvpCrCjulPJDQCfTC6c
T47YjD9rTeMWqwUQrT/IhG8=
=XjMa
-----END PGP SIGNATURE-----