Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of davanum@gmail.com designates
 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=lJd2jkdLaS+EjvbI2yacT241jCMbN6RKOsC24haJOd6kpEhjmVsfWvm6lFweQe5luQe50EWcvlE+VtscxBCHrLwiET50AVuUz4Pf9SLO3pc/A11m2ub8OKAyK2hb6mkjUuK4CuWm2VPfOR2jp3vlAvr3t63AaARo2NsXdRfE1hE=
Message-ID: <19e0530f0703131825t1351b006w6834095a9a431b57@mail.gmail.com>
Date: Tue, 13 Mar 2007 21:25:49 -0400
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: [axis2] JAXWS problems?
In-Reply-To: <45F7434C.7020501@thoughtcraft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <OF717F2DF6.A3805A3D-ON8725729D.00631582-8625729D.00633468@us.ibm.com>
	 <45F705F1.5090206@thoughtcraft.com>
	 <9abd5e730703131405q923e5eay34753d53face0092@mail.gmail.com>
	 <45F7434C.7020501@thoughtcraft.com>

When you build with JDK1.4 the jaxws stuff is not built...

-- dims

On 3/13/07, Glen Daniels <glen@thoughtcraft.com> wrote:
> Weird - I switched from Java5 to the 1.4.2_10 JDK and everything is now
> building fine.  I'll try again with J5 later to see if that reproduces
> the problem.
>
> Spooky.
>
> Incidentally, if I haven't already said this, three cheers for the
> automated builds, David!
>
> --G
>
>
> David Illsley wrote:
> > Glen,
> > Just FYI,the m2 build (including tests) is currently passing on
> > continuum (includes jaxws). [1]
> > David
> >
> > [1]
> > http://ws.zones.apache.org:10000/continuum/servlet/continuum/target/ProjectBuilds.vm/view/ProjectBuilds/id/61;jsessionid=32deio4w3ssw4
> >
> >
> >
> > On 13/03/07, Glen Daniels <glen@thoughtcraft.com> wrote:
> >> Nicholas L Gallardo wrote:
> >> > That's interesting...  I haven't seen that one before myself, but I
> >> know
> >> > others have seen OOM errors when trying to run the JAXWS test suite
> >> with
> >> > trace enabled.  The other interesting bit is that the elapsed time
> >> for the
> >>
> >> I'm running a clean build, so whatever's the defaults, I'm using them.
> >> Have you tried the Maven2 build?  I just tried it again after wiping my
> >> entire repository, and still get the same exact errors.
> >>
> >> The Maven1 build works fine for the JAXWS module.
> >>
> >> Any clues greatly appreciated.
> >>
> >> > tests is over double what the normal run is.  I'm not familiar with
> >> > surefire so I can't comment on what overhead that might be adding.  Is
> >> > there an additional tool that's needed to run that, or is it
> >> packaged with
> >> > maven by default?
> >>
> >> I assumed it's what Maven2 does by default to run tests...?
> >>
> >> --Glen
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org