Export fullDataSet to XML from MS SQL Server 2005

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Export fullDataSet to XML from MS SQL Server 2005

William Anderson-4
New to dbUnit -- Having problems trying to export fullDataSet to XML from Microsoft SQL Server 2005
Any help would be appreciated --Thanks

Microsoft SQL Server Management Studio                      9.00.4035.00
Microsoft Analysis Services Client Tools                        2005.090.4035.00
Microsoft Data Access Components (MDAC)                  6.1.7600.16385 (win7_rtm.090713-1255)
Microsoft MSXML                                                         3.0 6.0
Microsoft Internet Explorer                                            8.0.7600.16385
Microsoft .NET Framework                                            2.0.50727.4952
Operating System                                                        6.1.7600

Code snippet --

IDatabaseConnection connection = null;
        try {
            // database connectionG
            log.info("-- Start Connection --");
            Class driverClass = Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
            Connection jdbcConnection = DriverManager.getConnection(url + dbName, userName, password);
            connection = new DatabaseConnection(jdbcConnection);
            log.info("-- End Connection --");
        } catch (Exception e) {
            e.printStackTrace();
        }
       
               
     try {
         // full database export
         log.info("-- Start Full Data Set --");
         String fullDataSetName = "fullMSSQLGenius.xml";
         IDataSet fullDataSet = connection.createDataSet();
            FlatXmlDataSet.write(fullDataSet, new FileOutputStream(fullDataSetName));
         log.info("-- EndFull Data Set --");
    } catch (Exception e) {
        e.printStackTrace();
    }

[                          main] AbstractTableMetaData          WARN  Potential problem found: The configured data type factory 'class org.dbunit.dataset.datatype.DefaultDataTypeFactory' might cause problems with the current database 'Microsoft SQL Server' (e.g. some datatypes may not be supported properly). In rare cases you might see this message because the list of supported database products is incomplete (list=[derby]). If so please request a java-class update via the forums.If you are using your own IDataTypeFactory extending DefaultDataTypeFactory, ensure that you override getValidDbProducts() to specify the supported database products.
org.dbunit.dataset.DataSetException: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'End'.
    at org.dbunit.database.DatabaseDataSet.getTable(DatabaseDataSet.java:323)
    at org.dbunit.database.DatabaseTableIterator.getTable(DatabaseTableIterator.java:89)
    at org.dbunit.dataset.stream.DataSetProducerAdapter.produce(DataSetProducerAdapter.java:83)
    at org.dbunit.dataset.xml.FlatXmlWriter.write(FlatXmlWriter.java:124)
    at org.dbunit.dataset.xml.FlatXmlDataSet.write(FlatXmlDataSet.java:378)
    at com.glynlyon.GeniusDBFullBackup.testMSSQLGeniusFullDataSetExport(GeniusDBFullBackup.java:84)
    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:597)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'End'.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
    at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(Unknown Source)
    at org.dbunit.database.AbstractResultSetTable.<init>(AbstractResultSetTable.java:110)
    at org.dbunit.database.ForwardOnlyResultSetTable.<init>(ForwardOnlyResultSetTable.java:59)
    at org.dbunit.database.CachedResultSetTableFactory.createTable(CachedResultSetTableFactory.java:60)
    at org.dbunit.database.DatabaseDataSet.getTable(DatabaseDataSet.java:319)
    ... 31 more


------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
dbunit-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/dbunit-user
Reply | Threaded
Open this post in threaded view
|

Re: Export fullDataSet to XML from MS SQL Server 2005

Jeff Jensen-2
Just guessing; perhaps setting the DataType factory [0] will resolve
the problem?

[0] http://www.dbunit.org/properties.html


On Sat, Apr 23, 2011 at 8:25 PM, William Anderson
<[hidden email]> wrote:

> New to dbUnit -- Having problems trying to export fullDataSet to XML from
> Microsoft SQL Server 2005
> Any help would be appreciated --Thanks
>
> Microsoft SQL Server Management Studio                      9.00.4035.00
> Microsoft Analysis Services Client Tools
> 2005.090.4035.00
> Microsoft Data Access Components (MDAC)                  6.1.7600.16385
> (win7_rtm.090713-1255)
> Microsoft MSXML                                                         3.0
> 6.0
> Microsoft Internet Explorer
> 8.0.7600.16385
> Microsoft .NET Framework
> 2.0.50727.4952
> Operating System
> 6.1.7600
>
> Code snippet --
>
> IDatabaseConnection connection = null;
>         try {
>             // database connectionG
>             log.info("-- Start Connection --");
>             Class driverClass =
> Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
>             Connection jdbcConnection = DriverManager.getConnection(url +
> dbName, userName, password);
>             connection = new DatabaseConnection(jdbcConnection);
>             log.info("-- End Connection --");
>         } catch (Exception e) {
>             e.printStackTrace();
>         }
>
>
>      try {
>          // full database export
>          log.info("-- Start Full Data Set --");
>          String fullDataSetName = "fullMSSQLGenius.xml";
>          IDataSet fullDataSet = connection.createDataSet();
>             FlatXmlDataSet.write(fullDataSet, new
> FileOutputStream(fullDataSetName));
>          log.info("-- EndFull Data Set --");
>     } catch (Exception e) {
>         e.printStackTrace();
>     }
>
> [                          main] AbstractTableMetaData          WARN
> Potential problem found: The configured data type factory 'class
> org.dbunit.dataset.datatype.DefaultDataTypeFactory' might cause problems
> with the current database 'Microsoft SQL Server' (e.g. some datatypes may
> not be supported properly). In rare cases you might see this message because
> the list of supported database products is incomplete (list=[derby]). If so
> please request a java-class update via the forums.If you are using your own
> IDataTypeFactory extending DefaultDataTypeFactory, ensure that you override
> getValidDbProducts() to specify the supported database products.
> org.dbunit.dataset.DataSetException:
> com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the
> keyword 'End'.
>     at
> org.dbunit.database.DatabaseDataSet.getTable(DatabaseDataSet.java:323)
>     at
> org.dbunit.database.DatabaseTableIterator.getTable(DatabaseTableIterator.java:89)
>     at
> org.dbunit.dataset.stream.DataSetProducerAdapter.produce(DataSetProducerAdapter.java:83)
>     at org.dbunit.dataset.xml.FlatXmlWriter.write(FlatXmlWriter.java:124)
>     at org.dbunit.dataset.xml.FlatXmlDataSet.write(FlatXmlDataSet.java:378)
>     at
> com.glynlyon.GeniusDBFullBackup.testMSSQLGeniusFullDataSetExport(GeniusDBFullBackup.java:84)
>     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:597)
>     at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>     at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>     at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>     at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>     at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>     at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>     at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>     at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>     at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>     at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>     at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>     at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>     at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>     at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>     at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
>     at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax
> near the keyword 'End'.
>     at
> com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown
> Source)
>     at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown
> Source)
>     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown
> Source)
>     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(Unknown
> Source)
>     at
> org.dbunit.database.AbstractResultSetTable.<init>(AbstractResultSetTable.java:110)
>     at
> org.dbunit.database.ForwardOnlyResultSetTable.<init>(ForwardOnlyResultSetTable.java:59)
>     at
> org.dbunit.database.CachedResultSetTableFactory.createTable(CachedResultSetTableFactory.java:60)
>     at
> org.dbunit.database.DatabaseDataSet.getTable(DatabaseDataSet.java:319)
>     ... 31 more
>
>
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can gain
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> dbunit-user mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/dbunit-user
>
>

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
dbunit-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/dbunit-user
Reply | Threaded
Open this post in threaded view
|

Re: Export fullDataSet to XML from MS SQL Server 2005

gunipati81
 
I have added the following properties to the database connection.
 
             idbconn = new DatabaseConnection(JdbcConneciton, SchemaName);
            DatabaseConfig Config = idbconn.getConfig();
            Config.setProperty(DatabaseConfig.PROPERTY_DATATYPE_FACTORY, new MsSqlDataTypeFactory());
            Config.setProperty(DatabaseConfig.PROPERTY_RESULTSET_TABLE_FACTORY, new ForwardOnlyResultSetTableFactory());
            Config.setProperty("http://www.dbunit.org/features/qualifiedTableNames", true);
            Config.setProperty("http://www.dbunit.org/features/caseSensitiveTableNames", true);
 
I think you can try this one.


Cheers,
Mahesh



On 24 April 2011 19:30, Jeff Jensen <[hidden email]> wrote:
Just guessing; perhaps setting the DataType factory [0] will resolve
the problem?

[0] http://www.dbunit.org/properties.html


On Sat, Apr 23, 2011 at 8:25 PM, William Anderson
<[hidden email]> wrote:
> New to dbUnit -- Having problems trying to export fullDataSet to XML from
> Microsoft SQL Server 2005
> Any help would be appreciated --Thanks
>
> Microsoft SQL Server Management Studio                      9.00.4035.00
> Microsoft Analysis Services Client Tools
> 2005.090.4035.00
> Microsoft Data Access Components (MDAC)                  6.1.7600.16385
> (win7_rtm.090713-1255)
> Microsoft MSXML                                                         3.0
> 6.0
> Microsoft Internet Explorer
> 8.0.7600.16385
> Microsoft .NET Framework
> 2.0.50727.4952
> Operating System
> 6.1.7600
>
> Code snippet --
>
> IDatabaseConnection connection = null;
>         try {
>             // database connectionG
>             log.info("-- Start Connection --");
>             Class driverClass =
> Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
>             Connection jdbcConnection = DriverManager.getConnection(url +
> dbName, userName, password);
>             connection = new DatabaseConnection(jdbcConnection);
>             log.info("-- End Connection --");
>         } catch (Exception e) {
>             e.printStackTrace();
>         }
>
>
>      try {
>          // full database export
>          log.info("-- Start Full Data Set --");
>          String fullDataSetName = "fullMSSQLGenius.xml";
>          IDataSet fullDataSet = connection.createDataSet();
>             FlatXmlDataSet.write(fullDataSet, new
> FileOutputStream(fullDataSetName));
>          log.info("-- EndFull Data Set --");
>     } catch (Exception e) {
>         e.printStackTrace();
>     }
>
> [                          main] AbstractTableMetaData          WARN
> Potential problem found: The configured data type factory 'class
> org.dbunit.dataset.datatype.DefaultDataTypeFactory' might cause problems
> with the current database 'Microsoft SQL Server' (e.g. some datatypes may
> not be supported properly). In rare cases you might see this message because
> the list of supported database products is incomplete (list=[derby]). If so
> please request a java-class update via the forums.If you are using your own
> IDataTypeFactory extending DefaultDataTypeFactory, ensure that you override
> getValidDbProducts() to specify the supported database products.
> org.dbunit.dataset.DataSetException:
> com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the
> keyword 'End'.
>     at
> org.dbunit.database.DatabaseDataSet.getTable(DatabaseDataSet.java:323)
>     at
> org.dbunit.database.DatabaseTableIterator.getTable(DatabaseTableIterator.java:89)
>     at
> org.dbunit.dataset.stream.DataSetProducerAdapter.produce(DataSetProducerAdapter.java:83)
>     at org.dbunit.dataset.xml.FlatXmlWriter.write(FlatXmlWriter.java:124)
>     at org.dbunit.dataset.xml.FlatXmlDataSet.write(FlatXmlDataSet.java:378)
>     at
> com.glynlyon.GeniusDBFullBackup.testMSSQLGeniusFullDataSetExport(GeniusDBFullBackup.java:84)
>     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:597)
>     at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>     at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>     at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>     at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>     at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>     at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>     at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>     at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>     at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>     at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>     at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>     at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>     at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>     at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>     at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
>     at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
>     at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax
> near the keyword 'End'.
>     at
> com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown
> Source)
>     at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown
> Source)
>     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown
> Source)
>     at
> com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown
> Source)
>     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(Unknown
> Source)
>     at
> org.dbunit.database.AbstractResultSetTable.<init>(AbstractResultSetTable.java:110)
>     at
> org.dbunit.database.ForwardOnlyResultSetTable.<init>(ForwardOnlyResultSetTable.java:59)
>     at
> org.dbunit.database.CachedResultSetTableFactory.createTable(CachedResultSetTableFactory.java:60)
>     at
> org.dbunit.database.DatabaseDataSet.getTable(DatabaseDataSet.java:319)
>     ... 31 more
>
>
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can gain
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> dbunit-user mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/dbunit-user
>
>

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
dbunit-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/dbunit-user


------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been
demonstrated beyond question. Learn why your peers are replacing JEE
containers with lightweight application servers - and what you can gain
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
dbunit-user mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/dbunit-user