We are using NAS4.0.. and my recommendations
1) The builder NAB4.0 sucks... it is neither a good editor nor a good IDE
2) NAS4.0 often throws this GX2GX Socket Result code missing error.. which can happen for some hazar different reasons and you have no clue why it happens... debugging is a pain in such cases
3) The runtime error stack trace often gives inadequate information
4) Connection pooling never worked on Unix platforms.
5) Entity beans not fully supported
6) the runtime only supports jdk1.1.7 or earlier versions.. not compatible if you intend using jdk1.2
5) I can go on... but in a nutshell NAS4.0 is a simple and rapid hack over their earlier NAS3.0 i.e the applogic version, released with the sole objective of being among the first j2ee compliant ejb servers.
Finally I'd say, evaluate their iplanet6.0 which they claim is fully ejb compliant and has jdk1.2 runtime..or even better, if you have an option, go for different vendors viz. IAS or Weblogic etc..
~Prasad
-----Original Message-----
From: Ravindra Balija [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, April 13, 2000 10:21 AM
To: [EMAIL PROTECTED]
Subject: Regarding NAS 4.0 using EJB
Dear ALL,
Does anybody in the list have any experiences with NAS 4.0
implementation EJB Support and JSP support? We are going into the
coding phase soon. I would like to know are there any pitfalls which
we need to take care of. Please let us know so that we could avoid
making the same mistakes.
Thanks with regards,
Ravindra
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
