You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
(1159) |
Apr
(2137) |
May
(2414) |
Jun
(3068) |
Jul
(2160) |
Aug
(1232) |
Sep
(881) |
Oct
(682) |
Nov
(577) |
Dec
(311) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(619) |
Feb
(563) |
Mar
(594) |
Apr
(694) |
May
(1004) |
Jun
(2251) |
Jul
(1258) |
Aug
(1309) |
Sep
(1246) |
Oct
(1084) |
Nov
(934) |
Dec
(823) |
2003 |
Jan
(1102) |
Feb
(1115) |
Mar
(1138) |
Apr
(1369) |
May
(1356) |
Jun
(1119) |
Jul
(1074) |
Aug
(1062) |
Sep
(918) |
Oct
(834) |
Nov
(707) |
Dec
(716) |
2004 |
Jan
(571) |
Feb
(2397) |
Mar
(3637) |
Apr
(3718) |
May
(3095) |
Jun
(3054) |
Jul
(2532) |
Aug
(2092) |
Sep
(2217) |
Oct
(2336) |
Nov
(2406) |
Dec
(2315) |
2005 |
Jan
(2624) |
Feb
(2540) |
Mar
(2489) |
Apr
(2549) |
May
(2468) |
Jun
(2531) |
Jul
(2500) |
Aug
(2422) |
Sep
(2124) |
Oct
(2692) |
Nov
(2487) |
Dec
(4165) |
2006 |
Jan
(4721) |
Feb
(5016) |
Mar
(5630) |
Apr
(4747) |
May
(6193) |
Jun
(5074) |
Jul
(1734) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: <gav...@jb...> - 2006-07-10 18:24:52
|
So then it sounds like a pure-jsf problem, nothing to do with Seam, right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956688#3956688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956688 |
From: trouby <do-...@jb...> - 2006-07-10 18:22:30
|
Cool, but thanks, I'll stick with the @Transient pre-loaded data options for now... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956687#3956687 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956687 |
From: cromeroz <do-...@jb...> - 2006-07-10 18:21:28
|
I'm having the same problem with my application (I use latin characters, ISO8859-15). But the weird thing is that my windows installation seems to have no problem. The same version of JBoss on both machines, but my test server is a RedHat AS. In linux, JBoss seems to be re-encoding the UTF-8 string passed by the client again to UTF-8. Is there a way to prevent this without using the filter? I installed a tomcat 5.5 on that server and that installation seems to have no problem at all. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956686#3956686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956686 |
From: bkyrlach <do-...@jb...> - 2006-07-10 18:16:39
|
Problem 3: So, trying it a new way, I had the pages action start a conversation by invoking a method with the following annotation... @Begin(id=1) in a stateful conversational bean. However, when submitting the form on the page, the following exception is thrown... 14:15:21,805 ERROR [PhaseListenerManager] Exception in PhaseListener RENDER_RESPONSE(6) beforePhase. javax.faces.el.EvaluationException: Exception while invoking expression #{processInfozapAction.createInfoZapDTO} at org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:153) at org.jboss.seam.core.Pages.callAction(Pages.java:169) at org.jboss.seam.core.Pages.callAction(Pages.java:151) at org.jboss.seam.jsf.AbstractSeamPhaseListener.callPageActions(AbstractSeamPhaseListener.java:135) at org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:106) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:53) at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: begin method invoked from a long running conversation, try using @Begin(join=true) at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:188) at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:98) at $Proxy346.createInfoZapDTO(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:129) ... 32 more Caused by: java.lang.IllegalStateException: begin method invoked from a long running conversation, try using @Begin(join=true) at org.jboss.seam.interceptors.ConversationInterceptor.endOrBeginLongRunningConversation(ConversationInterceptor.java:44) at sun.reflect.GeneratedMethodAccessor299.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:16) at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90) at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60) at org.jboss.seam.interceptors.BusinessProcessInterceptor.manageBusinessProcessContext(BusinessProcessInterceptor.java:58) at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:16) at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90) at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60) at org.jboss.seam.interceptors.ConversationalInterceptor.checkConversationForConversationalBean(ConversationalInterceptor.java:80) at sun.reflect.GeneratedMethodAccessor297.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:16) at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90) at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60) at org.jboss.seam.interceptors.RemoveInterceptor.removeIfNecessary(RemoveInterceptor.java:39) at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:16) at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90) at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60) at org.jboss.seam.interceptors.ExceptionInterceptor.handleExceptions(ExceptionInterceptor.java:40) at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:16) at org.jboss.seam.interceptors.Interceptor.aroundInvoke(Interceptor.java:90) at org.jboss.seam.interceptors.SeamInvocationContext.proceed(SeamInvocationContext.java:60) at org.jboss.seam.ejb.SeamInterceptor.aroundInvokeInContexts(SeamInterceptor.java:73) at org.jboss.seam.ejb.SeamInterceptor.aroundInvoke(SeamInterceptor.java:45) at sun.reflect.GeneratedMethodAccessor351.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:57) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) ... 52 more This is wrong according to the Seam documentation, which says that if you call the @Begin method of a conversational bean and the id expression evaluates to the same id as the current conversation, that the @Begin method will be skipped, and you'll join the currently in progress conversation. Please help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956684#3956684 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956684 |
From: trouby <do-...@jb...> - 2006-07-10 18:16:11
|
Hey, I dont think this is the problem, the stateless bean is accessible ( I use a DataModel to display the dataTable where each of its rows is a checkbox ) and the methods are accessible, the problem -ONLY- occures when I use a 'selectBooleanCheckbox' where its value is an array! when the value is not an array the action is executed fine :-/ Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956683#3956683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956683 |
From: <gav...@jb...> - 2006-07-10 18:13:48
|
facelets has ui:composition/ui:define which lets you do the stuff that tiles is mostly used for. I understand that tiles has some extra functionality but are you sure you need it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956682#3956682 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956682 |
From: <gav...@jb...> - 2006-07-10 18:13:08
|
Add a @Begin annotation to the page action method. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956681#3956681 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956681 |
From: <gav...@jb...> - 2006-07-10 18:12:08
|
Note that the correct way to handle this problem today is to put a mutable component in the parent conversation context, and set a property value from the child conversation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956680#3956680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956680 |
From: <gav...@jb...> - 2006-07-10 18:08:53
|
Check the Seam startup log, to make sure that all your components are actually getting installed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956679#3956679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956679 |
From: DreadPirateFlint <do-...@jb...> - 2006-07-10 18:01:49
|
Tim, Thanks for attempting and succesfully reproducing. I have been away from the net for awhile with heath issues. I was able to figure out what was happening. I was attempting to re-subscribe with the same clientID (not subscription ID), and it was taking awhile for the jboss server to time out the clientID. Reconnecting with a different client ID did the trick. Looks like you may have found a problem anyway. Thanks for the effort! /kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956678#3956678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956678 |
From: <rob...@jb...> - 2006-07-10 18:01:08
|
"oabidian" wrote : Right click and remove from server. Does not remove it from the disk (removes it from the view but not disk). Anyhow, I am giving up on it. I will wait until a stable release is available (JBoss Eclipse IDE). | Thanks for the replies. Thanks for reporting this, oabidan. I had thought I had fixed this problem but upon delving deeper I found some upstream coad caching something that I wasn't aware of. Thanks again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956677#3956677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956677 |
From: rpiaggio <do-...@jb...> - 2006-07-10 17:59:12
|
I think it is great to have a component for email manipulation, but IMHO this concern is orthogonal to that of a web framework. Including something like this in the Seam standard would add unnecesary complexity to the framework and its documentation. Again, IM(Very)HO, I see a place for a repository of optional additional components for specific concerns. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956676#3956676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956676 |
From: <gav...@jb...> - 2006-07-10 17:57:16
|
The docs are wrong. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956675#3956675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956675 |
From: <gav...@jb...> - 2006-07-10 17:56:56
|
This is all designed to minimize the traffic involved in replicating changes across a cluster. Your proposal would require replicating the entire conversation on each request to the server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956674#3956674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956674 |
From: <gav...@jb...> - 2006-07-10 17:55:22
|
Right, but EJB3 injection is just perfect here, no need for anything new, I guess... Of course, it would be -totally- trivial to create a manager component for a datasource, but I don't see the need. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956672#3956672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956672 |
From: krsenthil <do-...@jb...> - 2006-07-10 17:54:27
|
Hi cpob, Thanks for your response. The Action allows to set up handler?s trap one of the below event type. I don't think you can use it for setting up Decision handler. I think API for setting up decision handler in "Decision" class is missing or may be I am missing something here. Also I have modified my code to create an action and associate with Decision but my handler wasn't called. Decision amountcheck = new Decision(); amountcheck.setName("amountcheck"); processDefinition.addNode(amountcheck); Delegation delegation = new Delegation(); delegation.setClassName("com.mycomp.test.AmountDecisionHandler"); Action action = new Action(); action.setActionDelegation(delegation); amountcheck.setAction(action); Action events types : public static final String EVENTTYPE_TRANSITION = "transition"; public static final String EVENTTYPE_BEFORE_SIGNAL = "before-signal"; public static final String EVENTTYPE_AFTER_SIGNAL = "after-signal"; public static final String EVENTTYPE_PROCESS_START = "process-start"; public static final String EVENTTYPE_PROCESS_END = "process-end"; public static final String EVENTTYPE_NODE_ENTER = "node-enter"; public static final String EVENTTYPE_NODE_LEAVE = "node-leave"; public static final String EVENTTYPE_SUPERSTATE_ENTER = "superstate-enter"; public static final String EVENTTYPE_SUPERSTATE_LEAVE = "superstate-leave"; public static final String EVENTTYPE_SUBPROCESS_CREATED = "subprocess-created"; public static final String EVENTTYPE_SUBPROCESS_END = "subprocess-end"; public static final String EVENTTYPE_TASK_CREATE = "task-create"; public static final String EVENTTYPE_TASK_ASSIGN = "task-assign"; public static final String EVENTTYPE_TASK_START = "task-start"; public static final String EVENTTYPE_TASK_END = "task-end"; public static final String EVENTTYPE_TIMER = "timer"; View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956671#3956671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956671 |
From: <gav...@jb...> - 2006-07-10 17:53:46
|
The whole area of processing email is an important one that I wanted to get sorted out, but it just keeps getting pushed and pushed... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956670#3956670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956670 |
From: halversp <do-...@jb...> - 2006-07-10 17:53:38
|
I worked around it by changing the mapped table name from JBP_OBJECT_NODE_SECURITY_ACTIONS to JBP_OBJ_NODE_SEC_ACTS in the hibernate mapping file. Seemed to work (after I dropped the schema and rebuilt), but I'm surprised it wasn't caught before. pch View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956669#3956669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956669 |
From: <gav...@jb...> - 2006-07-10 17:50:19
|
"bambata" wrote : So, in case of a stateless Bean Seam uses for Injection via @In a common | JNDI-lookup to the containers registry(ENC) ? | | In the case of a SLSB, @In does a JNDI lookup (global or ENC). In the case of a JavaBean, it does a new. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956668#3956668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956668 |
From: <gav...@jb...> - 2006-07-10 17:48:21
|
I have not looked at Ajax4JSf before, so I can't help you with your immediate problem - try using your debugger. Our plan for partial rendering in JSF was to implement something probably quite similar to Ajax4JSF on top of the work that Jacob/Adam/Ed have been doing. Actually I was going to work on that stuff over the next couple of weeks and release it as Seam 1.1. However, I will take a closer look at Ajax4JSF and see if it is a better starting point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956667#3956667 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956667 |
From: halversp <do-...@jb...> - 2006-07-10 17:40:37
|
Was this fix incorporated into 2.4? I'm getting the same error: | 2006-07-10 13:20:06,109 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] Unsuccessful: create table JBP_OBJECT_NODE_SECURITY_ACTIONS (PK number(19,0) not null, ACTIONS varchar2(255 char)) | 2006-07-10 13:20:06,109 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] ORA-00972: identifier is too long | JBoss Portal 2.4.0 Beta1 Bundled Oracle 10g Pete View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956666#3956666 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956666 |
From: petemuir <do-...@jb...> - 2006-07-10 17:38:07
|
No it can only send email. When I wrote this I started off with the JavaMail API (which jboss has an impl of) which CAN be used to receive email but changed to commons email (which is build on JavaMail API) as it presented an easier to use interface. And I have no need to receive emails ;) I might have another look at how much worse it would be to use the javamail api rather than commons. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956665#3956665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956665 |
From: <gav...@jb...> - 2006-07-10 17:35:39
|
What version of myfaces are you using? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956664#3956664 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956664 |
From: <gav...@jb...> - 2006-07-10 17:34:11
|
Not at present no, sorry. Basically, for now, just use the capabilities that are built in to EJB3. Seam 1.5 will provide deep integration with the WS/ESB layer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956663#3956663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956663 |
From: <gav...@jb...> - 2006-07-10 17:30:24
|
You must retrieve the entity from the conversation-scoped PC, and then whenever a transaction commits, changes to the entity will be flushed to the database. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956661#3956661 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956661 |