The collapsed EAR (not fully compatible with what it really is nowadays)
was an OpenEJB feature.
With Java EE 6, we pushed that feature to the spec so that now it's fully
standard.
Jean-Louis
2013/1/6 Anthony Fryer
> If the collapsed ear concept is a "tomee' specific idea and not part of the
>
...but was changed by the spec
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 Jean-Louis MONTEIRO :
> The collapsed EAR (not fully compatible with what it really is
Which spec defines the collapsed ear packaging? I'm looking
javaee-platform-6_0-fr-spec.pdf but can't see mention of 'collapsed ear'
anywhere.
Anyhow, is only ejb lite supported in a collapsed ear? I found a
conversation thread where David wanted to be able to deploy rars in wars.
Would be real
I see "The mailing list us...@javaee-spec.java.net does not have any
messages in its archive." following your link, not sure why
tw i don't see anything blocking technically to support it. If it
doesn't break tck we should be able to do it.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rm
I initially specified the wrong link. When i edited it, it didn't resend the
email. The correct link is
http://java.net/projects/javaee-spec/lists/users/archive/2012-09/message/9
--
View this message in context:
http://openejb.979440.n4.nabble.com/How-do-i-deploy-a-ManagedConnectionFactory-i
Hi it is possible to use the tomee snapshot in tomee maven plugin??
org.apache.openejb.maven
tomee-maven-plugin
1.0.1
1.5.2-SNAPSHOT
.
.
.
.
.
.
Hi,
if you ask i guess you have an issue?
typically you can use tomee maven plugin in version 1.5.2-SNAPSHOT (we
aligned it with tomee version yesterday) but 1.0.1 should work
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rm
Im testing tomee plugin, because i want to use it for deploy my ear and
before that use the tomee plugin that detects changes in code (like
JRebel). But im learning how to use it.
I ask for version because you fix some CODI issue's in 1.5.2-SNAPSHOT.
2013/1/7 Romain Manni-Bucau
> 1.5.2-SNAPS
Just try to use 1.5.2-SNAPSHOT version of plugin, it should be far
enough IMO and shouldn't bother you since you already rely on the
snapshot, no?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github
Yes i rely on. Im testing now.
2013/1/7 Romain Manni-Bucau
> Just try to use 1.5.2-SNAPSHOT version of plugin, it should be far
> enough IMO and shouldn't bother you since you already rely on the
> snapshot, no?
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress
didn't try with eclipse but worked for hazelcast resource adapter with
tomee mvn plugin: https://issues.apache.org/jira/browse/TOMEE-710
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmann
I have a problem, i dont know what im doing wrong.
If i try to use tomee:start apparently it try to run more than 1 time the
tomee server and i get a PORT IN USE, im trying to use with an ear file.
Here is my plugin dependency:
org.apache.openejb.maven
start on a multimodule project runs start on all submodules, isnt it your issue?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 José Luis Cetina :
> I have a problem
Yes, as i can see it starts for each submodule as you said, but how can i
prevent the port in use?
2013/1/7 Romain Manni-Bucau
> start on a multimodule project runs start on all submodules, isnt it your
> issue?
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress
not sure i get it
you want to start it by module? if yes just provide a different config for ports
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 José Luis Cetina :
I just want to deploy my ear file as normal (deploy in apps).
2013/1/7 Romain Manni-Bucau
> not sure i get it
>
> you want to start it by module? if yes just provide a different config for
> ports
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedI
so add inherited to false in the parent and run with -N
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 José Luis Cetina :
> I just want to deploy my ear file as norm
I use parent tag for my ejb module and my web module, what do you mean with
inherited to false?? and run with -N??
2013/1/7 Romain Manni-Bucau
> N
Do you mean the tag?
2013/1/7 José Luis Cetina
>
> I use parent tag for my ejb module and my web module, what do you mean
> with inherited to false?? and run with -N??
>
>
>
> 2013/1/7 Romain Manni-Bucau
>
>> N
>
>
>
>
--
---
yes
not perfect but works
or define it only in your child and run it from here
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 José Luis Cetina :
> Do you mean the
Whe i add inherited like this:
org.apache.openejb.maven
tomee-maven-plugin
1.0.1
false
1.5.2-SNAPSHOT
8080
8005
false
Do you run it from the pom where it is defined?
Well the easier is to define it in the pom defining the ear and not in
others then cd myear && mvn package tomee:run
Le 7 janv. 2013 18:33, "José Luis Cetina" a écrit :
> Whe i add inherited like this:
>
>
>
> org.apac
Yes, i ran it where is defined.
If i comment inherited tag i have the same port occupied issue
If i use tomee:run i dont have this error but the ear isnt deployed.
2013/1/7 José Luis Cetina
> Whe i add inherited like this:
>
>
>
> org.apache.openejb.maven
>
Weird, never saw this behavior
Did you align plugin version?
Maybe share your project if with snapshot versions it doesnt work
Le 7 janv. 2013 19:11, "José Luis Cetina" a écrit :
> Yes, i ran it where is defined.
>
> If i comment inherited tag i have the same port occupied issue
>
> If i use to
org.apache.openejb.maven
tomee-maven-plugin
1.0.1
false
1.5.2-SNAPSHOT
8080
8005
false
5005
mmm i dont know what could be wrong
2013/1/7 José Luis Cetina
>
>
>
> org.apache.openejb.maven
> tomee-maven-plugin
> 1.0.1
> false
>
> 1.5.2-SNAPSHOT
>
Can you give a try to my example: https://github.com/maxtorzito/tomee-tests
2013/1/7 José Luis Cetina
> mmm i dont know what could be wrong
>
>
> 2013/1/7 José Luis Cetina
>
>>
>>
>>
>> org.apache.openejb.maven
>> tomee-maven-plugin
>>
Another question, why if i use tomee:run the ear is copied to apps folder
but is not "unwrapped" ???
2013/1/7 José Luis Cetina
> Can you give a try to my example:
> https://github.com/maxtorzito/tomee-tests
>
>
>
>
> 2013/1/7 José Luis Cetina
>
>> mmm i dont know what could be wrong
>>
>>
>> 2
Hi Romain,
Thanks for having a look at the code. However, I'm sorry but I don't
understand your email. I looked into the source of wicket and only found
3 @Inject annotations (all in wicket-cdi).
How and where does wicket-cdi "define beans with constructor params"? I
probably don't know enou
wicket-cdi does not define beans, they define injection targets which
OpenWebBeans (IMHO incorrectly) treats as managed beans, hence the
confusing messages.
I've started a new thread [1] on the OWB user list for this issue.
I've tested Bertrand's sample without problems on GlassFish/Weld, and
Harald,
Thanks for jumping in! I think you are much better informed regarding
this issue than I am.
Regarding the UnmanagedObject class, you are right. I meant "unmanaged"
in the sense that wicket does not inject it automatically, but via a
method call in the constructor. Since this test pro
I dont know what i was doing wrong.
But what i did is create a new maven project. In my pom.xml i add the maven
plugin with inherited set to false and i create src/main/conf with my own
server.xml, tomcat-users.xml and tomee.xml now the ear is deployed and
unwrapped when i run tomee:run
2013/1/7
here the diff: https://gist.github.com/e3255c2d34677c7ea3b6
works fine
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 José Luis Cetina :
> I dont know what i was do
BTW guys,
it works then no? just warnings at startup no?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/1/7 Bertrand Guay-Paquet :
> Harald,
>
> Thanks for jumping in!
Yes, it works, but with warnings. And these warnings seem to highlight a
design issue in OWB...
Am 07.01.2013 22:18, schrieb Romain Manni-Bucau:
BTW guys,
it works then no? just warnings at startup no?
As far as I can see it works, yes.
However, I do have a suspicious eye towards warnings which I don't
understand. Also, I thought maybe this was somehow related to the crash
I get if I uncomment the "seam-conversation-owb" dependency in the pom.
Bertrand
On 07/01/2013 4:18 PM, Romain Manni-B
not sure it is related, think it is log just for info because it tends
to be an issue (that's not a common usage) - that's how i understand
it looking the code
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: h
37 matches
Mail list logo
