Three new doubts...
1) Is there some way to print messages in server.log to guarantee that
the conversation is destroyed at a time, in development time? Some
config in logging.properties...
2) I configured my web.xml to redirect this kind of exception to a
default html file. Does this work ?
<error-page>
<exception-type>javax.enterprise.context.NonexistentConversationException</exception-type>
<location>/expired.html</location>
</error-page>
<error-page>
<exception-type>org.jboss.weld.context.NonexistentConversationException</exception-type>
<location>/expired.html</location>
</error-page>
<error-page>
<exception-type>javax.faces.application.ViewExpiredException</exception-type>
<location>/expired.html</location>
</error-page>
3) Is it possible to disable the logs below in a production environment?
Informações: class:
org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeExternalContextWrapper
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.listener.request.JsfRequestBroadcaster
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.exception.control.BridgeExceptionHandlerWrapper
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.security.SecurityAwareViewHandler
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.navigation.NavigationHandlerAwareApplication
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.token.DoubleSubmitAwarePhaseListener
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.scope.window.JsfWindowContextQuotaHandler
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.view.DeltaSpikeViewHandler activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.config.view.ViewControllerActionListener
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.navigation.DeltaSpikeNavigationHandler
activated=true
Informações: class:
org.apache.deltaspike.jsf.impl.scope.viewaccess.ViewAccessScopedAwareNavigationHandler
activated=true
On 26-12-2014 14:05, Gerhard Petracek wrote:
hi edilmar,
codi did that for you (automatically).
with deltaspike you need to do it manually (see e.g. [1]).
regards,
gerhard
[1]
https://github.com/os890/ee6-ds-demo/blob/master/src/main/webapp/templates/main-template.xhtml#L94
http://www.irian.at
Your JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache
MyFaces, DeltaSpike and OpenWebBeans
2014-12-26 17:57 GMT+01:00 Edilmar LISTAS <[email protected]>:
Hi again,
I am migrating to DeltaSpike GroupConversationScoped now but I didn't
undertand this part:
Therefore, do not forget to add the ds:windowId (xmlns:ds="
http://deltaspike.apache.org/jsf";) component in case of
ClientWindowConfig#CLIENTWINDOW to your page(/template) and ensure that
the window-handling works properly (otherwise conversations will not work
correctly). The base principle is similar to CODI-Conversations. CODI users
just have to ensure that they have to add ds:windowId and the names are
slightly different.
When using CODI I never configured ds:windowId in any place and
I really don't know what about this.
On 08-12-2014 14:33, Thomas Andraschko wrote:
Hey,
DeltaSpike is compatible with JEE6 and JEE7 :)
2014-12-08 18:04 GMT+01:00 Edilmar LISTAS <[email protected]>:
Hi,
Just one more question... is it possible to migrate from CODI to
DeltaSpike conversations
but to continue using JEE6, Glassfish 3.1.2.2, JSF 2.1 and CDI/Weld
2.1.6?
Because this
would be great, because I could change all the controllers to new class
and imports before
a bigger upgrade to JEE7 and many new libraries that I need to
test/checkout.
On 02-12-2014 16:58, Gerhard Petracek wrote:
hi edilmar,
@GroupedConversationScoped is just a new name, but you get the same
concept
as with codi.
you can inject GroupedConversation as well as GroupedConversationManager
to
manage conversations (see [1] and e.g. [2]).
just fyi:
the reset to null isn't needed. with that you just drop the injected
proxy
and not the conversation itself -> #close is enough.
regards,
gerhard
[1]
http://deltaspike.apache.org/documentation/jsf.html#__
grouped_conversations
[2] https://github.com/os890/tomee_mf_stack_001/tree/codi2ds
http://www.irian.at
Your JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache
MyFaces, DeltaSpike and OpenWebBeans
2014-12-02 19:38 GMT+01:00 Edilmar LISTAS <[email protected]>:
Hi,
I have a web/enterprise app running at this environment:
Glassfish 3.1.2.2 + JSF 2.1 + Richfaces 4.3.7 + CDI + CODI 1.0.6 + JPA
2.0
+ Hibernate 4.2.7.
Now, I have planned migrating from JEE6 to JEE7:
Glassfish 4.1 + JSF 2.2 + Richfaces 4.5 (waiting final version) + CDI +
DeltaSpike 1.1.0 + JPA 2.1 + Hibernate 4.3.x.
I use only ConversationScope from CODI like this:
=========
1) CODE 1:
=========
import org.apache.myfaces.extensions.cdi.core.api.scope.conversation.
ConversationScoped;
...
@ConversationScoped
public class Controller1 implements Serializable {
private @Inject Conversation conversation;
...
public void aPlaceToCloseConversation(ActionEvent event) {
if (conversation != null) {
conversation.close();
conversation = null;
}
}
}
=========
2) CODE 2:
=========
import org.apache.myfaces.extensions.cdi.core.api.scope.
conversation.WindowContext;
...
@RequestScoped
public class Controller2 implements Serializable {
@Inject WindowContext windowContext;
...
public void aPlaceToCloseAllConversations(ActionEvent event) {
windowContext.closeConversations();
}
}
I didn't find a way to migrate my ConversationScoped to DeltaSpike,
just
I
found GroupConversations
and ViewScoped. What have I to change in my code for this migration?
