... 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 <[EMAIL PROTECTED]> schrieb:
> Guys!! i'll fix this today. Patience please :)
>
> -- dims
>
> On 2/8/06, Ajith Ranabahu <[EMAIL PROTECTED]>
> 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, [EMAIL PROTECTED]
> > <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
> schrieb:
> > >
> > > > Hi Ted;
> > > >
> > > > I dont think maven war goal will fail now ,
> there
> > > > was a bug and we have
> > > > fixed that , try and see :)
> > > >
> > > > [EMAIL PROTECTED] 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 <[EMAIL PROTECTED]>
> > > > 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.
> > > > >>
> > > > >>[EMAIL PROTECTED] 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
> <[EMAIL PROTECTED]>
> > > > 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.deBUILD FAILED
File...... C:\Dokumente und Einstellungen\ted\.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: 6 minutes 13 seconds
Finished at: Wed Feb 08 14:21:24 CET 2006
