You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "SanJ.SANJAY" <gi...@gmail.com> on 2009/01/13 21:06:13 UTC

Upgrading Struts from 1 to 2.0.14

I am having some issues while upgrading the struts:

I dowloaded the latest 2.0.14 source from mirror and then copied all the
.jars from the /lib  folder to my application /lib folder. Now when I
restart my Jboss, it throws error for deploying my web application with an
error:

java.lang.ClassCastException: org.apache.struts.tiles.TilesPlugin cannot be
cast to org.apache.struts.action.PlugIn
        at
org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:855)
        at
org.apache.struts.action.ActionServlet.init(ActionServlet.java:356)
        at javax.servlet.GenericServlet.init(GenericServlet.java:211)
        at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
        at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925)
     ....


:confused:

So I am not sure if this error comes because of new jar files that I added
to upgrade struts or I did not follow the complete process for upgrading the
struts. Any insights???



-- 
View this message in context: http://www.nabble.com/Upgrading-Struts-from-1-to-2.0.14-tp21443421p21443421.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Dave Newton <ne...@yahoo.com>.
Wes Wannemacher wrote:
> I think he was referring to the - 
> Spring/Hibernate-JSF Integration Technology stack (S.H.I.T. for short)
> 
> I came across it recently on a project I was tasked to make a few
> seemingly simple fixes. The more I worked with the codebase, I started
> to wonder if the original author really knew S.H.I.T., or if he was just
> trying to throw S.H.I.T. together. 

Heh. Heh heh.

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by dusty <du...@yahoo.com>.
Wes, you are my hero.   And besides, Cold Fusion is making a huge come back
and is slated to take over for JSF.


Wes Wannemacher wrote:
> 
> On Tue, 2009-01-13 at 17:03 -0500, Musachy Barroso wrote:
>> On Tue, Jan 13, 2009 at 3:48 PM, SanJ.SANJAY <gi...@gmail.com> wrote:
>> >
>> >spring-Hibernate/JSF.
>> 
>> uh?
>> 
>> musachy
>> 
> 
> 
> I think he was referring to the - 
> Spring/Hibernate-JSF Integration Technology stack (S.H.I.T. for short)
> 
> I came across it recently on a project I was tasked to make a few
> seemingly simple fixes. The more I worked with the codebase, I started
> to wonder if the original author really knew S.H.I.T., or if he was just
> trying to throw S.H.I.T. together. 
> 
> Anyways, I was able to get in and get out, but decided that if I worked
> on it in the future, I would invest in a good pair of rubber gloves.
> 
> -Wes
> 
> (Thanks folks, I'll be here all week)
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Upgrading-Struts-from-1-to-2.0.14-tp21443421p21446445.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Wes Wannemacher <we...@wantii.com>.
On Tue, 2009-01-13 at 17:03 -0500, Musachy Barroso wrote:
> On Tue, Jan 13, 2009 at 3:48 PM, SanJ.SANJAY <gi...@gmail.com> wrote:
> >
> >spring-Hibernate/JSF.
> 
> uh?
> 
> musachy
> 


I think he was referring to the - 
Spring/Hibernate-JSF Integration Technology stack (S.H.I.T. for short)

I came across it recently on a project I was tasked to make a few
seemingly simple fixes. The more I worked with the codebase, I started
to wonder if the original author really knew S.H.I.T., or if he was just
trying to throw S.H.I.T. together. 

Anyways, I was able to get in and get out, but decided that if I worked
on it in the future, I would invest in a good pair of rubber gloves.

-Wes

(Thanks folks, I'll be here all week)



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Musachy Barroso <mu...@gmail.com>.
On Tue, Jan 13, 2009 at 3:48 PM, SanJ.SANJAY <gi...@gmail.com> wrote:
>
>spring-Hibernate/JSF.

uh?

musachy

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Dave Newton <ne...@yahoo.com>.
SanJ.SANJAY wrote:
 > Re-write? So if someone wants to upgrade struts,

If someone wants to upgrade from S1 to S2, yes. Of course, there's also 
S1.3, which is a much easier path--but you didn't say where you were 
coming from.

 > if thats the case then I think its the last thing
 > a developer will do.

Agreed; there needs to be a valid business need to re-write an 
application in a new framework. This is true no matter what.

> If I have re-write the application, I would rather look at 
 > some much better frameworks, like spring-Hibernate/JSF.

"Better" is, of course, *highly* subjective.

You'd have to *really* work to convince me that, say, JSF is (a) 
"better" than S2, and (b) an easier re-write (than to S2) from S1 (hint: 
it isn't).

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


RE: Upgrading Struts from 1 to 2.0.14

Posted by Radu Solomon <rs...@n-able.com>.
I second that point. We did same thing and only ported parts of S1 code when needed but the two run in parallel and interact beautifully. And the neat thing is we can use the dojo widgets from S2 in S1 pages. Not as is as in S2 but not very complex.

----------------------------------------------
Radu Solomon
Software Developer
N-able Technologies(r)
450 March Road, 4th Floor
Ottawa, Ontario
K2K 3K2
www.n-able.com

rsolomon@n-able.com
Tel: (613) 592-6676 x 301
Toll Free: 877-655-4689 x 301
Fax: (613) 592-2242

-----Original Message-----
From: Robert Graf-Waczenski [mailto:rgw@lsoft.com]
Sent: January 14, 2009 3:06 AM
To: Struts Users Mailing List
Subject: Re: Upgrading Struts from 1 to 2.0.14

Frank W. Zammetti wrote:
>
> Dave is 100% correct: S2 != S1.  They have a few concepts in common
> naturally, but there is, I think it's fair to say, more that makes
> them different than makes them alike.  A complete rewrite is probably
> the best bet (I heard tell of some porting possibilities, side-by-side
> execution possibilities, but I'm not sure what the status of those are).
>
> Or, as I said, no rewrite at all.  Sometimes leaving well enough alone
> really is the best option.

I'd suggest to not rewrite completely in one big bang but to do this in
a continuous process over time. In our shop here i'm currently working
with S2 in a (so we claim) highly complex application heavily using
Struts 1 (or, to say the truth, a custom-patched beta version of Struts
1). So we have here the typical scenario where actually upgrading
*everything* would be an effort in the mega-worker-hours region.
Therefore we decided to indeed run S2 in parallel with S1 and implement
new stuff with S2 and continue maintaining the old stuff in S1. (We may
or may not port old S1 actions to S2 in the future, that depends on the
issues we encounter. Existing and working S1 actions will definitely not
be touched!)
Running the two side-by-side works as expected (if you define the filter
mapping in your web.xml properly). We have a few battle-proven S1-based
actions that we need the new S2 actions to interact with, for this we
needed a few S2 struts.xml result definitions that redirect to S1-based
action URLs, and a few S1-based stuts-config.xml forward paths that
redirect to S2-based action URLs.
I would definitely say that this approach is good for any non-trivial
application. As an ultimate benefit, working with two frameworks in
parallel keeps your mind fresh :-)

Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by "SanJ.SANJAY" <gi...@gmail.com>.


Robert Graf-Waczenski wrote:
> 
> Frank W. Zammetti wrote:
>>
>> Dave is 100% correct: S2 != S1.  They have a few concepts in common 
>> naturally, but there is, I think it's fair to say, more that makes 
>> them different than makes them alike.  A complete rewrite is probably 
>> the best bet (I heard tell of some porting possibilities, side-by-side 
>> execution possibilities, but I'm not sure what the status of those are).
>>
>> Or, as I said, no rewrite at all.  Sometimes leaving well enough alone 
>> really is the best option.
> 
> I'd suggest to not rewrite completely in one big bang but to do this in 
> a continuous process over time. In our shop here i'm currently working 
> with S2 in a (so we claim) highly complex application heavily using 
> Struts 1 (or, to say the truth, a custom-patched beta version of Struts 
> 1). So we have here the typical scenario where actually upgrading 
> *everything* would be an effort in the mega-worker-hours region. 
> Therefore we decided to indeed run S2 in parallel with S1 and implement 
> new stuff with S2 and continue maintaining the old stuff in S1. (We may 
> or may not port old S1 actions to S2 in the future, that depends on the 
> issues we encounter. Existing and working S1 actions will definitely not 
> be touched!)
> Running the two side-by-side works as expected (if you define the filter 
> mapping in your web.xml properly). We have a few battle-proven S1-based 
> actions that we need the new S2 actions to interact with, for this we 
> needed a few S2 struts.xml result definitions that redirect to S1-based 
> action URLs, and a few S1-based stuts-config.xml forward paths that 
> redirect to S2-based action URLs.
> I would definitely say that this approach is good for any non-trivial 
> application. As an ultimate benefit, working with two frameworks in 
> parallel keeps your mind fresh :-)
> 
> Robert
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 

You are right Robert, thanks! keeping both S1 and S2 is a good option or
slowly upgrade to S2 completely. Makes lot of sense.


-- 
View this message in context: http://www.nabble.com/Upgrading-Struts-from-1-to-2.0.14-tp21443421p21458457.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Robert Graf-Waczenski <rg...@lsoft.com>.
Frank W. Zammetti wrote:
>
> Dave is 100% correct: S2 != S1.  They have a few concepts in common 
> naturally, but there is, I think it's fair to say, more that makes 
> them different than makes them alike.  A complete rewrite is probably 
> the best bet (I heard tell of some porting possibilities, side-by-side 
> execution possibilities, but I'm not sure what the status of those are).
>
> Or, as I said, no rewrite at all.  Sometimes leaving well enough alone 
> really is the best option.

I'd suggest to not rewrite completely in one big bang but to do this in 
a continuous process over time. In our shop here i'm currently working 
with S2 in a (so we claim) highly complex application heavily using 
Struts 1 (or, to say the truth, a custom-patched beta version of Struts 
1). So we have here the typical scenario where actually upgrading 
*everything* would be an effort in the mega-worker-hours region. 
Therefore we decided to indeed run S2 in parallel with S1 and implement 
new stuff with S2 and continue maintaining the old stuff in S1. (We may 
or may not port old S1 actions to S2 in the future, that depends on the 
issues we encounter. Existing and working S1 actions will definitely not 
be touched!)
Running the two side-by-side works as expected (if you define the filter 
mapping in your web.xml properly). We have a few battle-proven S1-based 
actions that we need the new S2 actions to interact with, for this we 
needed a few S2 struts.xml result definitions that redirect to S1-based 
action URLs, and a few S1-based stuts-config.xml forward paths that 
redirect to S2-based action URLs.
I would definitely say that this approach is good for any non-trivial 
application. As an ultimate benefit, working with two frameworks in 
parallel keeps your mind fresh :-)

Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
SanJ.SANJAY wrote:
> Re-write? So if someone wants to upgrade struts, they have to be prepared to
> re-write their application in new version ..if thats the case then I think
> its the last thing a developer will do. If I have re-write the application,
> I would rather look at some much better frameworks, like
> spring-Hibernate/JSF.
>
>   
Not sure I'd say JSF is a better framework than *anything*, but I digress...

You could always go with door #3: don't upgrade at all.  S1 is still a 
perfectly viable framework, and especially if you have no pressing need 
(other than resume padding), then what's the point of upgrading at all?  
There are TONS of perfectly good applications still in the wild running 
on S1, and no one is clamoring to update many of them.

Dave is 100% correct: S2 != S1.  They have a few concepts in common 
naturally, but there is, I think it's fair to say, more that makes them 
different than makes them alike.  A complete rewrite is probably the 
best bet (I heard tell of some porting possibilities, side-by-side 
execution possibilities, but I'm not sure what the status of those are).

Or, as I said, no rewrite at all.  Sometimes leaving well enough alone 
really is the best option.

Frank

-- 
Frank W. Zammetti
Author of "Practical Dojo Projects"
  and "Practical DWR 2 Projects"
  and "Practical JavaScript, DOM Scripting and Ajax Projects"
  and "Practical Ajax Projects With Java Technology"
  (For info: apress.com/book/search?searchterm=zammetti&act=search)
My "look ma, I have a blog too!" blog: zammetti.com/blog


>
>
> newton.dave wrote:
>   
>> SanJ.SANJAY wrote:
>>     
>>> Thanks Dave for the reply. I did not follow any process. I just wanted to
>>> upgrade Struts from1 to 2.0.14. SO read at the user guide that you just
>>> need
>>> to throw the *.jar files to your
>>> lib(http://struts.apache.org/1.x/userGuide/installation.html#Prerequisites).
>>>       
>> That says Struts 1; you said you were upgrading to Struts 2. Anything 
>> found in Struts 1 documentation, by definition, isn't particularly 
>> useful for Struts 2.
>>
>>     
>>> To upgrade is this not enough what is the complete process to do that?
>>>       
>> Re-write your application in Struts 2.
>>
>> I wasn't kidding when I said that Struts 2 is ***completely*** different 
>> than Struts 1.
>>
>> Dave
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
>>
>>
>>     
>
>   



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by stanlick <st...@gmail.com>.
Wes Obama -- 

You will make a fine Struts Czar once your publication is released.  Please
consider me for a cabinet position --  Newton can be my driver.

Peace,
Scott


Struts 1 is well-supported, and saw a new release just about a month
ago. So, it is supported and maintained. Struts 2 is a rewritten "next
generation" of Struts. If you are looking to get an existing project
up-to-date, just grab the latest Struts 1 release (if memory serves, it
is 1.3.10). If you are looking to move into a build an app from scratch,
and want to use a modern framework (yet quite a bit different from
Struts 1), then look at Struts 2. 

If you are considering the differences between the two, there is also a
good set of migration docs available here -

http://struts.apache.org/2.0.14/docs/migration-guide.html

There is also a Struts 1 / Struts 2 plugin, but depending on your
reasons for upgrading, I'm not sure that this is the route you want to
take.

-Wes


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org




-- 
View this message in context: http://www.nabble.com/Upgrading-Struts-from-1-to-2.0.14-tp21443421p21486320.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Wes Wannemacher <we...@wantii.com>.
On Tue, 2009-01-13 at 12:48 -0800, SanJ.SANJAY wrote:
> Re-write? So if someone wants to upgrade struts, they have to be prepared to
> re-write their application in new version ..if thats the case then I think
> its the last thing a developer will do. If I have re-write the application,
> I would rather look at some much better frameworks, like
> spring-Hibernate/JSF.
> 
> 

Struts 1 is well-supported, and saw a new release just about a month
ago. So, it is supported and maintained. Struts 2 is a rewritten "next
generation" of Struts. If you are looking to get an existing project
up-to-date, just grab the latest Struts 1 release (if memory serves, it
is 1.3.10). If you are looking to move into a build an app from scratch,
and want to use a modern framework (yet quite a bit different from
Struts 1), then look at Struts 2. 

If you are considering the differences between the two, there is also a
good set of migration docs available here -

http://struts.apache.org/2.0.14/docs/migration-guide.html

There is also a Struts 1 / Struts 2 plugin, but depending on your
reasons for upgrading, I'm not sure that this is the route you want to
take.

-Wes


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by "SanJ.SANJAY" <gi...@gmail.com>.
Re-write? So if someone wants to upgrade struts, they have to be prepared to
re-write their application in new version ..if thats the case then I think
its the last thing a developer will do. If I have re-write the application,
I would rather look at some much better frameworks, like
spring-Hibernate/JSF.




newton.dave wrote:
> 
> SanJ.SANJAY wrote:
>> Thanks Dave for the reply. I did not follow any process. I just wanted to
>> upgrade Struts from1 to 2.0.14. SO read at the user guide that you just
>> need
>> to throw the *.jar files to your
>> lib(http://struts.apache.org/1.x/userGuide/installation.html#Prerequisites).
> 
> That says Struts 1; you said you were upgrading to Struts 2. Anything 
> found in Struts 1 documentation, by definition, isn't particularly 
> useful for Struts 2.
> 
>> To upgrade is this not enough what is the complete process to do that?
> 
> Re-write your application in Struts 2.
> 
> I wasn't kidding when I said that Struts 2 is ***completely*** different 
> than Struts 1.
> 
> Dave
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Upgrading-Struts-from-1-to-2.0.14-tp21443421p21444194.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Dave Newton <ne...@yahoo.com>.
SanJ.SANJAY wrote:
> Thanks Dave for the reply. I did not follow any process. I just wanted to
> upgrade Struts from1 to 2.0.14. SO read at the user guide that you just need
> to throw the *.jar files to your
> lib(http://struts.apache.org/1.x/userGuide/installation.html#Prerequisites).

That says Struts 1; you said you were upgrading to Struts 2. Anything 
found in Struts 1 documentation, by definition, isn't particularly 
useful for Struts 2.

> To upgrade is this not enough what is the complete process to do that?

Re-write your application in Struts 2.

I wasn't kidding when I said that Struts 2 is ***completely*** different 
than Struts 1.

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by "SanJ.SANJAY" <gi...@gmail.com>.
Thanks Dave for the reply. I did not follow any process. I just wanted to
upgrade Struts from1 to 2.0.14. SO read at the user guide that you just need
to throw the *.jar files to your
lib(http://struts.apache.org/1.x/userGuide/installation.html#Prerequisites).
Thats all I did. To upgrade is this not enough what is the complete process
to do that ?? Would appreciate any insights.




newton.dave wrote:
> 
> SanJ.SANJAY wrote:
>> I am having some issues while upgrading the struts:
>> 
>> I dowloaded the latest 2.0.14 source from mirror and then copied all the
>> .jars from the /lib  folder to my application /lib folder. Now when I
>> restart my Jboss, it throws error for deploying my web application with
>> an
>> error:
>> 
>> java.lang.ClassCastException: org.apache.struts.tiles.TilesPlugin cannot
>> be
>> cast to org.apache.struts.action.PlugIn
>>         at
>> org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:855)
>>         at
>> org.apache.struts.action.ActionServlet.init(ActionServlet.java:356)
>>         at javax.servlet.GenericServlet.init(GenericServlet.java:211)
>>         at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
>>         at
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925)
>>      ....
>> 
>> 
>> :confused:
>> 
>> So I am not sure if this error comes because of new jar files that I
>> added
>> to upgrade struts or I did not follow the complete process for upgrading
>> the
>> struts. Any insights???
> 
> Not knowing what process you followed for the upgrade it's really hard 
> to say. I'll note, however, that you can't just randomly throw jar files 
> into a project and expect it to work.
> 
> Struts 2 is *completely* different from Struts 1. Can you be more 
> specific as to what you've already done?
> 
> Dave
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Upgrading-Struts-from-1-to-2.0.14-tp21443421p21443799.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Upgrading Struts from 1 to 2.0.14

Posted by Dave Newton <ne...@yahoo.com>.
SanJ.SANJAY wrote:
> I am having some issues while upgrading the struts:
> 
> I dowloaded the latest 2.0.14 source from mirror and then copied all the
> .jars from the /lib  folder to my application /lib folder. Now when I
> restart my Jboss, it throws error for deploying my web application with an
> error:
> 
> java.lang.ClassCastException: org.apache.struts.tiles.TilesPlugin cannot be
> cast to org.apache.struts.action.PlugIn
>         at
> org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:855)
>         at
> org.apache.struts.action.ActionServlet.init(ActionServlet.java:356)
>         at javax.servlet.GenericServlet.init(GenericServlet.java:211)
>         at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
>         at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925)
>      ....
> 
> 
> :confused:
> 
> So I am not sure if this error comes because of new jar files that I added
> to upgrade struts or I did not follow the complete process for upgrading the
> struts. Any insights???

Not knowing what process you followed for the upgrade it's really hard 
to say. I'll note, however, that you can't just randomly throw jar files 
into a project and expect it to work.

Struts 2 is *completely* different from Struts 1. Can you be more 
specific as to what you've already done?

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org