Re: Oracle Unit Testing

From: joel garry <joel-garry_at_home.com>
Date: 31 Jan 2007 11:16:12 -0800
Message-ID: <1170270972.000323.303010@a75g2000cwd.googlegroups.com>

On Jan 31, 7:57 am, "WebCom Systems" <i..._at_webcomsystems.co.uk> wrote:
> You guys are obviously not familiar with scalable J2EE applications.

That is true. Could you give an example of one?

>
> The point of using objects is that you can pass a completely
> structured object containing the data to the Java layer of the
> application.

Perhaps I would see this point if you would put it in terms of relational algebra.

>
> Objects can not only be data structured and also contain other
> objects.

Uhhhhh... java.lang.reflect.InvocationTargetException

at sun.reflect.GeneratedConstructorAccessor9.newInstance(Unknown Source)

at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java: 27)

at java.lang.reflect.Constructor.newInstance(Constructor.java: 274)

at
org.apache.poi.hssf.record.RecordFactory.createRecord(RecordFactory.java: 213)

at
org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.java: 149)

at
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java: 183)

at
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java: 152)

at
com.bnpparibas.grp.framework.testing.testpack.TestPackReader.<init>(TestPackReader.java: 114)

at
com.bnpparibas.grp.framework.testing.testpack.TestPackReaderTest.testTestPack(TestPackReaderTest.java: 13)

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25)

      at java.lang.reflect.Method.invoke(Method.java:324)
      at junit.framework.TestCase.runTest(TestCase.java:154)
      at junit.framework.TestCase.runBare(TestCase.java:127)
      at junit.framework.TestResult$1.protect(TestResult.java:106)
      at junit.framework.TestResult.runProtected(TestResult.java:124)
      at junit.framework.TestResult.run(TestResult.java:109)
      at junit.framework.TestCase.run(TestCase.java:118)
      at junit.framework.TestSuite.runTest(TestSuite.java:208)
      at junit.framework.TestSuite.run(TestSuite.java:203)
      at junit.textui.TestRunner.doRun(TestRunner.java:116)

atcom.intellij.rt.execution.junit.IdeaTestRunner.doRun(IdeaTestRunner.java: 69)

      at junit.textui.TestRunner.doRun(TestRunner.java:109)
      at

com.intellij.rt.execution.junit.IdeaTestRunner.startRunnerWithArgs(IdeaTestRunner.java: 24)

at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java: 118)

at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java: 40)

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25)

      at java.lang.reflect.Method.invoke(Method.java:324)
      at

com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: 12007

      at java.lang.String.checkBounds(String.java:287)
      at java.lang.String.<init>(String.java:319)
      at

org.apache.poi.util.StringUtil.getFromCompressedUnicode(StringUtil.java: 163)

at
org.apache.poi.hssf.record.StringRecord.fillFields(StringRecord.java: 89)

      at org.apache.poi.hssf.record.Record.<init>(Record.java:55)
      at
org.apache.poi.hssf.record.StringRecord.<init>(StringRecord.java:51)
      ... 32 more

org.apache.poi.hssf.record.RecordFormatException: Unable to construct record instance, the following exception occured: null

at
...

>
> In terms of maintenance, a highly modular multi-tiered approach of far
> better for maintenance than a flatter 2-teir traditional architecture.
> The point of multi-tiered applications is that every bit of code is in
> its correct place, DML in the table encapsulation layer, objects in
> the object layer, business logic in the java layer, and so on...

Well, this actually almost makes sense. Except the part about business
logic in the java layer. What's so great about java? Over the past few
months, it's been the greatest source of problems on my home peecee, that's for sure. For a business, I would want to centralize the business
logic, which means a database, though not necessarily the same database
as the data. And yet, the n-tier version of the app I work on prefers IIS,
so I prefer the 3-tier version, even though that means most of the logic
is in reusable or library compiled 4GL code... but at least it works.

--
@home.com is bogus.
http://www.arcade-history.com/index.php?page=detail&id=1644

Received on Wed Jan 31 2007 - 13:16:12 CST