Tomeerealm is a.wrapper for your realm so issue with it
Le 31 août 2012 23:45, "Luca Merolla" a écrit :
> Yes the url should be fine.
>
> I have configured the Realm inside the Engine like this:
>
> localDataSource="true"
> dataSourceName="MyDS"
> userTable="VUser" userNameCol="vname" userCredCo
Yes the url should be fine.
I have configured the Realm inside the Engine like this:
Looking in the jconsole I see 3 realm:
/realm0 [TomEERealm]
/realm0/realm0 [LockOutRealm]
/realm0/realm0/realm0 [UserDatabaseRealm]
I don't know if TomEERealm is my Realm
I think you need to set a custom jnditemplate. Personally i used jee
namespace, thats easier
Le 31 août 2012 22:22, "laredotornado" a écrit :
> Hi,
>
> I am using jee:lookup, at least I think so. We use a "jndiName" property
> in
> the Spring application context file. Here's the declaration in
Hi,
I am using jee:lookup, at least I think so. We use a "jndiName" property in
the Spring application context file. Here's the declaration in that file
...
http://www.springframework.org/dtd/spring-beans.dtd";>
= Begin spring context snippet
===
It can be.
I can have a look around the 10th of september
Le 31 août 2012 20:58, "Luca Merolla" a écrit :
> I have done some tests with my war with the latest snapshot of TomEE. These
> are the libraries that are inside the WEB-INF/lib of the war
>
> asm-3.1.jar
> atmosphere-annotations-1.0.0.be
You checked the url?
Hmm no more idea, is the ds is good, the realm well configured it should be
fine
Le 31 août 2012 19:27, "Luca Merolla" a écrit :
> I can see my datasource with the jconsole, but still I get the same error.
>
> On Fri, Aug 31, 2012 at 1:52 PM, Romain Manni-Bucau
> wrote:
>
>
I have done some tests with my war with the latest snapshot of TomEE. These
are the libraries that are inside the WEB-INF/lib of the war
asm-3.1.jar
atmosphere-annotations-1.0.0.beta5.jar
atmosphere-compat-jbossweb-1.0.0.beta5.jar
atmosphere-compat-tomcat-1.0.0.beta5.jar
atmosphere-compat-tomcat7-
Added
- Original Message -
From: "David Blevins"
To:
Sent: Saturday, September 01, 2012 3:43 AM
Subject: Help make TomEE official on LinkedIn
Help us make TomEE an official Sill on LinkedIn!
Here's how Tomcat looks:
- http://www.linkedin.com/skills/skill/Tomcat
We'd love to see T
Help us make TomEE an official Sill on LinkedIn!
Here's how Tomcat looks:
- http://www.linkedin.com/skills/skill/Tomcat
We'd love to see TomEE listed as well (link will currently not work):
- http://www.linkedin.com/skills/skill/TomEE
We need you to help make that happen. Add 'TomEE' to you
I can see my datasource with the jconsole, but still I get the same error.
On Fri, Aug 31, 2012 at 1:52 PM, Romain Manni-Bucau
wrote:
> You should be able to check your datasource config through JMX.
>
> - Romain
> Le 31 août 2012 12:55, "Luca Merolla" a écrit :
>
> > I think it must be somethin
No, that's pretty new. However some of our trunk examples already use it.
- Romain
Le 31 août 2012 18:11, "Yann Blazart" a écrit :
> Hi ! I'm trying to use arquillian with embedded openejb. I only found a
> 4.1.0-SNAPSHOT of arquillian-openejb-embedded-4 in repository.apache.org.
>
> Does 4.0.0
Hi ! I'm trying to use arquillian with embedded openejb. I only found a
4.1.0-SNAPSHOT of arquillian-openejb-embedded-4 in repository.apache.org.
Does 4.0.0 exists ?
Add these properties in spring lookup (only needed in embedded, not tomee)
Le 31 août 2012 16:38, "laredotornado" a écrit :
> Hi,
>
> I'm using OpenEJB 4.0.0, Spring 3.1.0.RELEASE, and JUnit 4.8.1. I'm trying
> to test a Spring controller that attempts to get an EJB from JNDI …
>
>
Do you have a short example to share (kinda Hello Worldline)?
I already made that working few month ago so it should a matter of
configuration.
Jean-Louis
2012/8/31 laredotornado
> Hi,
>
> I'm using OpenEJB 4.0.0, Spring 3.1.0.RELEASE, and JUnit 4.8.1. I'm trying
> to test a Spring controller
Hi,
I'm using OpenEJB 4.0.0, Spring 3.1.0.RELEASE, and JUnit 4.8.1. I'm trying
to test a Spring controller that attempts to get an EJB from JNDI …
final Context context = new InitialContext();
Object myprojectStandardMgrHomeObj = context.lookup(
"MyProjectStandard
Nothing against it but here is my opinion,
JEE is designed to be testable so no need of any "complicated for nothing"
framework.
For me mockito answer to a different need.
For a cdi sample we have an example on trunk using alternatives ans
stereotypes.
- Romain
Le 31 août 2012 12:45, "Yann Blaz
You should be able to check your datasource config through JMX.
- Romain
Le 31 août 2012 12:55, "Luca Merolla" a écrit :
> I think it must be something wrong with the configuration of the
> datasource.
>
> In fact in the database for "admin:admin" I have
>
> admin:21232f297a57a5a743894a0e4a801fc
I think it must be something wrong with the configuration of the datasource.
In fact in the database for "admin:admin" I have
admin:21232f297a57a5a743894a0e4a801fc3
and If I try to generate the MD5 digest from the command line I get the
same value:
java -classpath "*:/home/luca/bin/apache-tomee
I'm agree but tests with arquilian take more time than simple unit tests.
Le 31 août 2012 11:21, "Jean-Louis MONTEIRO" a écrit :
> Waiting for Romain's answer, but I guess it will be. Mocking is an old
> school solution ;-)
> Indeed, nowadays, and mainly thanks to EJB 3 lite, Arquillian, and so o
Waiting for Romain's answer, but I guess it will be. Mocking is an old
school solution ;-)
Indeed, nowadays, and mainly thanks to EJB 3 lite, Arquillian, and so on,
it's far easier to get simple integration tests. So the need to really
write unit tests is smaller.
Just some thoughts.
Romain is cur
Well, in fact I'm not sure to go in the right way.
I wan't to make the demonstration that jee6 can now replace spring.
One thing very interesting in spring is about that faculty to make
"unit-test" between real unit-test and integration tests with
@Configuration. I wanted to make the same thing.
Did you play with digest attribute?
Le 30 août 2012 23:46, "Luca Merolla" a écrit :
> I think here the problem is the encoding of the password defined in the
> datasource.
>
> Basically since I'm migrating from JBoss, where I have a configuration like
> that:
>
>
> v
I dont think so (the proxy). The need is more than it: vetoing a bean
deployment (not managed today i think) + mocking (i would like to avoid to
update core for this need)
- Romain
Le 31 août 2012 09:15, "Jean-Louis MONTEIRO" a écrit :
> Romain,
>
> maybe a proxy handler on top of the business i
Romain,
maybe a proxy handler on top of the business interface can do the trick.
Not sure it will work, but it should be able to provide any implementation
even a mock to a business interface.
The need is there, so that be great to have a look.
Any other ideas?
Jean-Louis
2012/8/30 Romain Mann
24 matches
Mail list logo
