[JBoss Portal] - Re: MS SQL with Jboss-portal-2.6-BETA1
by glarenzie
This is a list of tables built and populated, are they all there?
jbp_cms_cmsentry
jbp_cms_perm
jbp_cms_perm_criteria
jbp_cms_perm_role
jbp_cms_perm_user
jbp_cms_repositoryentry
jbp_cms_version_binval
jbp_cms_version_node
jbp_cms_version_prop
jbp_cms_version_refs
jbp_cms_versionentry
jbp_cms_wsp_binval
jbp_cms_wsp_node
jbp_cms_wsp_prop
jbp_cms_wsp_refs
JBP_CONTEXT
JBP_INSTANCE
JBP_INSTANCE_PER_USER
JBP_INSTANCE_SECURITY
JBP_INSTANCE_SECURITY_ACTIONS
JBP_OBJECT_NODE
JBP_OBJECT_NODE_SEC
JBP_OBJECT_NODE_SEC_ACTIONS
JBP_PAGE
JBP_PORTAL
JBP_PORTAL_MODE
JBP_PORTAL_OBJECT
JBP_PORTAL_OBJECT_PROPS
JBP_PORTAL_WINDOW_STATE
JBP_PORTLET_CONSUMER
JBP_PORTLET_GROUP
JBP_PORTLET_REGISTRATION
JBP_PORTLET_STATE
JBP_PORTLET_STATE_ENTRY
JBP_PORTLET_STATE_ENTRY_VALUE
jbp_role_membership
jbp_roles
jbp_user_prop
jbp_users
JBP_WINDOW
JBPM_ACTION
JBPM_BYTEARRAY
JBPM_BYTEBLOCK
JBPM_COMMENT
JBPM_DECISIONCONDITIONS
JBPM_DELEGATION
JBPM_EVENT
JBPM_EXCEPTIONHANDLER
JBPM_ID_GROUP
JBPM_ID_MEMBERSHIP
JBPM_ID_PERMISSIONS
JBPM_ID_USER
JBPM_LOG
JBPM_MESSAGE
JBPM_MODULEDEFINITION
JBPM_MODULEINSTANCE
JBPM_NODE
JBPM_POOLEDACTOR
JBPM_PROCESSDEFINITION
JBPM_PROCESSINSTANCE
JBPM_RUNTIMEACTION
JBPM_SWIMLANE
JBPM_SWIMLANEINSTANCE
JBPM_TASK
JBPM_TASKACTORPOOL
JBPM_TASKCONTROLLER
JBPM_TASKINSTANCE
JBPM_TIMER
JBPM_TOKEN
JBPM_TOKENVARIABLEMAP
JBPM_TRANSITION
JBPM_VARIABLEACCESS
JBPM_VARIABLEINSTANCE
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038132#4038132
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038132
19 years, 1 month
[JBoss Seam] - Re: Seam Conversation Should Be Flexible but NOT
by app4you@yahoo.com
anonymous wrote :
| -> SESSION scope is never a good implementation unless you have a very good reason to go for,
|
| Yes, you shouldn't put data that doesn't need to be session scoped into the session. But if your spec says that you need session scope views then...
Did you read my post carefully yet :) Common I did not say that I need all components in SESSION.
anonymous wrote : neither a very long running conversation timeout or even set it to the same time-out as the HTTP session time out. Standard is 30 minutes, or at least most of my apps.
|
|
| Sorry, I can't parse this.
Can't see? Can you look at the conversation stack for a bunch of runaway conversations waiting to be closed? Hardware is cheap but never enough for a large user base environment.
anonymous wrote : <core:manager concurrent-request-timeout="500"
| conversation-timeout="#{session.timeout}" conversation-id-parameter="cid"
| conversation-is-long-running-parameter="clr" />
I knew this and did even use Seam's API to control programmatically but this is not what I was talking about in my original post. A more elegant timeout that coordinates with http session timeout.
anonymous wrote : Yes, if you want to hold open a view as long as the sesion is active, then you have to use the session to hold the data. A shorter-lived scope won't ever cut it here!I don't want to use conversational session scope, only conversational scope here or no conversation at all by setting the conversation on/off.
Thanks anyway
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038129#4038129
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038129
19 years, 1 month
[JBoss Seam] - Re: Problems Starting Page Flows
by Delphi's Ghost
anonymous wrote : The outcome you return from your action method on starting the pageflow should determine which transition it uses from the start-state - if you are sure it doesn't, raise an issue in JIRA
AFAICT, when using the start-state pageflow the following applies :
void action methods start the pageflow on the first page (correct)
non-null outcomes with a matching transition in the start-state element results in making that transition and displaying the transitioned-to page(correct)
non-null outcomes without a matching transition in the start-state element results in re-displaying the current page.(don't know)
Null outcomes re-display the same page (correct)
Heh, you're right, you can use global outcome managers to navigate to that link AND get the benefit of RESTful URLs
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038126#4038126
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038126
19 years, 1 month
[JBoss Seam] - Re: Seam Conversation Should Be Flexible but NOT
by petemuir
"app4you(a)yahoo.com" wrote :
| -> SESSION scope is never a good implementation unless you have a very good reason to go for,
Yes, you shouldn't put data that doesn't need to be session scoped into the session. But if your spec says that you need session scope views then...
anonymous wrote : neither a very long running conversation timeout or even set it to the same time-out as the HTTP session time out. Standard is 30 minutes, or at least most of my apps.
Sorry, I can't parse this.
anonymous wrote : ->. Imagine that your application has tab and tree UI components exposed all time and setting the conversation timeout greater than the HTTP session time out or unlimited, aren't you asking for trouble? You will have a whole bunch of runaway conversations running behind the scene and waiting to be closed by the their conversation timers, assume that the user did not click on the DONE or CLOSE button to close the forms' conversations properly.
I can't see why.
anonymous wrote : anonymous wrote : Or are you after flexibility - giving different conversations different timeouts (you can currently do this programmatically, but not through xml/annotations)
|
| -> Who would you go about that? And would that manually setting be scattered all over the place, for each component that is?
You could have a property on the @Begin annotation and on the pages.xml begin-conversation element that takes either a integer or injects an integer using EL. Further, there is undocumented support for conversations which use natural ids - you could set the timeout for such a conversation.
anonymous wrote : What we need is the ability to control the conversation time-out to rely on the HTTP session timeout
Something like this would perhaps help (but you would still get conversations timing out before the session if they hadn't been "touched" recently).
components.xml
| <core:manager concurrent-request-timeout="500"
| conversation-timeout="#{session.timeout}" conversation-id-parameter="cid"
| conversation-is-long-running-parameter="clr" />
|
anonymous wrote : or a way to disable the conversation timeout but not by means of "never timed out conversations"
Surely this is an oxymoron - you want to have conversations that don't timeout but don't never timeout. You need to explain this one better ;) If you are saying you want to clean up the conversations associated with a user when their session times out, then this is current behaviour.
anonymous wrote : Just try to put a complex UI application that has a lot of business components with tree+tab interfaces and see how sufficient the application conversation stack can be. Please make sure that "the application data entry form has to be in the edit mode all the time unless the user want to close the form by clicking on the DONE, CLOSE or whatever... button to get back to the search result page".
|
Yes, if you want to hold open a view as long as the sesion is active, then you have to use the session to hold the data. A shorter-lived scope won't ever cut it here!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038120#4038120
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038120
19 years, 1 month