Oracle XA datasource configuration

Hi, According to http://tomee.apache.org/common-datasource-configurations.html adding an Oracle XA datasource should be as simple as appending the following configuration to your tomee.xml: JdbcDriveroracle.jdbc.xa.client.OracleXADataSource JdbcUrl jdbc:oracle

Re: JSON Webservice... interpreting null as null

Hi That was jettison behavior. This is fixed with cxf 3. Ps: here is the jira enhancing it https://jira.codehaus.org/plugins/servlet/mobile#issue/JETTISON-126 Le 9 sept. 2014 02:43, "Jonathan Fisher" a écrit : > Consider this request: > > { > "call" : { > "type" : "Call", > "subject" : null >

JSON Webservice... interpreting null as null

Consider this request: { "call" : { "type" : "Call", "subject" : null } } This object: @XmlRootElement(name = "call") @XmlAccessorType(XmlAccessType.NONE) public class ApiCallActivity { @NotNull @XmlElement(name = "type") public String type; @Size(min = 1, max = 255) @XmlElement(name = "subjec

Re: DuplicateDeploymentIdException in parallel deployment

2. If restart the server only the most recent version of the application >starts. The older ones fail with a DuplicateDeploymentIdException: > > GRAVE: Unable to deploy collapsed ear in war > StandardEngine[Catalina].StandardHost[localho

DuplicateDeploymentIdException in parallel deployment

tarts. The older ones fail with a DuplicateDeploymentIdException: GRAVE: Unable to deploy collapsed ear in war StandardEngine[Catalina].StandardHost[localhost].StandardContext[/colaborador##20140908-1455] org.apache.openejb.DuplicateDeploymentIdException: Application cannot be deployed as it con

Re: Question on transactions

he he -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Sep 8, 2014 at 3:35 PM, Lars-Fredrik Smedberg wrote: > Sorry... saw the following in the JavaDoc for @TransactionAttribute > > "If the TransactionAttribute annotation is not specified, and the bean u

Re: Question on transactions

Right, the idea is to get 80% of the use cases supported by default and running without anything. So yes, if nothing at all, then REQUIRED is assumed. Not all wrong indeed ;-) -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Sep 8, 2014 at 3:32 PM, Lars-F

Re: Question on transactions

Sorry... saw the following in the JavaDoc for @TransactionAttribute "If the TransactionAttribute annotation is not specified, and the bean uses container managed transaction demarcation, the semantics of the REQUIRED transaction attribute are assumed." That answers my follow up question... On

Re: Question on transactions

Hi Jean-Louis So an EJB (e.g. a stateless EJB) NOT annotated with @TransactionAttribute at all will still have the container start a transaction when its methods are called? My understanding was that REQUIRED was the default if annotated, I might have got it all wrong though Regards LF On Mon,

Re: Question on transactions

Sorry, NOT_SUPPORTED does not throw an exception, but suspend the current if any. All detailed here http://docs.oracle.com/javaee/6/api/javax/ejb/TransactionAttributeType.html JLouis -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Sep 8, 2014 at 3:25 PM,

Re: Question on transactions

Hi, As per the spec, the default is REQUIRED. So if nothing specified on the class and on the method, the container is going to start a new transaction before executing the method. If you do not want this behavior, use SUPPORTS (if one already started use it, otherwise, do nothing) or NOT_SUPPORT

Question on transactions

Hi! Just a small question on EJBs and transactions. I assume that there are no implicit transactions started when calling a business method on an EJB that does not have the @TransactionAttribute annotation? (Assume of course that there are no other ongoing transaction) Regards LF -- Med vänlig