Re: plain JSP in a ASP.NET page

Tech-Archive recommends: Fix windows errors by optimizing your registry

> What do you mean by "the lowest pages"? Thanks for the great advice.
> And
Sorry for the confusion. I meant if you were to have the index.jsp as the
top of the tree, and the rest of your jsp pages fanning down out from there.
So then, pick on leaf/jsp, and start working upwards with new aspx pages.
That way, you can handle isolated jsps and their associated servlets one at
a time. When you convert the jsp to aspx, you can write the button handlers
as well (to replace the servlets). That way, you would only ever be
bridging one jsp to aspx gap at any one time and hopefully you can do this
with the querystring (url) or maybe even with your db. The bad thing is
you'll always be doing that bridge from jsp to aspx until you complete the
whole app. What's another way? Take one entire sub tree and convert it to
aspx, but from the top level (index.jsp I assume) you're starting with a
jsp, so either way, you're going to have this issue to contend with

After thinking about it a bit, the first thing to handle is probably taking
a look at some global utilities and maybe your data layer and convert that
stuff over first. Are you using an Oracle or MS db? Are you using EJBs?
Custom tags? What about a lot of utility/static methods/classes? You might
be able to get away with moving those bigger pieces over to .net code when
you run into them.

> no, I'm not in Ontrario, sorry.
Too bad. :< Oh well, c'est la vie I guess. Good luck! :>


.

Quantcast