× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Aaron,

Thanks much for the detailed note.  I'm leaning toward Java for the
reasons you mentioned.  

Do you know anything about the WebSphere Development Studio and the
WebSphere Host Publisher Studio?  I have that as part of my iSeries
Enterprise License.   Should I also have the WDSc as well as part of my
iSeries license?  If so, do you know what disks it is found on?

Thanks,

Dave 

>>> albartell@xxxxxxxxx 8/4/2005 09:55:23 >>>
Based on your requirements and IBM's support of Java I would definitely
go
with Java for every tier with DB2 on the backend. Some may disagree
with my
assessment and recommendation, but there is so many good things about
Java
and it's future that it makes an excellent long term commitment.  

I have an application I have been working on for the past 9 months that
uses
JSF (JavaServer Faces), Hibernate, and MySQL (among other open source
technologies). My development environment is Eclipse with the
MyEclipseIDE.com plugin. This environment has served me quite well and
I
love it!  Just so you know from where I speak, I am traditionally an
RPG
programmer (about 6 years)who has been using WDSc since 4.0 and have
been
making a gradual change to Java for the past 5 years or so.

The reason I would go with one language (Java) is because that gives
you
very easy debugging capabilities right from within your IDE. You can
step
into the different tiers with the nice debugger included in Eclipse.
Note
that if you have a software license with IBM you can get WDSc v6.0 at
no
additional charge, and it has very nice support for JSF (along with
many
other things).  

HTH,
Aaron Bartell

-----Original Message-----
>From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]

>On
>Behalf Of Dave Odom
>Sent: Wednesday, August 03, 2005 4:11 PM
>To: web400@xxxxxxxxxxxx 
>Subject: [WEB400] Recommendations on development language/environment

>for webpresentation layer
>
>Fellow iSeries developers,
>
>What are your best recommendations for development language, 
>environment, tools, etc., to create a web presentation layer and 
>application layer over iSeries tables that make up an iSeries Data
>Warehouse/Data Mart/Operational Data Store.   As an aside, the
>database
>will be DB2 tables created via DDL and access from the presentation 
>layer/application layer will be via SQL and stored procedures
fostering 
>static SQL on the iSeries as much as possible.
>
>Since I'll do a prototype and then the production application, I'd
like 
>a toolset that allows for easy development of the first and flow into
>the second.   I'd like the language/development environment NOT to be
>esoteric and out of the skills mainstream.  I'd like the 
>language/development environment to facilitate ease of development,
>maintenance and rapid development.    I'd like the
>language/development
>environment to have a track record and probability of being around in

>the future.
>
>Having said all the "wants", I'll entertain alternative suggestions.
>
>Thanks in advance,
>
>Dave Odom
>Arizona
>  
>
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To
post a
message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list
options,
visit: http://lists.midrange.com/mailman/listinfo/web400 
or email: WEB400-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.