Re: EJB Injection in JSF Managed Bean

I am replying to my original post because I was not subscribed to mailing list at the time when I posted my problem. I'd like everybody to know about existence of this topic. -- View this message in context: http://openejb.979440.n4.nabble.com/EJB-Injection-in-JSF-Managed-Bean-tp4634407p4634823.h

Re: EJB Injection in JSF Managed Bean

it is a bug of the 1.0.0, there is a JIRA about it explaining it was during the jsf optimization phase when we refactored the scanning logic (jira is offline for maintance so i can't find the link back, sorry) it is already fixed on the snapshot - Romain 2012/5/15 marcin > I am replying to my

Re: EJB Injection in JSF Managed Bean

Thanks for help. I've tried to find new snapshot in binary form but without a success. Do I have to build OpenEJB from head revision from SVN in order to acquire fixed version? -- View this message in context: http://openejb.979440.n4.nabble.com/EJB-Injection-in-JSF-Managed-Bean-tp4634407p4634892

Re: EJB Injection in JSF Managed Bean

Here it is https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.0.0-beta-3-SNAPSHOT/ Ignore the beta-3 we have to fix versions on trunk - Romain Le 15 mai 2012 19:07, "marcin" a écrit : > Thanks for help. I've tried to find new snapshot in binary form but > w

Re: Tomee Datasource

I did this: context.mxl MyDataSourceRealm.java: package realm.test; import java.sql.Connection; import javax.naming.InitialContext; import javax.sql.DataSource; public class MyDataSourceRealm extends org.apache.catalina.realm.DataSourceRealm{ @Override protected Connection op

Re: EJB Injection in JSF Managed Bean

Thanks for the link. I've downloaded snapshot and deployed my application on this new server. The problem with injection of EJB indeed is no longer present, but I have found another bug. On beta-2 resources of JSF application can be accessed with URL such as: http://localhost:8080/MyApplication/ja

Re: Tomee Datasource

it should be in tomee libs, not your project. (another solution is to use the snapshot ;) and use the default datasource realm) - Romain 2012/5/15 José Luis Cetina > I did this: > > context.mxl > > > > dataSourceName="MyDataSource" > userTable="usertable" > userNameCol="usercol" > userC

Re: EJB Injection in JSF Managed Bean

why did you add .xhtml? - Romain 2012/5/15 marcin > Thanks for the link. I've downloaded snapshot and deployed my application > on > this new server. The problem with injection of EJB indeed is no longer > present, but I have found another bug. > > On beta-2 resources of JSF application can be

Re: EJB Injection in JSF Managed Bean

Hmm, this is a good question. It is the only way it worked on beta-2. Maybe it is somehow connected with my declaration of servlet mapping, i.e.: Faces Servlet *.xhtml -- View this message in context: http://openejb.979440.n4.nabble.com/EJB-Injection-in-JSF-Managed-Bean-tp4634407p46350

Re: Tomee Datasource

Ok i add my class in a jar file, but im getting: javax.naming.NameNotFoundException:The name openejb/Resource/MyDataSource does not exist in the current context. is openejb/Resource/MyDataSource the correct directory for use the datasource? 2012/5/15 Romain Manni-Bucau > it should be in tome

Re: Tomee Datasource

it seems fine, any luck you share this part of the project? - Romain 2012/5/15 José Luis Cetina > Ok i add my class in a jar file, but im getting: > > javax.naming.NameNotFoundException:The name openejb/Resource/MyDataSource > does not exist in the current context. > > is openejb/Resource/MyD

Re: Tomee Datasource

((DataSource) new InitialContext().lookup("openejb:Resource/myDataSource")).getConnection() sorry i pasted the bad path last time - Romain 2012/5/15 Romain Manni-Bucau > it seems fine, any luck you share this part of the project? > > - Romain > > > 2012/5/15 José Luis Cetina > >> Ok i add my

Re: Tomee Datasource

Here is the configuration: MyDataSourceRealm.java: package test.myrealm; import java.sql.Connection; import javax.naming.InitialContext; import javax.sql.DataSource; public class MyDataSourceRealm extends org.apache.catalina.realm.DataSourceRealm{ @Override protected Connection open()

DigestEncoding DataSourceRealm

This is my realm declaration: This work with SHA-256 and hex encoding password, but if i want to explicit add the digestEncodig (digestEncoding="hexadecimal" or digestEncoding="hex" or digestEncoding="HEX") like this: I get: Severe: Illegal digestEncoding: hex java.io.UnsupportedEncodingE

Re: DigestEncoding DataSourceRealm

Did you override the validation? Le 15 mai 2012 22:32, "José Luis Cetina" a écrit : > This is my realm declaration: > > className="com.test.MyDataSourceRealm" >dataSourceName="MyDataSource" >userTable=" userTable " >userNameCol=" userNameCol " >userCredCol=

Re: DigestEncoding DataSourceRealm

Noup, here is my entire class: package com.test; import java.sql.Connection; import javax.naming.InitialContext; import javax.sql.DataSource; public class MyDataSourceRealm extends org.apache.catalina.realm.DataSourceRealm{ @Override protected Connection open() { System.out.prin

Re: DigestEncoding DataSourceRealm

here the comments: /** * Digest algorithm used in storing passwords in a non-plaintext format. * Valid values are those accepted for the algorithm name by the * MessageDigest class, or null if no digesting should * be performed. */ protected String digest = null;