Re: Compiling basicPortal with NetBeans 3.5 (i.e. Tomcat 4.0.6)?

Thanks for the kind words.

Yes one issue with J2EE free choices is that no 2 organizations have
the same configuration.

You have a choice of 10 IDE, 10 VM, 10 Containers, 10 DBs, 10 OS, etc.
That is 10 to the 5th power of combinations, but realy a lot more.

Tha tis one of the reasons I ship IDE, JVM, DB and app. server is to
lower the odds of .... oh, this combination was not tested; But allow
for any SQL db of 10 supported by iBatis, and any J2EE, IDE, etc.

I will be teaching online again, most likely class starting after 5/17,
similar topics and this "new code", all prior students are welcome
(free) and as always hands on required.

.V

ps: I had some issues w/ Sun 1.4.1.02! and Sun VM's in generals so I
use other VMs.

Hue Holleran wrote:

Vic,

I definetly tested under Tomcat 4.1.x. <<

Problem seems to be with tomcat shipped with netbeans:

I get exactly the same compilation error under Linux (Debian) using netbeans
3.5 (caveat: beta): "java.lang.ExceptionInInitializerError ...
java.lang.NullPointerException at
org.apache.struts.util.MessageResources.getMessageResources(MessageResources
.java:577)" running Sun's JDK 1.4.1_02 as Win2k running netbeans 3.5 running
Sun's JDK 1.4.1_02 and it looks like a problem loading messages property
bundle - so at least I'm starting to get a little consistency! This also
generates same error under latest netbeans release 3.4.1 on Linux (Debian)
running Sun's JDK 1.4.1_02 - but I'm not sure if this is a JDK 1.4.1_02
issue or a netbeans issue.

ALSO - the strutsel-exercise-taglib.war (expanded) from
jakarta-struts-20030424 nightly (later nightlies do not have contrib/el as
there must be a compilation problem for auto builder again) gives exactly
the same error under netbeans! Which points to a more general problem with
el taglibs or a more general problem with tomcat 4.0.6 bundled with netbeans
(or Sun's JDK 1.4.1_02?) not being able to load messages property bundle.

BUT bp deploys and runs faultlessly under Tomcat 4.0.3 (from Debian 'stable'
.deb) and latest Tomcat 4.0.6 (from jakarta) on Linux (Debian) again running
Sun's JDK 1.4.1_02 - so it is not a problem specific to bp - I have checked
netbeans issuezilla but cannot find any related bug so will post to netbeans
list and check. Sorry to have taken your time on this.

*The configuration for Tomcat 4.1.x is in DOCO.*, with data source,so I

did not mess with SQL mapping, just the data source. <<

Yes, thanks - I did check the server.xml but to be honest wanted to
understand ibatis-db and ScaffoldXPress a little better - so got source and
started trying different settings.

I must say I'm very impressed with both the lower-level ibatis and
ScaffoldXPress's highler-level bean+DAOhelper approach - your basebeans
tuition was extremely useful in getting to understand what appears to be a
very high-performance architecture. Kudos to the ibatis developers and to
you and your colleagues in using ibatis in such a reusable and approachable
way. bp is a very nice demonstration app to demonstrate the power of both
ibatis and ScaffoldXPress and shows what can really be done with relatively
very little code.

Thanks again,

Hue.