[jboss-user] [JBoss Seam] - Re: Inject EBJ

2007-03-22 Thread kayart
Thank for your advice. "petemuir" wrote : That should be @In(create=true) I have another problem. I've had the following exception. javax.naming.NameNotFoundException: No object bound to name java:comp/env/SeamFaceletsTemplate/Action2Bean/local Maybe seam can't search the object. I'm using

[jboss-user] [JBoss Seam] - Re: Inject EBJ

2007-03-19 Thread kayart
Hello, "petemuir" wrote : Try @Stateless | | @Name("action2") | | public class Action2Bean implements Action2Local { | | @In private Action1Local action1; | | } acton1 is typo. I have another example. --- @Stateless @Name("action2") public class Action2Bean implements Action2L

[jboss-user] [JBoss Seam] - Inject EBJ

2007-03-19 Thread kayart
I'm working on Seam1.2 and GlassFish. Plase tell me how to inject ejb into ejb. ---class1--- @Stateless @Name("action1") public class Action1Bean implements Action1Local {...} ---class2--- @Stateless @Name("action2") public class Action2Bean implements Action2Local { @EJB private Action1Loca

[jboss-user] [JBoss Seam] - Re: Req: I18N mail function

2007-03-07 Thread kayart
I'll write the requirements of the mail format in Japan again. - Message body must be ISO-2022-JP. - Subject, from, to (etc.) headers in Japanese must be ISO-2022-JP and be encoded by base64. - Content-Type and Content-Transfer-Encoding must be set to charset=ISO-2022-JP and 7bit. So, I made

[jboss-user] [JBoss Seam] - Re: Req: I18N mail function

2007-03-05 Thread kayart
"petemuir" wrote : For the message body you *should* be able to just set the encoding as per normal for facelets. I haven't heard this failing but... please test :) That's right, but note that Content-Type and Content-Transfer-Encoding fields must be set. --Kay View the original post : htt

[jboss-user] [JBoss Seam] - Req: I18N mail function

2007-03-01 Thread kayart
Folks I'd like to send mail message by seam-mail in Japanese. Mail messages are required the following format in Japan. - Message body must be ISO-2022-JP. - Subject, from, to (etc.) headers in Japanese must be ISO-2022-JP and be encoded by base64. - Content-Type and Content-Transfer-Encoding