I think I got something like this before when i had a typo in
standardjaws.xml or jaws.xml. Are you sure that's not the case? I thought
I put some better error messages when a parsing error happens. Check
server.log or something.
Regards,
Bill
> -Original Message-
> From: [EMAIL PROTE
I was experiencing a similar issue with 2.4. If I didn't specify a default
datasource in standardjaws.xml, I was getting a null pointer exception. I
*did* specify a valid datasource in my jaws.xml.
jim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf O
The standardjaws.xml & jaws.xml files will deploy under the latest cvs
unchanged, so I do not believe there is a typo. I would look into it more,
but I have bigger fish to fry, it looks like this has been fixed in later
releases.
My concern is that folks will try to download a 2.4 build and atte
Yes, I think something is broken there. Do you know if the same will happen
(no default ds & null pointer) in the main cvs branch?
--jason
On Mon, 9 Jul 2001, James Cook wrote:
> I was experiencing a similar issue with 2.4. If I didn't specify a default
> datasource in standardjaws.xml, I was
t; To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] 2.4 release(s) & jaws.xml problem
>
>
> Yes, I think something is broken there. Do you know if the same
> will happen
> (no default ds & null pointer) in the main cvs branch?
>
> --jason
>
>
> On Mon, 9 Jul
IL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jason
> > Dillon
> > Sent: Monday, July 09, 2001 10:59 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [JBoss-dev] 2.4 release(s) & jaws.xml problem
> >
> >
> > Yes, I think something is broken t
