OK -- I will test (no time today, but I will : ) and report back. Thanks
again.
Best,
Stuart
On Tue, Apr 22, 2014 at 3:21 PM, Romain Manni-Bucau
wrote:
> resources.xml is design to work with all types but should work with
> ObjectFactory using factory-method="getObject" as additional
> attribute
surely linked to https://issues.apache.org/jira/browse/TOMEE-1183
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-22 18:36 GMT+02:00 José Luis Cetina :
> My tomee runs
resources.xml is design to work with all types but should work with
ObjectFactory using factory-method="getObject" as additional
attribute.
Another workaround could be to not set type to DataSource but a
subtype of DataSource if you know the impl type.
Romain Manni-Bucau
Twitter: @rmannibucau
Hi, many thanks for the suggestion. : ) So I've reviewed everything I can
find on Resource declarations in tomee.xml and resources.xml (and tried
various tests), and what's not entirely clear (to me) is: is creating a
DataSource using a custom javax.naming.spi.ObjectFactory supported...? I am
tryin
Hi
Did you try using resources.xml or tomee.xml? Basically context.xml
datasources are converted to tomee datasources to get pooling etc by
default. Using resources.xml you can define whatever you want so it
should match your need.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibuca
Greetings all, this may be a straightforward question, but I'm unable to
find a solution. Basically I need to define a DataSource with a custom
resource factory.
According to this thread:
http://openejb.979440.n4.nabble.com/Getting-Started-TomEE-Plus-and-Custom-Resources-td4662031.html
in Tomee:
My tomee runs already under C:\tomee, in the related topic, i uploaded a
maven project that you can check it, this is a TomEE problem.
2014-04-22 11:28 GMT-05:00 Romain Manni-Bucau :
> Well first check basic things like spaces etc, can be a hidden bug
> until now. Basically try to deploy in c:\t
Well first check basic things like spaces etc, can be a hidden bug
until now. Basically try to deploy in c:\tomee. If the issue is still
here we'll try to have a deeper look. But we have a lot of win users
and a really blocking win issue would have popped earlier I guess.
Romain Manni-Bucau
Twitt
Hi, my problem was i mean IS with CODI using Windows.
Here is the conversation:
http://openejb.979440.n4.nabble.com/No-bean-found-for-type-org-apache-myfaces-extensions-cdi-jsf-api-config-JsfModuleConfig-td454.html
@Romain, maybe this is realted i hope you can have a windows pc for check
it!!
Hi
to test a *war* arquillian is more adapted but if you just want to
reuse code it should work
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-22 18:09 GMT+02:00 amb
Hi Romain,
finally got it :) thank you for your advices
I migrated from openEJB 4.5.2 to 4.6.0 (there was some problems with
jboss-as-ejb-client-bom dependency, moved it, and now it's ok), and I
changed the way to initiate openEJb to :
Now I can have a Maven layer to test/junit my REST servi
Jose' can advise on this when he gets some time. Jose' is doing EARs + CDI
+ TomEE for some/many months now.
Jose', please advise on this topic at your earliest convenience.
I think Jose' had to use BeanManager and had to use the JNDI name specified
in the tomee/catalina log when tomee starts. I
hmm, can be URL related. Did you ask it on atmosphere forum? Our
scanning should be the same on both platforms now
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-22 1
Ok, the problem seems to be platform-related.
I started the same TomEE 1.6.1 SNAPHOT on two Windows 7 systems and one
Windows Server 2008 R2 (all with the latest JDK 7_55) and it failed in all
three cases (with the described error).
Then I started the same TomEE server (I used the same prepared zi
checked on ubuntu from a build of your app put in apps/ of tomee trunk
(built locally).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-22 16:27 GMT+02:00 Lars Knemeye
That's indeed strange...
Just to make sure: you deployed the
"atmosphere-chat-cdi-ear-0.0.1-SNAPSHOT.ear" from the zip I linked in my
second mail to TomEE's "apps" directory?
I did the following:
1. Download and unpack TomEE from
https://tomee.apache.org/download/tomee-1.6.1-snapshot.html
2. Crea
Here what I get:
avr. 22, 2014 4:12:56 PM org.atmosphere.cpr.AtmosphereFramework info
Infos: Atmosphere is using async support:
org.atmosphere.container.Tomcat7Servlet30SupportWithWebSocket running
under container: Apache Tomcat (TomEE)/7.0.53 (1.6.1-SNAPSHOT) using
javax.servlet/3.0
...
avr. 22,
I tried it with 1.6.0, 1.6.0.1 and the latest 1.6.1-SNAPSHOT from
https://tomee.apache.org/download/tomee-1.6.1-snapshot.html (The last one is
the trunk, isn't it?).
Unfortunately the relevant logs are only shown if you enable TRACE-Logging
for "org.atmosphere" (I use slf4j via log4j).
If you ena
seems ok on trunk, did you try?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-22 13:48 GMT+02:00 Lars Knemeyer :
> Hi, thanks for the quick reply!
>
> I created a sa
Hi, thanks for the quick reply!
I created a sample that I attached to the original Atmosphere github issue:
https://dl.dropboxusercontent.com/u/3063577/atmosphere-cdi-ear.zip
It is basically just the Atmosphere CDI sample
(https://github.com/Atmosphere/atmosphere-samples/tree/master/extensions-sam
Hi
EAR handling of TomEE is different from other servers ATM (AFAIK it is
the choice done in CDI spec but other servers did other choice before
the discussion at spec level). We maybe have a bug but we need a
sample to have a look otherwise, out of the box, I'm tempted to say
the bug is in Atmosph
Hi,
I am currently migrating my application from javax.websocket API to the
Atmosphere framework.
Sadly this migration is now stuck because CDI is not working inside my
Atmosphere service.
At first I thought it was an Atmosphere-specific problem so I filed an issue
on the Atmosphere issue tracker:
22 matches
Mail list logo
