Using DUST to junit test rql

Looking for assistance with DUST. Following the GSATest pattern here: http://atgdust.sourceforge.net/repository-test.html. Trying to test rql for product items with custom catalog to extend item description. Ideally, hsql schema would be automatically created and the junit setup would populate product items, then test would run component with rql.
I've only gotten as far as trying to pull in the extension custom catalog which does not parse because the "primary" table types are declared in the DCS customCatalog.xml:
ATG10.0.2/DCS/src/config/atg/commerce/catalog/custom/customCatalog.xml
/atg/commerce/catalog/ProductCatalog Error parsing template: atg.repository.RepositoryException: Your item-descriptor catalog must have a table tag with type="primary".
/atg/commerce/catalog/ProductCatalog Your item-descriptor category must have a table tag with type="primary".
Thanks.

Did you add the DCS.CustomCatalogs into the configpath?
Peace
Shaik

Similar Messages

Using TimesTen for JUnit tests

I want to switch from using HSQL (in memory) to TimesTen in my Unit tests. Is there a simple setup for TimesTen when used for this purpose?
For example, for HSQL, all I have to do is include the hsql.jar as a dependency in my project, then include the following line in my JUnit test:
DataSource dataSource = new DriverManagerDataSource("org.hsqldb.jdbcDriver",
"jdbc:hsqldb:target/test-classes/com/project/path/test/schema", user, pw);
schema is a reference to the schema.script that includes the DDL for all the tables that I need to create in memory.
Can anyone help me out? Thanks.

From what little I know about it TimesTen is not an in-memory database, it is a caching architecture. Therefore I would expect the set-up to be different - the TimesTen stuff should be set up once ever[], like the schema of a regular database, rather than everytime you run your unit tests.
I think you need to sit down with the TimesTen documentation and figure out how you are going to use the product. If you are just looking for a quick DB to use in unit tests I think you may well want to keep using HSQL.
Cheers, APC

Exceptions trying to run Junit test thro Jdev. Test uses Application module

Hi,
my junit test works through the OraTst frame work. But I want to debug the code and If I try to run the same test through Jdev I am running into a following exception. Can somebody tell me how to fix this issue.
I am a consumer of the Application module, I have not created it. I am using it by referencing it through the jar file provided by the owner.
oracle.jbo.DMLException: JBO-27200: JNDI failure. Unable to lookup Data Source at context jdbc/EMReposDS
at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1414)
at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:309)
at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:203)
at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolConnect(ApplicationPoolMessageHandler.java:553)
at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolMessage(ApplicationPoolMessageHandler.java:409)
at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:8534)
at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:4392)
at oracle.jbo.common.ampool.ApplicationPoolImpl.prepareApplicationModule(ApplicationPoolImpl.java:2388)
at oracle.jbo.common.ampool.ApplicationPoolImpl.prepareResource(ApplicationPoolImpl.java:3621)
at oracle.jbo.pool.ResourcePool.useResource(ResourcePool.java:344)
at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:2200)
at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:3088)
at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:460)
at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:431)
at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:426)
at oracle.jbo.client.Configuration.getApplicationModule(Configuration.java:1494)
at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1399)
at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1370)
-Sidd

Sidd,
No idea what OraTst is, but based upon the name of your data source, I'd guess you are an Oracle employee using an internal framework. I understand that there are some internal Oracle forums that you can use.
John

How to test servlet using Junit test????

Hello everybody
Does anybody know how to test an servlet class using Junit without using Cactus test . Is it possible to test a servlet using Junit without cactus test.Plz tell me the process how to test a servlet using Junit test .
Regards
srikant

1) Do yoiu mean how to "run" your servlet code with sample parameter? This call manual testing with a sample run of you code. You need a web server(eg Tomcat), create a webapp with your servlet then deploy it there in order to run it.
2) httpunit and junit are framework to write test case code that can be automated and repeatable. Plz read their doc.
3) Your sample code me a very wrong way to retrieve and convert servlet parameters.
Get a java toturial and servlet tutorial book and read it over the weekend. You need to get at least the basic.

Creating junit test cases using the reflection API

In order to use the reflection API to get information about a *.java file's class name and methods, I need to compile the *.java file first, and then get info through the *.class file. Am I right?
Eclipse, the Java IDE, can create junit test cases for java files the user selects right after the *.java files have been created, and even before the *.java files have been compiled by the user. I guess Eclipse internally compiles the java files before creating JUnit test cases for them. Does anyone know about it? Thanks.

Let me explain my problem in more details.
Given any java source tree, my program is supposed to create junit test cases for each class using java reflection. My approach is to scan through the source tree to keep the list of classes available, then compile all the java files in the given source tree, then do Class.forName() to load them to get their methods... Obviously I don't know what classes I will have at compilation time. I create a temp_classes directory as the output directory for the given source tree java files, and I add temp_classes to my classpath when I strart up my own program. However, that won't work..
D:\eclipse\workspace\cmpe271_hw4\classes>java -classpath ..\classes;..\temp_classes Test
javac -classpath .\temp_classes; -d .\temp_classes @temp_classes\javalist.txt
java.lang.ClassNotFoundException: Factory
java.lang.ClassNotFoundException: InvalidDateFormatException
java.lang.ClassNotFoundException: MyUtility
java.lang.ClassNotFoundException: Storage

Writing JUnit test app to test a method which uses AppResources

Recently I was given a requirement to write a JUnit class( with main) to test a method in a Processor class which is running in weblogic. But this method in processor class makes use of AppResources like this: AppResources appResources = new AppResources("ApplicationResources"); String ruleFileName = appResources.getResourceString("rule.file.irlfile"); But when I try to run my JUnit test (stand alone app with main class) I am getting "java.util.MissingResourceException: Can't find bundle for base name ApplicationResources" exception. The appResources is null... Any ideas how to work around this problem?

It doesn't sound like the Process class was designed for testability outside of its J2EE server container, probably. So writing a unit test for it, under its current design, may be an exercise in futility. You might want to look into "Cactus" tests (search for JUnit Cactus on the web), to test it in its container. Or, redesign the class for testability, separating its business logic better (that's a lot of work to do though) so that it can be instantiated and exercised independently of its environment.

Use JUnit test EJB bean class

I'm using Junit test EJB 3.0 session bean class by initialize :
SessionBeanClass sbc = new SessionBeanClass()
so the object I got is just a normal object, it's not remote or local interface.
however, when I start JUnit within Jdeveloper, looks like the embed OC4J start.
this behivor is strange to me, I thought I 'm not calling EJB in this case,why the OC4J start?
this is different than running JUnit outside of JDeveloper?

Yes, this is the way JDev works -- JDeveloper notices that this class happens to be a Session bean, and when you 'run' it, it assumes you want to 'run' it in the embedded OC4J server -- though clearly it is not what you want in this case.
One way you can override this behavior is by creating a wrapper (POJO) class to be your JUnit test class, and have that class instantiate your Session bean.

Unable to run ADFBC JUNIT Test Classes with JDEV11G 11.1.1.6

Dear All,
I upgraded my project to the latest release JDEV 11G 11.1.1.6
Previously we are on JDEV 11G 11.1.1.5
I have a JUNIT class that I am running which test my ADFBC components.
public class MyTestClass {
@Test
public void testVOAccess()
    //assertions
}Unfortunately, I am hitting an error like this from the messages.
Mar 9, 2012 1:28:07 PM oracle.adf.share.ADFContext getCurrent
WARNING: Automatically initializing a DefaultContext for getCurrent.
Caller should ensure that a DefaultContext is proper for this use.
Memory leaks and/or unexpected behaviour may occur if the automatic initialization is performed improperly.
This message may be avoided by performing initADFContext before using getCurrent().
For more information please enable logging for oracle.adf.share.ADFContext at FINEST level.
Mar 9, 2012 1:28:08 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: org.xml.sax.SAXParseException: Invalid encoding name "Cp1252".
Mar 9, 2012 1:28:10 PM oracle.mds
NOTIFICATION: PManager instance is created without multitenancy support as JVM flag "oracle.multitenant.enabled" is not set to enable multitenancy support.
Mar 9, 2012 1:28:12 PM oracle.security.jps.internal.config.xml.XmlConfigurationFactory initDefaultConfiguration
SEVERE: org.xml.sax.SAXParseException: Invalid encoding name "Cp1252".
Mar 9, 2012 1:28:12 PM oracle.adf.share.jndi.ReferenceStoreHelper getReferencesMapEx
WARNING: Incomplete connection reference object for connection:MYDATASOURCEAt the JUNIT Test Runner, I see this.
java.lang.ExceptionInInitializerError: null
     java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     org.junit.runners.BlockJUnit4ClassRunner.createTest(BlockJUnit4ClassRunner.java:171)
     org.junit.runners.BlockJUnit4ClassRunner$1.runReflectiveCall(BlockJUnit4ClassRunner.java:216)
Caused by: oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
     oracle.jbo.server.ConnectionPool.createConnection(ConnectionPool.java:207)
     oracle.jbo.server.ConnectionPool.instantiateResource(ConnectionPool.java:166)To validate the issue, I tried to run my same project using the older release which is JDEV 11G 11.1.1.5
and I see that I am not hitting any error. All my test classes runs fine.
Has anybody replicated this?
Thanks

Didier Laurent wrote:
I logged the following bug for this issue:
bug 14030895 - REGR: JDEVELOPER 11.1.1.6.0 JUNIT JBO-26061 ERROR WHILE OPENING JDBC CONNECTION
Regards,
Didier.So its really a bug..
I abandon this already since I cannot find any solution to look up for this.
On the other hand, I am maintaining two jdeveloper version just to get around this problem.
When testing ADFBC, I used the 11.1.1.5 while for non-junit test I used the 11.1.1.6
Hopefully this gets fixed on the next release as I am having a hard time swithcing between two JDev version.
Thanks
Edited by: Neliel on May 3, 2012 11:42 PM

Writing to file in JUnit test case? Not working?

I have a singleton class called InstantLogger that internally uses a PrintWriter to write to file. It is very basic, has startLogger(String filename), log(String msg), and stopLogger(). startLogger just creates file, log write to file, and stopLogger closes file.
When I use this class outside of the JUnit test suite it works fine.
As soon as I use it in a JUnit test it does not write to file. It creates the file (this happens in the TestSuite), but will not write anything to it (when log is called from TestCase). I put a System.out in the log function and I see that, but still nothing writing to file. And I will say it again, it does work in non TestCase scenarios so I know it works.
Is there something that could be preventing me from writing to file in JUnit TestCase? Could this be a Singleton Issue?
Thanks,

avalanche333 wrote:
I have a singleton class called InstantLogger Ouch.
that internally uses a PrintWriter to write to file. It is very basic, has startLogger(String filename), log(String msg), and stopLogger(). startLogger just creates file, log write to file, and stopLogger closes file.
When I use this class outside of the JUnit test suite it works fine.Oh, brother.
>
As soon as I use it in a JUnit test it does not write to file. It creates the file (this happens in the TestSuite), but will not write anything to it (when log is called from TestCase). I put a System.out in the log function and I see that, but still nothing writing to file. And I will say it again, it does work in non TestCase scenarios so I know it works.
Is there something that could be preventing me from writing to file in JUnit TestCase? Could this be a Singleton Issue?Um, no.
Your code is wrong. You're assuming something that isn't correct. You're also making the assumption that just because it "works" in another context that it's right in all contexts. The two aren't the same, be it configuration or something else.
Singleton? That GoF pattern has been voted off the island. Didn't you hear?
http://code.google.com/p/google-singleton-detector/
%

Re: junit test for entity beans ... ejb 3.0

I'm confused. I'm trying to test my entity bean.
I have:
- an entity bean
- a stateless session bean for accessing the entity bean (facade)
- an interface for accessing the the stateless bean
And I'm trying to write a JUnit test class to test this bean. However, I am uncertain as to how to test this (I'm new to EJB 3.0, JBoss and Eclipse).
What would the JUnit test look like? I'm confused as to whether or not I should be injecting the interface/bean/what???
I've tried several variations. I either get "NameNotFound" - not bound exceptions or Null pointer exceptions.
What would the @EJB syntax look like or how would I do it through the context?
For Example:
@EJB private TestFacade myTest; //interface to stateless bean ?
OR
InitialContext ctx = new InitialContext();
TestResultFacadeBean myTest = (TestResultFacadeBean) ctx.lookup("localTest");
I'm confused at to which method I should be using and what object I should be accessing. If I could get either one to work, I'd be happy. :)
How do I ensure my bean is deployed to the container? What do I need to do?
If anyone has a simple example or explanation as to which method I should use and how to use it, I'd be very grateful.
Thanks very much,
LisaD

OK, you need to have several layers of testing.
Layer 0. Test the entity beans are deployable (more on this later). Basically, you need to know that all your annotations work. Things to watch out for are multiple @Id fields in one class or @EmbeddedID or @IdClass in conjuction with @ManyToOne, @ManyToMany, @OneToMany, @OneToOne and fun with @JoinTable, @JoinColumn and @JoinColumns. Once you know how these are supposed to work with the spec, it's not too bad to write it correctly each time. But there are some gotchas that will break things later on.
Layer 1. Do the functions in the classes that don't depend on annotations work as expected. Typically, this is just going to be the getters and setters in your entity classes. Of course JUnit best practice says we don't bother testing functions that look like:
public T getX() {
return this.x;
or
public void setX(T x) {
this.x = x;
as there is nothing that can go wrong with them. So in that case, your level 1 tests will just be initial values specified from constructors and verifying that the non-get/set pairs work, and that the getters you have tagged @Transient work (because you've likely put some logic in them)
Layer 2. Test the session bean methods that don't require injection to work.
Layer 3. Test the session bean methods that require injection (Mock Objects). Simulate the injection for yourself, injecting Mock Objects for the entity manager. Then you can confirm that the correct methods are being called in the correct sequences, etc.
[Note this may require some skill in designing the mock. I'm working on developing my own entitymanager mock, and if it looks usefull I'll release it to the world.
Layer 4. Test the session bean methods that require injection (Real entity manager) (See Layer 0)
For this you will need an out of container persistence implementation. Currently Hibernate and Glassfish provide beta versions. You will need a different persistence.xml file that lists all the entities. You will have to use reflection to inject the entity manager(s) that you create from an entity manager factory unless you provide a constructor that takes an EntityManager as a parameter. You may need to use reflection to call any @PostConstruct method if you made it private.
Layer 5. Navigate the relationships in the objects returned from Layer 4 using a database that has been loaded with test data.
I am currently using Layers 0, 1, 2 & 4 to test my session beans and entity beans.

Exception while running a test file as JUNIT test case

Hi,
I am trying to build a code using Eclipse to generate an "ear" file that can be used for deployment. The ear file is generated successfully but the build is not successful as the following exception is thrown while debugging a junit test case:
javax.naming.CommunicationException: tdk.dk:389 [Root exception is java.net.SocketTimeoutException: connect timed out]
     at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
     at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
     at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
     at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2616)
     at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
     at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
     at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
     at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
     at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
     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 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 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
     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)
Kindly suggest a solution.
P.S. : All test cases are running fine except for one test case, whose error details are given.

No it is not. The Oracle JDeveloper and ADF forum is for development questions around development with Oracle JDeveloper and ADF.
If you use Eclipse through OEPE, you could post the question here
Enterprise Pack for Eclipse
If you don't use OEPE but Eclipse, then this forum may be a great source of help: http://stackoverflow.com/
Frank

Problem using Toplink with JUnit

Hi,
I have a problem using Toplink with JUnit. Method under test is very simple: it use a static EntityManager object to open a transaction and persists data to db. When I invoke the method from a test method, it gives me the exception:
java.lang.AssertionError
     at oracle.toplink.essentials.ejb.cmp3.persistence.PersistenceUnitProcessor.computePURootURL(PersistenceUnitProcessor.java:248)
     at oracle.toplink.essentials.ejb.cmp3.persistence.PersistenceUnitProcessor.findPersistenceArchives(PersistenceUnitProcessor.java:232)
     at oracle.toplink.essentials.ejb.cmp3.persistence.PersistenceUnitProcessor.findPersistenceArchives(PersistenceUnitProcessor.java:216)
     at oracle.toplink.essentials.internal.ejb.cmp3.JavaSECMPInitializer.initialize(JavaSECMPInitializer.java:239)
     at oracle.toplink.essentials.internal.ejb.cmp3.JavaSECMPInitializer.initializeFromMain(JavaSECMPInitializer.java:278)
     at oracle.toplink.essentials.internal.ejb.cmp3.JavaSECMPInitializer.getJavaSECMPInitializer(JavaSECMPInitializer.java:81)
     at oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider.createEntityManagerFactory(EntityManagerFactoryProvider.java:119)
     at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83)
     at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60)
     at it.valerio.electromanager.model.EntityFacade.<clinit>(EntityFacade.java:12)
     at it.valerio.electromanager.business.ClienteBiz.insertIntoDatabase(ClienteBiz.java:36)
     at it.valerio.electromanager.test.model.ClienteTest.insertDBTest(ClienteTest.java:30)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
     at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
     at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
     at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
     at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
     at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
     at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
     at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
     at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
     at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
     at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
     at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Where is the problem???
Regards,
Valerio

EntityFacade class is very simple and it uses a static EntityManager object. Here the code:
public class EntityFacade {
     private static EntityManager em = Persistence.createEntityManagerFactory("ElectroManager").createEntityManager();
     private static Logger logger=Logger.getLogger(EntityFacade.class);
     public static void insertCliente(Cliente c)
          logger.debug("Inserisco cliente nel db: " + c);
          em.getTransaction().begin();
          c.setId(getNextIdForTable("Cliente"));
          em.persist(c);
          em.getTransaction().commit();
If I call the method from inside a main it works well, so I think the problem is not the classpath neither the URL in the persistence.xml. However the URL is:
<property name="toplink.jdbc.url" value="jdbc:derby:c:/programmi/ElectroManager/db/electroManager"/>
I use the latest build version of TopLink.
Thanks.

Persist does not throw any exception in a JUnit test

I am implementing a JUnit test using Toplink as JPA provider. I must be missing something because I try to persist two times the same entity and no exception is thrown. Neither PersistenceException nor any other type of exception. The code cannot be easier:
@Test
public void testAddExistingTeam() throws Exception {
Team team = new Team("team2");
try{
EntityManagerFactory emf =
Persistence.createEntityManagerFactory("fofo");
EntityManager em = emf.createEntityManager();
em.getTransaction().begin();
em.persist(team);
em.persist(team);
em.getTransaction().commit();
em.close();
catch(Exception e){
e.printStackTrace();
Notice the two em.persist(team).
This code does not seem to either enter the catch block or produce any sort of exception. On the other hand, I have checked that after the first
em.persist(team); the team is really managed.
The relevant parts of the Team class definition follow:
@Entity
@Table (name ="TEAM")
public class Team implements Serializable {
@Id
@Column (name="NAME")
private String name;
@ManyToOne
@JoinColumn (name="CLUB_NAME", referencedColumnName="NAME")
private Club club;
private Category category;
private String email;
@ManyToMany(mappedBy="teams")
private List<Competition> competitions;
public Team (String name){
this.name = name;
this.club = null;
this.competitions = new ArrayList<Competition>();
....getters/setters....and more constructors.
I am really puzzled by this issue. Somebody could help??? I would be really grateful!!!
Josepma

This is expected behavior as persist is a no-op if called on a managed entity (other than to cascade over relationships marked with cascade.Persist), and the first persist call makes the passed in team entity managed.
Try calling em.flush(); and em.clear(); between the persist calls to get an exception.
The first flush will ensure the team is inserted in the database, while clear will detach it so that the second persist call will try to insert the team. JPA providers are not required to throw the entityExistsException on persist - it can be delayed until the transaction is flushed or committed, so you are likely to get a PersistenceException from the commit instead of EntityExistsException from persist.
Best Regards,
Chris

Jdeveloper 11g using Junit38ClassRunner from junit-4.5.jar

For some reason Jdeveloper is using the Junit38ClassRunner when I run Junit tests - so annotations like @Ignore and @Test are being ignored. Does anyone have any idea on how to change it to use the Junit4ClassRunner (which you'd kind of expect to be the default)?
Any assistance much appreciated.

The version of Jdeveloper is: J2EE Edition Version 11.1.2.0.0.
Yeah - I've checked which jar the class runner is being loaded from - it's from junit-4.5.jar. If I ctrl- for the class name then when it displays the Junit38ClassRunner class, Jdeveloper displays where it's getting the source from and it's from junit-4.5-src.jar. I've also searched for the class in all the jars available to Jdeveloper and this jar is the only one in which it occurs. Same jar has Junit4ClassRunner which is obviously the one it should be using. I can't find any obvious (or less than obvious) way to configure how the junit classrunner is invoked.

Best practice for @EJB injection in junit test (out-of-container) ?

Hi all,
I'd like to run a JUnit test for a Stateless bean A which has another bean B injected via the @EJB annotation. Both beans are pure EJB 3 POJOs.
The JUnit test should run out-of-container and is not meant to be an EJB client, either.
What is the easiest/suggested way of getting this injection happening without explicitely having to instantiate the bean B in my test setup ?

you can deal with EntityBeans without having the Container managed senario , you can obtain instance of EntityManager using the "EntityManagerFactory" and providing the "persistence.xml" file and provide the "provider" (toplink,hibernate ,...), then you can use entities as plain un managed classes

Using DUST to junit test rql

Similar Messages

Maybe you are looking for