I'd be tempted to ignore the 'no errors after restart' as a red herring as a first approach - I've seen these kinds of things from JBoss before, it does seem in some instances to use different code for startup and for hot deploy. In my experience the one that reported the errors was indeed correct, the one that doesn't is just being a little too lenient, either in interface requirements or XML parsing.
Run it in a debugger as previously suggested may well be the best next step. I haven't used tiles yet, but I suspect you there's something silly going on and you can take the exception at its word.


Dunno if that helps at all.
Brett Connor


Lucas Gonzalez Pearson wrote:

Hi,
I am still trying to find the root of this problem but I donīt seem to be
able to do it.

Has anyone experienced this problem before?
copying a struts .war file to jbossī deploy directory and then getting this
error:

javax.servlet.ServletException: TilesPlugin : Specified RequestProcessor not
compatible with TilesRequestProcessor
   at
org.apache.struts.tiles.TilesPlugin.initRequestProcessorClass(TilesPlugin.ja
va:360)

( doing a restart throws no errors )...

Any ideas? pointers?

Thanks... =)

----- Original Message ----- From: "Lucas Gonzalez Pearson" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, July 08, 2004 6:19 PM
Subject: Re: Extending Request Processor





I have this in my struts-config.xml file..

<plug-in className="org.apache.struts.tiles.TilesPlugin">
<set-property property="definitions-config"
value="/WEB-INF/tiles-defs.xml"/>
<set-property property="moduleAware" value="true"/>
<set-property property="definitions-parser-validate"


value="true"/>


   </plug-in>


itīs strange.. everything seems to be normal..

but another thing I found out was that the problem arises when I


hot-deploy


the .war file...

If I restart the jboss / tomcat , then the error is thrown, but the App
still works..

strange.. =/


----- Original Message ----- From: "Venkat Maddipati" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Thursday, July 08, 2004 6:00 PM
Subject: RE: Extending Request Processor



Try to put include the following in your struts configuratin file (struts-config.xml). Follow the comments to understand the Tiles plugin :

I have also extended my RequesteProcessor class from TilesRequestProcessor
class.



<!-- ========== Tiles plugin =================== -->
<!--
-->
<!--
This plugin initialize Tiles definition factory. This later can takes
some
parameters explained here after. The plugin first read parameters
from web.xml, then
overload them with parameters defined here. All parameters are
optional.
The plugin should be declared in each struts-config file.
- definitions-config: (optional)
Specify configuration file names. There can be several comma
separated file names (default: ?? )
- moduleAware: (optional - struts1.1)
Specify if the Tiles definition factory is module aware. If


true


(default),
there will be one factory for each Struts module.
If false, there will be one common factory for all
module. In this later case,
it is still needed to declare one plugin per module.
The factory will be
initialized with parameters found in the first
initialized plugin (generally the
one associated with the default module).
 true : One factory per module. (default)
 false : one single shared factory for all modules
  - definitions-parser-validate: (optional)
       Specify if xml parser should validate the Tiles
configuration file.
 true : validate. DTD should be specified in file
header. (default)
 false : no validation

 Paths found in Tiles definitions are relative to the main context.
 -->
 <plug-in className="org.apache.struts.tiles.TilesPlugin" >
   <set-property property="definitions-config"
                value="/WEB-INF/tiles-defs.xml" />
   <set-property property="moduleAware" value="true" />
   <set-property property="definitions-parser-validate" value="true" />
 </plug-in>



Thanks,
Venkat





-----Original Message-----
From: Lucas Gonzalez Pearson [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 1:37 PM
To: Struts Users Mailing List
Subject: Extending Request Processor


Hi Iīve recently extended the requestProcessor with one of my own and found this error:

javax.servlet.ServletException: TilesPlugin : Specified


RequestProcessor


not compatible with TilesRequestProcessor
           at



org.apache.struts.tiles.TilesPlugin.initRequestProcessorClass(TilesPlugin.ja


va:360)

Everything seems to be fine

public class MyRequestProcessor
       extends TilesRequestProcessor { .... }

and in struts-config.xml
   <controller
processorClass="com.convergia.laos.security.MyRequestProcessor"/>

Iīve searched quite a bit on the internet and only found that you have to
extend from TilesRequestProcessor just as I did

any ideas on why this is happening?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




************************************************************************

If you have received this e-mail in error, please delete it and notify the
sender as soon as possible. The contents of this e-mail may be


confidential


and the unauthorized use, copying, or dissemination of it and any
attachments to it, is prohibited.

Internet communications are not secure and Hyperion does not, therefore,
accept legal responsibility for the contents of this message nor for any
damage caused by viruses.  The views expressed here do not necessarily
represent those of Hyperion.

For more information about Hyperion, please visit our Web site at
www.hyperion.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to