@Romain
Hi,
remember this one?
I've been trying the last couple of days to debug this but I have'nt managed
to reproduce the issue.
I was wondering if you have any recommendation on how do debug the
NameNode.bind to see why it complains about the name?
br
hw
--
View this message in context:
On May 13, 2014, at 4:40 PM, Anthony Fryer wrote:
> I'm interested in the "EARs and complex packaging sucks" particularly in
> relation to JCA resource adapters,which can only be packaged in an EAR
> according to the standards today, even though TomEE supports deploying it in
> a WAR file. Any c
I have tried today with a simple WAR with HelloWorld servlet and still the
same problem, I can only deploy one application, when I tried to deploy the
second one the same exception of previous post is thrown. Moreover if I use
the remote Apache TomEE connector then although both applications are
de
@Andy: it doesn't work neither. Users relying on snapshot needs a new
feature and it is important to stick on new snapshots to limit risk of
potential regressions we sometimes had cause we fixed only a part of
the real issue and by side effect the app was no more working. So I
think either you use
Hi
does it happen if you don't do it for the else case (new Fact())? But
I guess it is linked to a relationship maybe
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-05-
Markus,
You also have to understand that 'depending' on a snapshot is generally not
a good idea. That doesn't mean snapshot builds are not a good idea, rather
wait for a green build on the buildbot here:
http://ci.apache.org/builders/tomee-trunk-ubuntu, then deploy your own
version of it somewher
That's correct. This will be the patched version 'required' for running under
Java 1.6, as OpenJPA currently has their snapshot and planned release for
Java 1.7+.
When we release TomEE 1.7.0 then this will be documented 'loudly' to ensure
everyone using OpenJPA updates their pom's accordingly.
As
Hi,
I use openjpa with DTO and when I try to manage @Version I get an
exception: Detected attempt to modify field
"com.kildeen.ref.domain.BaseEntity.version" with value strategy "restrict".
What I do is, I use find if the DTO has id. I then copy back the version
field but it seems It does not wo
I think I found something:
openejb-core-4.6.1-20140513.040854-160.pom:
—
org.apache.openjpa
openjpa
—
But in openejb-4.6.1-20140514.040710-171.pom we find:
—
org.apache.openejb.patch
openjpa
${openj
The build is running already ;-)
http://ci.apache.org/builders/tomee-trunk-deploy/builds/23
JLouis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Wed, May 14, 2014 at 8:03 AM, Markus F. Frisch wrote:
> I think I found something:
>
> openejb-core-4.6.1-201
Hi,
It works with the "cxf.authMethod" property.
Thanks,
Xavier
> From: kal...@hotmail.com
> To: users@tomee.apache.org
> Subject: RE: ApplicationComposer and secured WebService
> Date: Wed, 14 May 2014 10:29:37 +0200
>
> [fixed formatting]
>
> Hi,
>
> I
I tried cleaning my local cache and made sure that our company apache archive
doesn’t hold copies of the openejp-SNAPSHOT.
When I build I get the warning:
[WARNING] The POM for
org.apache.openejb:openejb-core:jar:4.6.1-20140513.040854-160 is invalid,
transitive dependencies (if any) will not b
Thx again,
It think i resolved my issue.
My Bean implementation was defined like this:
@stateless
@localbean
public class whatever implements whateveremote
Having
@statless
public class whatever implements whateveremote,whateverlocal
seems to be working.
Now I can use remote interface on all thr
We are using the OpenEJB snapshot as an embedded container for our integration
testing.
Currently we get the message
"[WARNING] The POM for
org.apache.openejb:openejb-core:jar:4.6.1-20140513.040854-160 is invalid,
transitive dependencies (if any) will not be available, enable debug logging
fo
Seems ok on repository.apache.org so maybe try to cleanup
4.6.1-SNAPSHOTs from your local repo
If you have big issues we can force a new deployment
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://git
Le 13/05/2014 19:00, Romain Manni-Bucau a écrit :
> Hi,
>
> can you give us some details (maybe irc freenode #openejb would be
> easier)? How business jar is added?
As discused yesterday night on IRC, there is now a classloader change caused by
xbean-finder-shaded.
When using "java -jar myapp.jar
[fixed formatting]
Hi,
I will try with with "cxf-rs.auth".
In the meantime, I found out @Module's could also return EjbModule which lets
me configure an OpenejbJar like this:
@Module
public EjbModule ejbModule() {
EjbJar ejbJar = new EjbJar();
EnterpriseBean bean = ejbJar.addEnterpriseBean
17 matches
Mail list logo
