Axiant experiences

Wed, 31 Jul 2002 09:55:19 -0700

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C238B3.0D8CFC00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Java is more robust that Axiant? Not sure I would agree
with that. If you're already an Oracle development partner,
why not use Developer 2000, or whatever it's called now?

-----Original Message-----
From: Pantos, Jim [mailto:Jim.Pantos@amisysllc.com]
Sent: Wednesday, July 31, 2002 7:59 AM
To: 'powerh-l@lists.swau.edu'; Bob Edis; Darren Reely; James Byrne; =
Witkopp,
Richard; Sam DeLeese; Steve Franklin
Subject: Axiant experiences

I am with a company located in the Washington DC metro area that is
considering migrating our HP-e3000 quick code to Axiant.  We have a =
large
application with about 1500 Quick screens, 500 of which are relatively
complex (from 1000 - 6000 lines of code).  One idea we are considering =
is
migrating our screens to Axiant to provide our clients with a GUI =
interface
in the short term (next 1-3 years), and then initiating a brand new
development project with a newer tool that provides a more robust =
toolset.
Another alternative we have been considering is scrapping the Axiant =
plan
altogether and initiating the new development project immediately, =
using
Java with Jdeveloper, and using a very methodical phased approach so we =
can
avoid the pitfalls of trying to convert a large system all in one bite. =
 We
have already committed to Oracle for our database solution and are now =
an
Oracle development partner, so this might be a low cost alternative for =
us.
We have been prototyping Axiant 3.1 running against HP-UX server and =
Oracle
database for a few months now and have found a lot of roadblocks that =
have
been very frustrating for us.  We have also been disappointed with the
limited features of Axiant vis-=E0-vis a more fully object-oriented
development tool.  We are going to install Axiant beta 3.4 in the near
future and do some further prototyping, but as with most projects these
days, we need to make a decision very soon, so we need to get informed =
as
quickly as we can.

My question is: Do any of you work at an Axiant development shop that =
is
also running Axiant in production?  What I really need is to be able to
visit a couple of development shops that have in-house developers, have
implemented Axiant and will give me an honest evaluation of the issues =
you
have confronted during your migration/development effort.  We really =
need to
know if our migration to Axiant is worthwhile for this relatively =
short-term
goal, how severe the issues are that we have found, and what sort of
workarounds you may have discovered through your own experiences.  =
Ideally,
we'd like to find someone close enough to our location that we could =
visit
in a day, but I'd really appreciate any feedback any of you might have =
for
me.  We would really appreciate the opportunity to come and pay you a =
visit.

Please feel free to contact me directly at my e-mail address, which is
listed below, or via the listserver.=20

Thanks!=20

Jim Pantos=20
Sr. Technical Development Advisor=20
AMISYS LLC.=20
Phone: 301-315-7211=20
Email: Jim.Pantos@amisysllc.com=20

Confidentiality Notice: This email message, including any attachments, =
is
for the sole use of the intended recipient and may contain confidential =
and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, =
please
contact the sender by reply e-mail and destroy all copies of the =
original
message

------_=_NextPart_001_01C238B3.0D8CFC00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Axiant experiences</TITLE>

<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV>Java=20
is more robust that Axiant? Not sure I would agree</DIV>
<DIV>with=20
that. If you're already an Oracle development =
partner,</DIV>
<DIV>why=20
not use Developer 2000, or whatever it's called =
now?</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">
 <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr>-----Original Message----- From: Pantos, Jim=20
 [mailto:Jim.Pantos@amisysllc.com] Sent: Wednesday, July 31, =
2002=20
 7:59 AM To: 'powerh-l@lists.swau.edu'; Bob Edis; Darren =
Reely; James=20
 Byrne; Witkopp, Richard; Sam DeLeese; Steve =
Franklin Subject: Axiant=20
 experiences </DIV>
 I am with a company located in the =
Washington DC=20
 metro area that is considering migrating our HP-e3000 quick code to=20
 Axiant.&nbsp; We have a large application with about 1500 Quick =
screens, 500=20
 of which are relatively complex (from 1000 - 6000 lines of =
code).&nbsp; One=20
 idea we are considering is migrating our screens to Axiant to provide =
our=20
 clients with a GUI interface in the short term (next 1-3 years), and =
then=20
 initiating a brand new development project with a newer tool that =
provides a=20
 more robust toolset.&nbsp; Another alternative we have been =
considering is=20
 scrapping the Axiant plan altogether and initiating the new =
development=20
 project immediately, using Java with Jdeveloper, and using a very =
methodical=20
 phased approach so we can avoid the pitfalls of trying to convert a =
large=20
 system all in one bite.&nbsp; We have already committed to Oracle for =
our=20
 database solution and are now an Oracle development partner, so this =
might be=20
 a low cost alternative for us.&nbsp; We have been prototyping Axiant =
3.1=20
 running against HP-UX server and Oracle database for a few months now =
and have=20
 found a lot of roadblocks that have been very frustrating for =
us.&nbsp; We=20
 have also been disappointed with the limited features of Axiant =
vis-=E0-vis a=20
 more fully object-oriented development tool.&nbsp; We are going to =
install=20
 Axiant beta 3.4 in the near future and do some further prototyping, =
but as=20
 with most projects these days, we need to make a decision very soon, =
so we=20
 need to get informed as quickly as we can.
 My question is: Do any of you work at =
an Axiant=20
 development shop that is also running Axiant in production?&nbsp; =
What I=20
 really need is to be able to visit a couple of development shops that =
have=20
 in-house developers, have implemented Axiant and will give me an =
honest=20
 evaluation of the issues you have confronted during your =
migration/development=20
 effort.&nbsp; We really need to know if our migration to Axiant is =
worthwhile=20
 for this relatively short-term goal, how severe the issues are that =
we have=20
 found, and what sort of workarounds you may have discovered through =
your own=20
 experiences.&nbsp; Ideally, we'd like to find someone close enough to =
our=20
 location that we could visit in a day, but I'd really appreciate any =
feedback=20
 any of you might have for me.&nbsp; We would really appreciate the =
opportunity=20
 to come and pay you a visit.
 Please feel free to contact me =
directly at my=20
 e-mail address, which is listed below, or via the listserver. =

 Thanks! 
 Jim Pantos =

Sr. Technical=20
 Development Advisor AMISYS LLC. Phone: 301-315-7211 Email: =
Jim.Pantos@amisysllc.com 
 Confidentiality Notice:=20
 This email message, including any attachments, is for the sole use of =
the=20
 intended recipient and may contain confidential and privileged =
information.=20
 Any unauthorized review, use, disclosure or distribution is =
prohibited. If you=20
 are not the intended recipient, please contact the sender by reply =
e-mail and=20
 destroy all copies of the original=20
message </BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C238B3.0D8CFC00--