1and1 / ioc-unit Goto Github PK

Scenario:

@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
class NonEjbSuper {
  public void doSomeDbChanges(){
    //...
  }
}


@Stateless
class EjbChild extends Super {

}

The TransactionalInterceptor only checks if the declaring class of the method is an EJB. When I instantiate EjbChild class, the method doSomeDbChanges doesn't have transaction although it should.
The same scenario works in arquillian

To support this, Datasources until now can only be produced by PersistenceFactory-objects.

ioc-unit-jta-narayana allows it to use tras and persistence without ejb. Try tohandle dbunit without ejb as well.

Incorrect Maven coordinates for dependency in README

Observed/Actual Result:

<groupId>net.oneandone</groupId>
<artifactId>ioc-unit</artifactId>

Expected Result:

<groupId>net.oneandone.ioc-unit</groupId>
<artifactId>ioc-unit</artifactId>

The lookup of the class path in the method com.oneandone.ejbcdiunit.cfganalyzer.TestConfigAnalyzer#isCdiClass will always fall if the url contains a space:
URL location = c.getProtectionDomain().getCodeSource().getLocation()
--> will return an url with the space escaped (%20), "file:/my%20folder"
cdiClasspathEntries
--> contains the url without escaping: "file:/my folder"

Hello,

I'm wondering if this project accepts contributions from people not affiliated with 1&1?

If so, is there any roadmap?
I've checked TODO.md in the root and all existing issues but I can't say I see directly actionable items there.

Any suggestions for first task and/or issue to investigate?

to search for transactionattributes

Using Restassured a Restservice can be called quite easily. If this restservice itself consumes rest-Services, these must be simulated as Java-Beans.