Re: Question about Java EE certification TomEE and Plume

F can have access to TCK suite. > > Best > Gurkan > > Sent from my iPhone > >> On 14 Oca 2016, at 20:45, Mark Struberg wrote: >> >> With other words, most of the other vendor packages are strictly seen also >> not ‚certified‘ but only ‚compliant‘. >

Re: Question about Java EE certification TomEE and Plume

ired to become a licensee of Oracle) , you can not use any >>> test and say that blabla server is compatible. Currently ASF is not >>> licensee of Oracle so no project in ASF can have access to TCK suite. >>> >>> Best >>> Gurkan >>> >>

Re: CDI behavior change: who is right ?

n/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2016-01-19 18:35 GMT+01:00 COURTAULT Francois < > francois.courta...@gemalto.com>: > >> Hello Romain, >> >> Thanks a lot for this useful exchange :-) >> >> BTW, who is Ma

Re: Change the location of tomee.xml

If you need global JTA resources then there they should get managed on the container level. This is a clean separation of concerns. The app says „I need resource X“ and the whole configuration and setup is done on container level depending on the system. Different stages or even customers obvio

Re: Re. TomEE // SCHWERWIEGEND: FATAL ERROR: Unknown error in Assembler. Please send the following stack trace and this message to users@tomee.apache.org :

> Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver That looks to me as if the postgresql jdbc driver jar is not in the /lib directory? LieGrue, strub > Am 14.02.2016 um 12:20 schrieb Michael Schubert : > >

Re: default json provider

Hi Matthew! Could you probably also bring this up on the Johnzon list? Maybe we simply miss an important use case over there. txs and LieGrue, strub > On Thursday, 8 September 2016, 11:26, chongma > wrote: > > i tried the following without any luck: > openejb.cxf.jax-rs.providers = > org.a

Re: tomee 1.7.1 plus . with deltaspike 1.7.1

+1 It is clearly a DeltaSpike question DeltaSpike people are also very responsive. There is actually quite an overlap in communities. But you will get better feedback for such DS related questions over there. LieGrue, strub > Am 09.09.2016 um 11:21 schrieb Romain Manni-Bucau : > > DeltaSpike

Re: How to disable OpenWebBeans?

> You are right, I just didn't understand what this container is for. > I thought it starts some Web > server listening on a tcp port ... Apache OpenWebBeans is the CDI container used in TomEE. It basically provides all the handling around @Inject, @RequestScoped, @SessionScoped, interceptors,

Re: OpenEJB and EL

Oh boy, sorry for you. You did hit a blank spot in the CDI spec. Problem is that the EE umbrella spec, the EL spec and the CDI spec contradict each other. The Weld guys solved this by introducing a Javax class. But that takes away the whole javax.* tree for the EL. That's just not good as it co

Re: OpenEJB and EL

t;a producer allows to get a shorter/more elegant naming like #{conv.id} if you >@Produces @Named("conv") ;) > > > >Romain Manni-Bucau >@rmannibucau | Blog | Old Wordpress Blog | Github | LinkedIn | Tomitriber | >JavaEE Factory > >2016-09-28 23:01 GMT+02:00

Re: OpenEJB and EL

name'.property}) > > Xavier > > > From: Romain Manni-Bucau > Sent: Wednesday, September 28, 2016 11:10 PM > To: users@tomee.apache.org; Mark Struberg > Subject: Re: OpenEJB and EL > > a producer allows to get a shorter/more elegant naming like #{con

Re: OpenEJB and EL

Name:conv, API >> Types:[java.lang.Object,javax.enterprise.context.Conversation], >> Qualifiers:[javax.enterprise.inject.Default,javax. >> enterprise.inject.Any,javax.inject.Named] from file:/D:/development/ >> workspaces/openejb-el/target/test-classes/eg/ConversationWra

Re: OpenEJB and EL

t; contrary, >> if >> > the requirement comes from the java EE spec, then I suppose it is >> > implemented in TomEE and that would explain why my tests fail. >> > >> > >> The name is built it in openwebbeans: >> https://github.com/apache/open

Re: OpenEJB and EL

The problems are in the details. an EL #{javax.enterprise.context.conversation.id} will iterate over the EL loader chain a whooping 5 times! First it will resolve „javax“. Then on that object it will resolve „enterprise“, then … And on the last (id) you will finally hit the OWB WebBeansELResolv

Re: OpenEJB and EL

mp; "javax".equals(property)) { >>context.setPropertyResolved(base, property); >>return new ExpandingImplicitObject("javax"); >>} >>if (base instanceof ExpandingImplicitObject && property instanceof >> String)

Re: OpenEJB and EL

Yes a posibility to escape the dots in EL would be great. Too bad that EL doesn’t fully follow ECMAScript conventions but is only ’similar’ to it. LieGrue, strub > Am 29.09.2016 um 20:33 schrieb Xavier Dury : > > I concur: (a) would be best... maybe in EL 3.1 or 4.0? (I don't know if a > revi

Re: EJBContainerRunner and @RequestScoped

You might give DeltaSpike CdiTestRunner a try. It cleans the contexts between test methods. Just use cdictrl-openejb as backend. LieGrue, Strub > Am 30.09.2016 um 11:45 schrieb Xavier Dury : > > Hi, > > Is it normal that all test methods from a test class running with > EJBContainerRunner sha

Re: TomEE performance

To give you a bit of perspective. I did have a public internet application written in JSF which _easily_ took 5 Mio page hits / day from about 70.000 unique users. Or another application which makes up to 20k requests per minute for about 7k users. Quick enough? ;) LieGrue, strub > Am 23.01

Re: Jackson vs Johnzon JAX-RS provider

> It does (actually an early release included it: johnzon-jsonb module), > another release is coming very soon with a more up to date spec. To be more precise: the work on JSONP-1.1 and JSONB-1.0 was finished a few days ago! We already checked the API signatures and they are 1:1 with the RIs. O

Re: Jackson vs Johnzon JAX-RS provider

the latest stage is Public Review > Ballot. There is not yet a Proposed Final Draft :-( > > If not, when do you think it will be ? > > Best Regards. > > -Original Message- > From: Mark Struberg [mailto:strub...@yahoo.de.INVALID] > Sent: samedi 1 avril 2017 18:56 &

Re: Tomcat security issues and tomee 1.7.x

Build is green now! We might check a few other dependencies as well, but most deps should have been updated. Who want's to run the 1.7.5 release train? LieGrue, strub > Am 13.04.2017 um 16:46 schrieb Romain Manni-Bucau : > > Hi > > Think Mark was waiting for a green build we got this morning

Re: Tomcat security issues and tomee 1.7.x

+1 John, txs for jumping in! I'll be around if you need an additional pair of eyes. LieGrue, strub > Am 13.04.2017 um 16:45 schrieb Jonathan Gallimore : > > Thanks for your mail! I think we're probably due a 1.7.x release by now. If > there's no objections, I'm happy to volunteer to be the rele

Re: [+SPAM+]: Re: Jackson vs Johnzon JAX-RS provider

Francois < > francois.courta...@gemalto.com>: > >> Hello Mark, >> >> Any update ? >> >> Best Regards. >> >> -Original Message- >> From: Mark Struberg [mailto:strub...@yahoo.de.INVALID] >> Sent: mercredi 5 avril 2017 21:50 &g

Re: Upgrading OpenEJB Standalone to 4.6.0.2

Just out of curiosity: Why not using 4.7.4. Is 1:1 compatible with 4.5 and 4.6 LieGrue, strub > Am 12.04.2017 um 09:48 schrieb Romain Manni-Bucau : > > Hi Geoff, > > are you sure you didn't recompile your application with java 8? 4.6 doesn't > support it if I recall correctly. The difference i

Re: CDI @Observes ApplicationScoped.class

+1 NO @Destroyed(SomeContext.class) can be observed in a bean with scope @SomeContext! I even suggest we throw a ContextNotActive in the future. You can observe the @Destroyed(ApplicationScoped.class) in an Extension. But most of the time a @PreDestroy in your @ApplicationScoped bean would work

Re: TomEE -Java EE 8 compatible or certified ?

Hi Francois! The community is already working on EE8. It's in the tomee8 branch. LieGrue, strub > Am 25.09.2017 um 17:15 schrieb COURTAULT Francois > : > > Hello everyone, > > As Java EE 8 is out, could you tell us when a TomEE version will be at least > compatible or certified released ?

Re: TomEE -Java EE 8 compatible or certified ?

Hmm, EE8 requires Java8. Just from the API alone. And anything compiled with Java8 will also run on Java9, right? So I'd say the minimum requirement in TomEE8 is Java8. Btw, we still can use Java9 for the TomEE8 development! The new Java9 Maven build chain supports to generate real Java8 code by

Re: TomEE supported on Java 9: when ?

I can roll an OWB-1.7.x release with Java9 support. LieGrue, strub > Am 06.12.2017 um 13:03 schrieb Romain Manni-Bucau : > > 2017-12-06 12:34 GMT+01:00 COURTAULT Francois > : >> Hello, >> >> I have seen that Tomcat 8.5.24 is supported on Java 9. >> >> I don't see in the TomEE 7.0.5 backlog a

Re: TomEE supported on Java 9: when ?

Btw, if we get a few more helping hands up then I'd be happy if someone could help me with the TomEE8 branch ;) LieGrue, strub > Am 06.12.2017 um 13:08 schrieb Mark Struberg : > > I can roll an OWB-1.7.x release with Java9 support. > > LieGrue, > strub > &g

Re: Removing version string from banner

or just add an tag in your web.xml. Because usually one wants to brand the error page anyway. LieGrue, strub > Am 14.02.2018 um 18:51 schrieb Jean-Louis Monteiro : > > Oups message left too quickly. > > The default error valve from Tomcat generates this HTML with information > you may not n

Re: TomEE Stable and OpenJDK

I think what the download page fails to communicate is which EE level it addresses. We should probably split this into different areas on the download page. To clarify this TomEE-1.7.x adresses the JavaEE 6 specifications, with minimum requirement Java7 (up to Java8) TomEE-7.0.x adresses Jav

Re: JAX-RS integration with managed beans

Hi! +1 for @javax.annotation.ManagedBean is a mess in the spec. I still remember how this got added to EE6. This annotation literally got added to EE6 in the last week before the spec went final. It was not discussed in the CDI, EJB and JSF Expert Groups and just had a single mention in an umbr

Re: TomEE Stable and OpenJDK

k Jonson : > > Mark Struberg wrote: > >> I think what the download page fails to communicate is which EE level >> it addresses. >> >> TomEE-1.7.x adresses the JavaEE 6 specifications, with minimum requirement >> Java7 (up to Java8) >> TomEE-7.0.x adr

Re: Migration step of jtaManaged flag in context resources

Hi Fabian! To give a bit more context: Having actual db connections configured inside a WAR or EAR is usually something you'd rather like to avoid. Having passwords checked in into your source repo, needing to recompile if you want to tweak the connection or credentials, etc All that is simply

Re: Migration step of jtaManaged flag in context resources

, strub > Am 11.05.2018 um 10:37 schrieb Romain Manni-Bucau : > > Le ven. 11 mai 2018 09:27, Mark Struberg a > écrit : > >> Hi Fabian! >> >> >> To give a bit more context: >> >> Having actual db connections configured inside a WAR or EAR

Re: [Newsletter] Migration step of jtaManaged flag in context resources

your replies! >> >> Is the resources.xml approach a portable solution? E.g. if we want to >> support Wildfly in the future, which approach is the most portable? >> Tomee.conf doesn’t sound too portable :) >> >> Thanks and best >> Fabian >> >>

Re: Deploying WAR in TomEE

There is a difference between ClassNotFoundException and NoClassDefFoundError ClassNotFoundException: the class you were looking for could not be found. NoClassDefFoundError: some other Class your own class needs could not be loaded. Essentially com.app.auth.AuthenticationService is there, but i

Re: Embedded TomEE 7.0.4 and Arquillian and TLS

will apply. LieGrue,strub On Monday, 18 June 2018, 16:35:44 CEST, Romain Manni-Bucau wrote: Looks good to me (if anyone wants to apply it otherwise I'll do it end of the week) Romain Manni-Bucau @rmannibucau |  Blog

Re: TomEE 7.0.4 and contextPath

that's news to me. Which ticket was that?Could not find it on bugzilla. On Monday, 18 June 2018, 17:15:01 CEST, Romain Manni-Bucau wrote: If you put the war in webapps (or auto deploy) you must rename the war file now (tomcat change). Romain Manni-Bucau @rmannibucau

Re: Johnzon is going to infinite loop on JPA entities with OneToMany relationship

Sadly there is no common handling for this in the current spec. I've already created a ticket [1], but this will only be available as of JakartaEE9. You should be able to swap out Johnzon-1.0.x with 1.1.8. Then use the following JsonbConfig and set "johnzon.deduplicateObjects" to true. Happy t

Re: Johnzon is going to infinite loop on JPA entities with OneToMany relationship

jsonb/JohnzonBuilder.java#L212 > Am 19.07.2018 um 21:57 schrieb Mark Struberg : > > Sadly there is no common handling for this in the current spec. > I've already created a ticket [1], but this will only be available as of > JakartaEE9. > > You should be able to sw

Re: Deltaspike 1.0.0 issue?

Hi! This Exception should only get thrown if you have a  @Specializes public class  A extends X where X is not in the classpath or not an enabled bean. Do you have a sample of this around somewhere? Oh and we finally need to change the error message to proper english! LieGrue, strub On Satu

Re: Deltaspike 1.0.0 issue?

Can you please check if you do have deltaspike-core-impl.jar in your classpath? LieGrue, strub On Saturday, 21 June 2014, 20:50, hwaastad wrote: > > >Hi Mark,ve >No, I do not have any of such. > >I have omnifaces in ear/lib.(a library is using this). > >I'll see if I can reproduce the is

Re: Deltaspike 1.0.0 issue?

+1 Put all except maybe deltaspike-jsf into the ear lib. LieGrue, strub > On Sunday, 22 June 2014, 17:52, Romain Manni-Bucau > wrote: > > Weird, i would have expected everything excepted jsf modules in common libs > only. > > > Le dimanche 22 juin 2014, hwaastad a écrit : >> Yeah, >> I

Re: Alternatives and beans.xml

Hi! I'd use neither approach ;) Take a look at Apache DeltaSpike @Exclude [1].   You can exclude beans (and thus disable alternatives and specializes) either via ProjectStage or via configuration. You can even do something like @Specializes @Exclude(onExpression="dbvendor!=oracle") public clas

Re: Alternatives and beans.xml

> The moment you find a way to do something,  > there is always a better one  Well, this is true for others as well ;) There is just no silver bullet and no 1-fits it all hammer for all problems. The thing is that we (as community) discussing about such things can spread the word and share ideas

Re: TomEE EE6/7 Certification

I'm not quite sure if this got resolved already on a legal level, but here is my pov up to what I know. There are 2 different profiles defined in JSR-316 (JavaEE6 umbrella spec): 1.) the full-profile 2.) the web-profile We pass the web-profile, but we do NOT implement the full full-profile but

Re: JDBC Transactions vs EJBs and @TransactionAttribute(...) and more...

Hi Lars-Fredrik! With pure JPA you could kind of 'emulate' JTA. At least in a poor mans way without 100% guarantee. iterate over all open connections and em.flush() them. This is actually the part where either the operation blows up or all is fine. Then after that in a second pass you loop over

CDI container performance

Hi! Yesterday I wrote a small micro benchmark to test the performance of some CDI containers. The outcome was pretty stunning - but best if you run it yourself: https://github.com/struberg/cdi-performance $> git clone https://github.com/struberg/cdi-performance.git $> cd cdi-performance Just

Re: CDI container performance

1 October 2014, 12:21, Daniel Kasmeroglu > wrote: > > Am 21.10.2014 um 11:37 schrieb Mark Struberg: > >> Hi! >> >> Yesterday I wrote a small micro benchmark to test the performance of some > CDI containers. The outcome was pretty stunning - but best if you run

Re: CDI container performance

Actually all CDI containers use proxies for NormalScoped beans. This is mandated by the spec. We also only cache 1 instance for all ApplicationScoped proxies of the same type. So I profiled (using YourKit profiler) that OWB allocates WAY less temporary objects - what results in a fraction of the

Re: Freemarker and CDI

+1 to what Romain said: http://deltaspike.apache.org/documentation/core.html#_beanprovider It works in JavaEE and also in SE. LieGrue, strub > On Saturday, 15 November 2014, 19:52, Romain Manni-Bucau > wrote: > > Ok got it. > > I'm not aware of an existing impl but using deltaspike BeanP

Re: [CDI - OpenWebBeans] explicit no arg constructor

I'm not sure what Weld does, but the spec clearly mandates it "3.15. Unproxyable bean types The container uses proxies to provide certain functionality. Certain legal bean types cannot be proxied by the container: • classes which don’t have a non-private constructor with no parameters, .. Otherw

Re: measure session size?

did that via a SerlvetFilter and just serialized the session into a byte[] and output the size. As benefit you also see early on whether you have something which is not properly Serializable and would fail on a cluster. LieGrue, strub > On Monday, 2 February 2015, 20:01, Karl Kildén wrote:

Re: measure session size?

zable and tomcat > sessionholder does not. The actual session is not obtainable :( >> >> Skickat från min iPhone >> >>> 4 feb 2015 kl. 16:52 skrev Mark Struberg : >>> >>> did that via a SerlvetFilter and just serialized the session into a >

Re: measure session size?

(by reflection). Should be serializable >>> >> >>> >> >>> >> Romain Manni-Bucau >>> >> @rmannibucau >>> >> http://www.tomitribe.com >>> >> http://rmannibucau.wordpress.com >>> >> htt

Re: measure session size?

ction. LieGrue, strub > On Monday, 9 February 2015, 15:05, Karl Kildén wrote: > > XRebel is on the todo list but it's good to able to log it in production. > > Thanks alot Romain and Mark for the information! > > > On 9 February 2015 at 11:26, Mark Struberg wr

Re: ApplicationComposer and Deltaspike 1.0

Hi Astah! I’m pretty good at DeltaSpike so to say, but I somehow lost the context. You are talking about an error in tomee but your log clearly shows you are working with WebSphere? > com.ibm.ws.container.service.state.StateChangeException: Maybe you mixed up the paste? Do you mind to explain m

Re: Wrong encoding using JSF with tomee 2.0-SNAPSHOT

So what is the exact problem? Is it Tomcat or is it in OWB? Probably have a small example for me? txs and LieGrue, strub > Am 31.03.2015 um 12:41 schrieb Karl Kildén : > > I tried downgrading to the catalina.jar from 1.7.1 and it works with that > one... > > On 31 March 2015 at 08:52, Karl Ki

Re: Total noob question - system.properties

Hi Brandon! TomEE’s conf/system.properties are _not_ intended for end users. If you like to configure something in your own project then please take a look at the DeltaSpike configuration system [1]. The basic idea is to have different ‚ConfigSources‘ (some property files, environment, -D java

Re: Total noob question - system.properties

o be used by any > System.getProperty user > > It is the fastest way to get a conf without worrying about cdi. Depending > the app cdi can be an issue (binding primitives etc) > Le 5 avr. 2015 09:55, "Mark Struberg" a écrit : > >> Hi Brandon! >> >> To

Re: Does TomEE 1.7.1 support JSF 1.1?

I think it should also work in 1.7.1. This is actually not a bug but basically some modularity feature you get from OpenWebBeans. Basically CDI is JavaEE6. But in OpenWebBeans we still support a lot of older integration scenarios as well. And even pure Java SE. OWB is built around a ‚core‘ whic

Re: Does TomEE 1.7.1 support JSF 1.1?

OpenWebBeans is built in a very modular fashion. We add integration features by simply dropping the plugin into the classpath. The webbeans-jsf* module adds support for 2 features: 1.) CDI @ConversationScoped support for JSF 2.) CDI EL support for JSF. Out of the box we have plugins to support

Re: NPE when webBeansContext.getApplicationBoundaryService() in AbstractProxyFactory

well, that should not happen of course ;) I can give you a quick explanation what the ApplicationBoundaryService is for. We use it to get the ClassLoader to use for a class we need to proxy. Say if we create a CDI proxy (Contextual Reference) for a MyCustomCdiBean in your project then we usually

Re: OpenEjb, Injection of datasource using "jboss naming"

you mean 7.0.0-SNAPSHOT right? LieGrue, strub > Am 26.05.2015 um 18:14 schrieb Romain Manni-Bucau : > > Le 26 mai 2015 09:00, "padou" a écrit : >> >> Hello >> >> I saw that you already improved it >> Is there a way to test with a SNAPSHOT ? what version of openEJB should I >> use (I see it w

Re: tomee jee 7

The question is rather what the options are :) TomEE will sustain for quite some time. And TomEE rocks all the other servers from a performance aspect with a quite big gain. TomEE also doesn’t just ship ‚banana-ware‘ and then switch to commercial releases after the projects starts to become ma

Re: Stateless dead lock

Hmm, if there is a network issue then the connection should actually get closed, right? So the lock gets cleaned and you will see an Exception in your app. Sounds really like a weird issue and I did not yet see this on any system yet. The more important it is to get behind the real reason why it

Re: Stateless dead lock

No, proxies have a rather short and defensive socket retention time. Otherwise they would too quickly become stuck and run out ot sockets… LieGrue, strub > Am 11.06.2015 um 18:51 schrieb Romain Manni-Bucau : > > Le 11 juin 2015 09:49, "Mark Struberg" a écrit : >&g

Re: Stateless dead lock

> feature/bug? >> >> >> BR >> >> Matej >> >> >> >> >> >> >> 2015-06-11 19:00 GMT+02:00 LG Optimusv : >> >>> This might be useless, but if you have nothing else to try, you can try >>> using the ip add

Re: JPA trying to alter table to add the single table discriminator before openJPA build the schema on tomee startup (1.6.0.2)

Hmm, never had this problem. Important for me to figure what goes wrong in your case. As you already stated: the schema is aways the user which logs in. Is there probably some login trigger which does an alter session to switch the schema after logon to oracle? And do you have enough rights and

Re: TomEE 7 M1 feel

OWB-1.6.2 is ready and released. So one more showstopper out of the way. And +1 for pushing this^^ LieGrue, strub > Am 12.08.2015 um 09:41 schrieb Alex Soto : > > Hi guys, I know that the release process in Apache can be a bit slow > because of votes and so on, but is your feeling that by the

Re: CDI unit test

ViewScope is _not_ part of the CDI spec. Thus ContextsService wont help you here. This is only for OWB internal Contexts. You need to use the ‚owner‘ of the Context if you like control it’s lifecycle. This depends on whether you have @ManagedBean @ViewScoped (which would be a JSF managed ViewS

Re: CDI unit test

+1 for a sample please. Then it will be pretty easy to identify your problem. txs and LieGrue, strub > Am 07.12.2015 um 20:37 schrieb Romain Manni-Bucau : > > Myfaces API pick up the proxy map implementation in a hardcoded fashion. I > dont see if you have the right classpath how it can fail thi

Re: SessionScoped does not seem to work

Was about to write the same pointer (wrong import) ;) In Apache DeltaSpike we even have a small Extension which ‚corrects‘ those wrong scope annoations for you because it’s such a frequent user-error ;) LieGrue, strub > Am 20.12.2015 um 22:38 schrieb Marco DE BOOIJ : > > It is intended to use

Re: TomEE 7.0.0 Perf

If you report that you are satisfied with the performance then I can go on and trigger a BVal release. LieGrue, strub > Am 13.01.2016 um 11:40 schrieb Romain Manni-Bucau : > > with maven plugin using remove:bval, > org.apache.bval:bval-jsr:1.1.1-SNAPSHOT, > org.apache.bval:bval-core:1.1.1-SNAP

Re: Question about Java EE certification TomEE and Plume

With other words, most of the other vendor packages are strictly seen also not ‚certified‘ but only ‚compliant‘. Which makes them not bad - it’s just that the terms often get mixed up by marketing (knowingly or not? I don’t know) and confuse users. LieGrue, strub > Am 11.01.2016 um 23:04 schri

Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs

I think under Windows it's catalina.bat. And the logs usually go under ./logs/... What I do whenever tomcat or another java process dies is to send a SIGINT. Which ich kill -3 [processid] under linux, and there is a special command for it under windows I think. Might be the jstack command if

Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs

wow -XX:MaxPermSize=4096m that might be a bit huge ^^ Permanent Generation Space is used for loaded classes and stuff. Usually 256m is plenty! In our production with 16 fat webapps we have 384m or so... LieGrue, strub - Original Message - > From: "Howard W. Smith, Jr." > To: users@t

Re: TomEE undeploy app is not invoking @PreDestroy on CDI @ApplicationScoped bean

And please make sure that it's really a CDI @ApplicationScoped and not the one from JSF. LieGrue, strub > > From: Romain Manni-Bucau >To: users@tomee.apache.org >Sent: Sunday, March 10, 2013 1:08 PM >Subject: Re: TomEE undeploy app is not invoking @PreDest

Re: @RequestScoped CDI constructor

Hi Jason! The default ct is needed for all 'NormalScoped' beans because they will always get proxied. And this proxy will use the default ct. It's perfectly fine to have this default ct protected. Just not private plz ;) The CDI container will invoke the @Inject annotated ct for your bean but wi

Re: @RequestScoped CDI constructor

al-introduction-to-cdi-contexts-and-dependency-injection-for-java-ee-jsr-299-42877.html Might help a bit. LieGrue, strub - Original Message - > From: James Green > To: users ; Mark Struberg > Cc: > Sent: Friday, March 15, 2013 5:12 PM > Subject: Re: @RequestScoped CDI c

Re: Injection data not found in JNDI context

according to the spec any EJB is automatically @Local if it doesn't implement more than 1 Interface (apart from javax.ejb.* stuff). LieGrue, strub - Original Message - > From: Romain Manni-Bucau > To: users@tomee.apache.org > Cc: > Sent: Friday, March 22, 2013 2:42 PM > Subject: Re:

Re: CDI instead of JSF

Hi Marco! Please don't do beans.iterator().next() - you can do BeanManager#resolve() instead. Also Bean != Contextual Instance of T You would to create a CreationalContext and invoke BeanManager#getReference You might take a look at Apache DeltaSpike BeanProvider [1] which provides easy help

Re: TomEE 5

well, for tomcat6 you would need to swap out the el-api to el-2.2 for using JSF-2.x in a nice way. Of course it also works with the older EL stuff but then you miss parameters in ELs... And of course servlet-3.0 Otherwise it is pretty ok. LieGrue, strub - Original Message - > From:

Re: Question regarding CDI: Injection needed in at runtime created objects.

Hi! You should be able to simply use @Inject in your @WebService. If you need the parsed stuff elsewhere, then just create a producer method for it. LieGrue, strub - Original Message - > From: Caroline Van den Hauwe > To: users@tomee.apache.org > Cc: > Sent: Sunday, 21 April 2013,

Re: TOMEE-916 rework webapp bean manager since owb 1.2...

Hiho Howard! I'll answer a few questions which might already be answered by Romain (just glimpsed over the whole thread) a.) There should be no need to change anything for you in your own code. All the refactoring is just internally. b.) If you do performance testing, then please always sw

Re: TOMEE-916 rework webapp bean manager since owb 1.2...

Btw: more important than OWB. As this is a primefaces-push issue: when/did tomee change MyFaces to the most recent 2.1.11? That might have much more impact on your issue than OWB does. LieGrue, strub - Original Message - > From: Mark Struberg > To: "users@tomee.apache

Re: TOMEE-916 rework webapp bean manager since owb 1.2...

answers inline > > From: "Howard W. Smith, Jr." >To: users@tomee.apache.org; Mark Struberg >Sent: Wednesday, 1 May 2013, 18:16 >Subject: Re: TOMEE-916 rework webapp bean manager since owb 1.2... > > > >Hi Mark! >

Re: Discussing MyFaces, OpenWebBeans, and Atmosphere

> hmmm... i understand 'let it break on any exception', but exclude stuff > like java.io.* ? In IntelliJ Idea you can set an 'Exception breakpoint' and add conditions. E.g. not trigger if the Exception gets thrown in any java.io.* class. LieGrue, strub - Original Message - > From: "H

Re: Discussing MyFaces, OpenWebBeans, and Atmosphere

Probably in TomEE we do not yet remove all our scanning results and temporary boot stuff after booting up the container. LieGrue, strub - Original Message - > From: "Howard W. Smith, Jr." > To: users@tomee.apache.org > Cc: > Sent: Thursday, 2 May 2013, 7:09 > Subject: Re: Discussing

Re: [OWB] CDI - how to realize default producer?

CDI-1.0 _has_ a concept of vetoing. Simply annotate Foo with @Typed() LieGrue, strub - Original Message - > From: John D. Ament > To: users@tomee.apache.org > Cc: > Sent: Sunday, 19 May 2013, 4:37 > Subject: Re: [OWB] CDI - how to realize default producer? > >T he easiest way is t

Re: [OWB] CDI - how to realize default producer?

> To: users@tomee.apache.org; Mark Struberg > Cc: > Sent: Sunday, 19 May 2013, 14:14 > Subject: Re: [OWB] CDI - how to realize default producer? > > Well, I think @Typed is another work around.  It doesn't remove the object > from the archive simply says you can't refere

Re: Re[2]: [OWB] CDI - how to realize default producer?

ot easily see that this is only for disabling it and is never intended to get listed as in beans.xml @Typed still looks the cleanest to me. LieGrue, strub - Original Message - > From: "Howard W. Smith, Jr." > To: users@tomee.apache.org > Cc: Mark Struberg &g

Re: Invoke EJB on Glassfish

I've tried such things once and gave up. For accessing the Remote EJB you need some client.jar from that very server (glassfish-client.jar). And those often contain lots of classes which really create classpath clashes. They are really only meant for clients which do not have any EJB knowledge a

Re: Invoke EJB on Glassfish

JB  + can be used to exchange data btw different EE containers  - same firewall/proxy issues like EJB So choose your weapon wisely young padawan :) hope that sums it up LieGrue, strub - Original Message - > From: Jean-Louis MONTEIRO > To: users@tomee.apache.org; Mark Struberg >

Re: Remote exceptions logging

For @Remote the exceptions usually get wrapped into an EJBException, isn't? This is done to prevent ClassNotFoundException on the client side. Imagine some OpenJPA OptimisticLockingException gets thrown on the Server, but your client project (say a swing app) doesn't have any openjpa.jar package

Re: Javaagent throwing NoClassDefFoundError

will fix this now :=) LieGrue, strub - Original Message - > From: Romain Manni-Bucau > To: users@tomee.apache.org > Cc: > Sent: Thursday, 30 May 2013, 19:43 > Subject: Re: Javaagent throwing NoClassDefFoundError > > Hi > > Add asm 4 as a dependency. I added a patch on openjpa to ge

Re: Remote exceptions logging

There are imo two different things in the game here: 1.) This imo indicates some nasty ClassLoader or scanning issue 2.) Afaik it's not defined whether you should get this log on the server at all. Most servers I know don't log it. You might work around it by writing a CDI Extension which add

Re: EJB lite

Hi Michiel! Slightly OT: the EJB timers are _really_ useful, but I found @Asynchronous to be barely useful because: * no @RequestScoped, @SessionScoped, etc gets propagated * no Transaction gets propagated and most important: * there are no guarantees that the async thread succeeds What i

Re: JMS [was: EJB lite]

> Worse yet, I have a customer who won't allow me to chance packages from > testing to production, Completely agree with your customer. A binary MUST NOT change between testing stages and production! All this EE configuration is pretty much useless in my opinion. Mike told me he likes to star

  1   2   >