iginal Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Michael Neale
> Sent: Tuesday, September 23, 2008 5:25 AM
> To: Rules Users List
> Subject: Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
>
> Hi Vikrant.
>
> well the drools
to
give another shot at seeing the behavior after upgrading to a higher
release.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] On Behalf Of Michael Neale
Sent: Tuesday, September 23, 2008 5:25 AM
To: Rules Users List
Subject: Re: [rules-users] RE: Deploying t
Sent: 23 September 2008 07:50
To: Rules Users List
Subject: RE: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
Well it is not that serious a problem as I initially thought. As I
mentioned the URL(adding the index.jsp) works, so there is an easy
work-around available.
The main bug seems to
ease.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Neale
Sent: Tuesday, September 23, 2008 5:25 AM
To: Rules Users List
Subject: Re: [rules-users] RE: Deploying the BRMS on Web-Sphere 6.1
Hi Vikrant.
well the drools-guvnor/ doesn't use a filter s
Hi Vikrant.
well the drools-guvnor/ doesn't use a filter so much as it is default
web.xml behaviour - you can specify a "welcome" page, which it goes to
when the root path is supplied. If Websphere 6.1 can't even do that -
I would say something is seriously wrong (may be a bad install?) - you
coul
Well it clearly is a problem with filters as the following works in WebSphere:
http://localhost:9080/drools-guvnor/index.jsp
However just typing
http://localhost:9080/drools-guvnor does not and gives you the Ugly 500.
Cheers,
Vikrant
From: Vikrant Yagnick
Sent: Monday, September 22, 2008 4:38
