× 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.



Now that I think of it, how about creating a web service to access the US
Postal service module that we just saw Sarah Poger post not too long ago.
That way it wouldn't be wasted code, somebody should be able to use that.

Thoughts?

Aaron Bartell

-----Original Message-----
From: Bartell, Aaron L. (TC) [mailto:ALBartell@xxxxxxxxxxxxxx]
Sent: Thursday, July 24, 2003 4:10 PM
To: 'WDSCI-L@xxxxxxxxxxxx'
Subject: [WDSCI-L] Getting to the bones with Java and .NET was -> RE:
RE: WDSC and Linux


We have been having a discussion on the CODE list, and it might be more
appropriate here.  We are looking at the steps needed to create a
process(undefined as of right now) from both a Java IDE (WDSc) and a M$
product(Visual Studio).


>Let me know if you want to follow up on that at some point.
Sounds good and I agree that this would clear out a lot of the blanket
statements that are being made without any details behind them.

>We'd probably have to move the discussion over to WEB400-L or maybe
WDSCI-L(because the WDSC folks would get a major benefit from hearing the
comparisons).
Cool.

>But mabye you and I could do a comparison of writing a simple application
using JSP Model II and .NET, and provide folks with some real comparisons?
Sounds good.

Hopefully I will be able to learn more about WDSc and Java with this
comparison.  Right now I still use Sun ONE Studio, because setting up
projects in WDSc was too confusing, and I couldn't make it work with my
existing namespace structure.


Aaron Bartell

-----Original Message-----
From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx]
Sent: Thursday, July 24, 2003 4:01 PM
To: CODE/400 Discussion & Support
Subject: RE: RE: WDSC and Linux


> From: Bartell, Aaron L.
>
> Maybe I haven't been doing .NET long enough (3 - 5 weeks), but from what I
> can tell you don't lose that capability to debug low enough to
> figure things
> out.  The code is there, it was just a lot easier to create.

Well, maybe out of all this we can generate an opportunity <grin>.  I don't
currently have access to .NET - 1800 bucks is a lot to shell out for a
development tool.  But mabye you and I could do a comparison of writing a
simple application using JSP Model II and .NET, and provide folks with some
real comparisons?

We'd probably have to move the discussion over to WEB400-L or maybe WDSCI-L
(because the WDSC folks would get a major benefit from hearing the
comparisons).

Let me know if you want to follow up on that at some point.

Joe

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

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.