Hi All, (specially Antonio and Mikolaj)

Finally found the root cause of the problem.

The error lies in case-sensitivity in declaring the form bean entry. If the
package name does not match the directory structure (in case-sensitive form)
then the corresponding error is thrown.

Thanks for all your help folks.

Regards,
Sandeep Gupta




On 10/11/06, Sandeep Gupta <[EMAIL PROTECTED]> wrote:

Antonio,

I have just now redeployed the Weblogic server but still am unable to
deploy the application.
The strange fact is that I am using the same weblogic version, java
version, eclipse version and ant version to build and deploy, and the
application deploys very smoothly.

Please help me out as the release is nearing.... :-(

- Sandeep



On 10/11/06, Sandeep Gupta < [EMAIL PROTECTED]> wrote:
>
> i have tried cleaning up the cache of the weblogic. also cleaned the
> build folder.
> by any method if i am deploying after deleting the additional
> <form-bean> line it works fine.
> but by adding just one another <form-bean> line the deployment fails and
> I start getting a 503 error.
>
> its really weird and making me crazy :-)
>
> - Sandeep
>
>
> On 10/11/06, Mikolaj Rydzewski < [EMAIL PROTECTED] > wrote:
> >
> > Sandeep Gupta wrote:
> > > But when I am deploying the WAR it works perfectly. I have validated
> > the
> > > struts-config.xml file using various validators and it is validated
> > > without
> > > any errors or warnings.
> > Maybe some kind of file-locking occurs? How do you make a deploy? Just
> > copy war's content into app's directory? Maybe this is the case,
> > weblogic keeps reference to old struts-config.xml or something like
> > that.
> >
> > When deploying as a war file, weblogic just removes old directory,
> > creates a new one and no file-locking occurs.
> >
> > --
> > Mikolaj Rydzewski < [EMAIL PROTECTED]>
> >
> >
> >
> >
>
>
> --
> Regards,
>
> Sandeep Gupta




--
Regards,

Sandeep Gupta




--
Regards,

Sandeep Gupta

Reply via email to