Re: JMS and login/password

Hi we fixed yesterday by adding this line to tomee.xml ResourceAdapter = senderResourceAdapter Adding container definition is a requirement? Could it be self discovered? Alex. El dj., 12 març, 2015 a les 23:02, Romain Manni-Bucau (< rmannibu...@gmail.com>) va escriure: > Would you care

Re: JMS and login/password

Not a requirement, just if you dont use default. Reusing default names would make it smoother. Le 13 mars 2015 09:52, "Alex Soto" a écrit : > Hi we fixed yesterday by adding this line to tomee.xml > > > ResourceAdapter = senderResourceAdapter > > > Adding container definition is a require

Realm password digest

We use TomEE 1.7.1, our app authentication scheme basically looks like this: * FORM based login is used * since the login procedure differs for different customers we omitted the idea of introducing multiple realms and combining them as it would be too complex (for some only database is used, some

Re: JMS and login/password

Hi I have tried the same example in tomee2.0.0 SNAPSHOT and it happens the same, if you want I can send you the war files and configuration file. El dv., 13 març, 2015 a les 11:24, Romain Manni-Bucau (< rmannibu...@gmail.com>) va escriure: > Not a requirement, just if you dont use default. Reusin

Re: Strange ROOT.unpacked directory

Always using ROOT.war with automatic unpack. I am trying to see if this is related to cargo-maven2-plugin:redeploy via /manager application. On Fri, Mar 13, 2015 at 2:01 AM, Romain Manni-Bucau wrote: > Hi > > Can happen if ROOT is a file IIRC. Also recall having worked on sthg like > it - not rel

Re: Realm password digest

Hi Sounds you want just a lazy realm https://rmannibucau.wordpress.com/2012/08/27/tomee-put-your-realm-in-your-webapp/ Le 13 mars 2015 13:58, "Darjan Oblak" a écrit : > We use TomEE 1.7.1, our app authentication scheme basically looks like > this: > > * FORM based login is used > * since the log

Re: JMS and login/password

No no seems what you see is fine if you dont use the default ra name. Le 13 mars 2015 15:02, "Alex Soto" a écrit : > Hi I have tried the same example in tomee2.0.0 SNAPSHOT and it happens the > same, if you want I can send you the war files and configuration file. > > El dv., 13 març, 2015 a les

Re: JMS and login/password

yes so it seems that you need to define the container if you are using a custom connection. El dv., 13 març, 2015 a les 15:15, Romain Manni-Bucau (< rmannibu...@gmail.com>) va escriure: > No no seems what you see is fine if you dont use the default ra name. > Le 13 mars 2015 15:02, "Alex Soto" a

Re: JMS and login/password

Yes. A MDBContainer is bound to a resource adapter. Default config binds it to Default JMS Resource Adapter All other configs need to be explicit. Romain Manni-Bucau @rmannibucau | Blog | Github

Re: JMS and login/password

Ok thanks :) I need to update the documentation :) El dv., 13 març, 2015 a les 16:17, Romain Manni-Bucau (< rmannibu...@gmail.com>) va escriure: > Yes. > > A MDBContainer is bound to a resource adapter. > > Default config binds it to Default JMS Resource Adapter > > All other configs need to be e

Re: Realm password digest

That would be an easy solution to the current problem. But what worries me is that it doesn't seem to be portable to other containers. I still can't see what advantage does using a lazy/cusotm realm really offer compared to hashing the password prior request.login call? On Fri, Mar 13, 2015 at 3:1

Re: Realm password digest

Your issue is: where to put link between authentication and the backend? Lazy realm answer is: in the app. Spec answer is: nothing. Your proposal is: in between/in both. Implementing a custom realm: in the container Romain Manni-Bucau @rmannibucau | Blog