Damian,

I don't know if you have read the ND release
 on the migration, but the official party 
line is to write your applications to the 
J2EE standard.  

I am facing a similar situation, and we 
decided that the application would be 
basically a rewrite regardless of what 
standards we adhered to.  We are placing 
chunks of business logic in EJB's such that 
theoretically they can be reused.  However, 
we realized that by forsaking the use of the 
spider classes we would not get the 
advantages of ND.  

If the event model of ND is gone, then the 
front-end of the application must be re-
created.  This in turn affects how you use 
the business logic.  Since we don't know 
what iPlanet is going to be like (from an 
IDE perspective), i.e. will there be an 
event model that gives you a hook to the 
equivalent of a 'onSubmit' event, we decided 
to take advantage of the here & now powers 
of ND.

Regarding your migration to ND5 first:  The 
major issues in the ND5 migration will 
center around the change from C++ database 
access to JDBC access.  No further spider 
changes are made, to my knowledge.  There 
are still a lot of issues with the JDBC 
access (Oracle 'no columns' and synonm 
issues come to mind), but for the most part 
these can be worked around.  ND5 will be 
supported for at least 2 years (more if you 
consider the first release of iPlanet has a 
ND5 app. server built in) and I believe the 
general consensus is that ND5 is a superior 
product to ND4 (better performance, IDE 
improvements, etc...).

I know this clears nothing up.  It may have 
even muddled my waters more.  I just thought 
you might like to know our decision points.

Lance Cannon
[EMAIL PROTECTED]

"Damian O'Connor" <[EMAIL PROTECTED]> wrote:
>
>Hi folks,
>
>Firstly I'd like to say I use this forum 
>considerably and hold in high regard the 
>information that is posted here. Undoubtly 
>it has saved our team months of work when we 
>moved from ND3 to ND4 earlier this year.
>
>Now though, what do we do? We have a 
>considerable amount of work coming up early 
>next year and with the demise of ND4 support 
>we are looking at our possible path forward. 
>
>Do we go ND4->ND5->iPlanet, or do we take a 
>risk and go ND4->iPlanet. Do we drop ND 
>completely and go something else? Given that we didn't fully move to the ND4 event 
>model 
>what are our risks by going directly to ND5 
>or iPlanet? What code migration is required?
>
>We don't use EJB's so if we move ND5->iPlant 
>should we write EJB's to allow us to move 
>to J2EE. To be honest the whole thing is 
>confusing and I'm hoping somebody out there 
>is in the same position and has evaluated 
>the best path forward. The discussions in 
>this forum to date give me the impression 
>that alot of people are in the same boat as 
>ourselves.
>
>ND have given us some good feedback, but 
>what is the average punter doing?
>
>Regards,
>Damian O'Connor
>Hewlett Packard
>Ireland
>

_________________________________________________________________________

For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html

For dire need help, email: [EMAIL PROTECTED]

Reply via email to