Here is the exception:
org.apache.webbeans.exception.WebBeansConfigurationException: If bean has a
public field, bean scope must be defined as @Scope. Bean is :
com.maxtorzito.test.MyBeanThree
at
Hmm, if your loging.config contains PropertiesLoginModule it should be
fine, if you copied/pasted the snippet we have on our website it should
be PropertiesLogin:
Realm className=org.apache.catalina.realm.JAASRealm
appName=PropertiesLogin
Well that was interesting! I ended up copying the LazyStopWebappLoader source
to my own implementation because it's missing from the current
tomee-catalina-1.6.0-SNAPSHOT.
I had to tweak it slightly to prevent an NPE:
@Override
protected synchronized void startInternal() throws
Hi,
weird for NPE, probably cause you use a custom one so the info is not set
since not in the default API (so i'd say that's normal)
about the presence of the file the loader is LazyStopLoader and the
classloader: LazyStopWebappClassLoader. Just a name issue i guess
*Romain Manni-Bucau*
Finally got this working now, thanks.
It was a strange reason why it wasn't working, but it was basically down to
some bad character (encoding or mistake) I had in the Service block. I typed
it out manually and it worked. I compared the one I typed out to the one I was
using before and
Hello,
I'm developing a multi-module JEE 6 web-application. I'm using the JEE
Webprofil so the application is packaged in a single war file. One of my
goal is to develop this application for Jboss, Glassfish and TomEE as
supported application servers.
It looks like this:
I understand, that I
Hi,
which version of tomee? can you reproduce it in a small maven project you
can share?
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
there are auto scanning too in tomee which is fine but that's not the issue
if i understood
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
The Internet is way too small
However I stoped using JSF and so PrimeFaces. I'm happy with Vaadin for now.
Is auto-scanning supposed to work? Like I said I have one persistence.xml in
my war file and the jar modules that include the entities are in
WEB-INF/lib.
The line
is in my
It should, that's why i'm curious to see if that's a real bug or not. That
said a workaround can be to add:
property name=openejb.jpa.auto-scan value=true /
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog:
Hi!
I've got a problem with javax.el.CompositeELResolver which is used by TomEE's
javaee-api-6.0-5.jar.
Version information and svn-repository here:
http://mvnrepository.com/artifact/org.apache.geronimo.specs/geronimo-el_2.2_spec/1.0.2
Source of class CompositeELResolver here:
Hi,
i guess you add something which is not built in since we never had this one
and we use several resolvers. But globally i think you are right. That said
that's more a geronimo issue ATM since they hold the apache spec jar and we
just shade them to get a javaee-api jar (easier to use).
*Romain
On Wed, Jun 12, 2013 at 2:47 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
Here is the exception:
org.apache.webbeans.exception.WebBeansConfigurationException: If bean has
a public field, bean scope must be defined as @Scope. Bean is :
com.maxtorzito.test.MyBeanThree
at
Of course i did, it is the in the first post.
2013/6/12 Howard W. Smith, Jr. smithh032...@gmail.com
doh, really? lol :)
Jose, did you 'not' copy/paste that user-friendly exception message when
you provided the stack trace?
On Wed, Jun 12, 2013 at 10:13 AM, Romain Manni-Bucau
I guess. jeje
2013/6/12 José Luis Cetina maxtorz...@gmail.com
Of course i did, it is the in the first post.
2013/6/12 Howard W. Smith, Jr. smithh032...@gmail.com
doh, really? lol :)
Jose, did you 'not' copy/paste that user-friendly exception message when
you provided the stack trace?
Hmmm, OP says, ... (keep reading below)
On Mon, Jun 10, 2013 at 2:02 PM, José Luis Cetina maxtorz...@gmail.com
wrote:
Just FYI, when you declare ( i did that by mistake) public attributes with
their getter and setters in your ManagedBean you get this exception (by the
way the error is not
I confirmed it again:
persistence.xml without jar-file entries:
Works on TomEE, does not work on Glassfish and JBoss
persistence.xml with
Works on TomEE, does not work on Glassfish and Jboss
persistence.xml with
Works on Glassfish and Jboss, does not work on TomEE
This is a little bit
Ok I think I made a mistake.
The Application is indeed working on TomEE without naming the modules in the
persistence.xml
But sadly the application does not work on JBoss or Glassfish.
It seems they do not scan the WEB-INF/lib/ path by default.
Here the example. A DataSource with the name
should be better with https://issues.apache.org/jira/browse/TOMEE-973
that said you can put the persistence.xml in WEB-INF and it should be fine
for every app servers
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog:
But isn't it first the container that needs to find persistence.xml, since
it needs to instantiate the provider? Don't you really have to pass in all
of this config to the provider? For some reason I recall the provider
being blind to the location of persistence.xml, other than by configuration
no, in JavaEE it has the PersistenceUnitInfo which contains this info
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github:
Cool thanks. I'll look forward to the 1.6 release...
3 TomEE and I appreciate all the work you guys do!
--
View this message in context:
http://openejb.979440.n4.nabble.com/JAX-RS-severely-broken-when-virtual-hosts-are-used-tp4663598p4663724.html
Sent from the OpenEJB User mailing list
with:
mvn test -Ptomee-build-managed -Dtomee.version=1.6.0-SNAPSHOT
-Dowb.version=1.2.1-SNAPSHOT
i get the injection, then the constraint validator is not enriched but not
sure we read validation.xml in WEB-INF/classes/META-INF, probably just in
WEB-INF as mentionned in the spec (i know others
Right, so the container needs to read persistence.xml, turn it into
PersistenceUnitInfo and pass to the provider.
On Wed, Jun 12, 2013 at 11:43 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
no, in JavaEE it has the PersistenceUnitInfo which contains this info
*Romain Manni-Bucau*
IIRC (didnt read it for months) but it sayd META-INF for jar and WEB-INF
for wars
btw i'll add the meta-inf support since that's quite common:
https://issues.apache.org/jira/browse/TOMEE-975
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog:
yep
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/6/12 John D. Ament
Why are you going to add it when it already works?
On Wed, Jun 12, 2013 at 12:05 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
IIRC (didnt read it for months) but it sayd META-INF for jar and WEB-INF
for wars
btw i'll add the meta-inf support since that's quite common:
Was not the case on trunk
Le 12 juin 2013 18:12, John D. Ament john.d.am...@gmail.com a écrit :
Not sure I follow. It was working fine for me yesterday in TomEE 1.5.2. I
saw bval load up my CVF and process injections properly (which is entirely
outside of my issue I'm reporting).
On Wed,
It now works. There is something strange with the
http://tomee.apache.org/tomee-jaas.html page. It is completely different
from the content that I get when I want to contribute to the page. On
that page the parameters userClassNames and roleClassNames are even
different from the ones in your
so the workaround is to put it in both places ;)
joke apart i wonder why jboss and glassfish doesn't follow the spec (or did
i misunderstood it? would be better probably, if not we could add a flag to
do like them)
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
Hmm weird, sure i saw the opposite...if not we have to open an issue since
it would be the only descriptor being here (sure for ejb-jar, web,
validator..)
Le 12 juin 2013 18:45, John D. Ament john.d.am...@gmail.com a écrit :
Spec says it goes in WEB-INF/classes/META-INF. In fact the spec says
spec for validator says it goes in WEB-INF/classes/META-INF as well.
So, web.xml, ejb-jar.xml, beans.xml go in WEB-INF
validator.xml, persistence.xml, beans.xml go in WEB-INF/classes/META-INF
Sounds like what we really have is an issue for the EE spec to sort out the
proper place to put
Thats not that trivial since javaee spec is kind of ambiguous saying
descriptors goes in web inf but not which one
Le 12 juin 2013 22:32, John D. Ament john.d.am...@gmail.com a écrit :
spec for validator says it goes in WEB-INF/classes/META-INF as well.
So, web.xml, ejb-jar.xml, beans.xml go
Hmm, a bit but wouldnt shock me to get it there too
So as you said a spec issue ;)
Le 12 juin 2013 22:54, John D. Ament john.d.am...@gmail.com a écrit :
I think the EE spec only refers to the deployment descriptors - beans.xml,
web.xml and ejb-jar.xml (application.xml doesn't relate to WAR
Sorry, when I refer to META-INF, I'm referring to WEB-INF/classes/META-INF.
/META-INF is really just for JAR wrapper stuff (e.g. maven files) in WARs.
On Wed, Jun 12, 2013 at 5:47 PM, Anthony Fryer apfr...@hotmail.com wrote:
I always thought, for war files you put jee config files in WEB-INF
35 matches
Mail list logo
