| VisualAge migration [message #112760] |
Thu, 08 December 2005 13:16  |
Eclipse User |
|
|
|
Originally posted by: goodwin.essence.co.uk
We have maybe 200,000 lines of code in VisualAge, much of it generated by
the Visual Composition editor. We are now migrating to Eclipse. We develop a
commercial application product.
This seems to work OK, but we use the VAJ 'Use one inner class for all
events' style. This seems to be intepreted OK by eclipse, but as we develop
in eclipse it seems to only generate the 'Use an inner class for each event'
style.
It therefore seems advaantageous for future maintenance to keep a single
style, and first regenerate all Java code by first changing the VAJ option
to 'Use an inner class for each event'. We have maybe 50 beans which would
need regeneration.
Does this make sense and is it recommended? I have found very little on
hints and tips for migration from VAJ, but I am sure a lot of people have
thought hard about this process and have hard won experiences.
|
|
|
|
| Re: VisualAge migration [message #112798 is a reply to message #112786] |
Fri, 09 December 2005 06:46  |
| Eclipse User |
|
|
|
Originally posted by: goodwin.essence.co.uk
Thanks. I was a little nervous about regenerating under a different style
myself.
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
news:dnag0t$dv2$1@news.eclipse.org...
> I don't recommend it. It sounds like it would be the best way, but we
> found there was a bug in VA Java when trying to that regeneration. I
> would say just leave it alone and as you go forward use more and more of
> the new style.
>
> Nigel wrote:
> > We have maybe 200,000 lines of code in VisualAge, much of it generated
by
> > the Visual Composition editor. We are now migrating to Eclipse. We
develop a
> > commercial application product.
> >
> > This seems to work OK, but we use the VAJ 'Use one inner class for all
> > events' style. This seems to be intepreted OK by eclipse, but as we
develop
> > in eclipse it seems to only generate the 'Use an inner class for each
event'
> > style.
> >
> > It therefore seems advaantageous for future maintenance to keep a single
> > style, and first regenerate all Java code by first changing the VAJ
option
> > to 'Use an inner class for each event'. We have maybe 50 beans which
would
> > need regeneration.
> >
> > Does this make sense and is it recommended? I have found very little on
> > hints and tips for migration from VAJ, but I am sure a lot of people
have
> > thought hard about this process and have hard won experiences.
> >
> >
>
> --
> Thanks,
> Rich Kulp
|
|
|
| Re: VisualAge migration [message #611514 is a reply to message #112760] |
Thu, 08 December 2005 18:35 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I don't recommend it. It sounds like it would be the best way, but we
found there was a bug in VA Java when trying to that regeneration. I
would say just leave it alone and as you go forward use more and more of
the new style.
Nigel wrote:
> We have maybe 200,000 lines of code in VisualAge, much of it generated by
> the Visual Composition editor. We are now migrating to Eclipse. We develop a
> commercial application product.
>
> This seems to work OK, but we use the VAJ 'Use one inner class for all
> events' style. This seems to be intepreted OK by eclipse, but as we develop
> in eclipse it seems to only generate the 'Use an inner class for each event'
> style.
>
> It therefore seems advaantageous for future maintenance to keep a single
> style, and first regenerate all Java code by first changing the VAJ option
> to 'Use an inner class for each event'. We have maybe 50 beans which would
> need regeneration.
>
> Does this make sense and is it recommended? I have found very little on
> hints and tips for migration from VAJ, but I am sure a lot of people have
> thought hard about this process and have hard won experiences.
>
>
--
Thanks,
Rich Kulp
|
|
|
| Re: VisualAge migration [message #611515 is a reply to message #112786] |
Fri, 09 December 2005 06:46 |
| Eclipse User |
|
|
|
Thanks. I was a little nervous about regenerating under a different style
myself.
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> wrote in message
news:dnag0t$dv2$1@news.eclipse.org...
> I don't recommend it. It sounds like it would be the best way, but we
> found there was a bug in VA Java when trying to that regeneration. I
> would say just leave it alone and as you go forward use more and more of
> the new style.
>
> Nigel wrote:
> > We have maybe 200,000 lines of code in VisualAge, much of it generated
by
> > the Visual Composition editor. We are now migrating to Eclipse. We
develop a
> > commercial application product.
> >
> > This seems to work OK, but we use the VAJ 'Use one inner class for all
> > events' style. This seems to be intepreted OK by eclipse, but as we
develop
> > in eclipse it seems to only generate the 'Use an inner class for each
event'
> > style.
> >
> > It therefore seems advaantageous for future maintenance to keep a single
> > style, and first regenerate all Java code by first changing the VAJ
option
> > to 'Use an inner class for each event'. We have maybe 50 beans which
would
> > need regeneration.
> >
> > Does this make sense and is it recommended? I have found very little on
> > hints and tips for migration from VAJ, but I am sure a lot of people
have
> > thought hard about this process and have hard won experiences.
> >
> >
>
> --
> Thanks,
> Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.04309 seconds
Home