[JBoss JIRA] Created: (JBPM-1875) Reset views when model changes
by Heiko Braun (JIRA)
Reset views when model changes
------------------------------
Key: JBPM-1875
URL: https://jira.jboss.org/jira/browse/JBPM-1875
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 CR1
It requires some listener mechanism, when the model changes (i.e. RemoteListView#reload()) associated widgets can reset/restore their state accordingly.
This does for instance happen with forms that are attached to grids, when the grid turns empty,
the last selected record still displays in the form.
But it does also happen across editor views. I.e. when a process instance is deleted the task list doesn't refresh and might show stale data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months
[JBoss JIRA] Commented: (JBPM-1450) Disable jBPM logging
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1450?page=com.atlassian.jira.plug... ]
Thomas Diesler commented on JBPM-1450:
--------------------------------------
Thomas,
Resolving this issue simply requires a change in the jBPM configuration.
I understand SOA-P uses its own jBPM and Hibernate configuration files.
We should change those files directly.
Julian, can you confirm whether SOA-P uses a separate jBPM configuration
Thomas,
Resolving this issue simply requires a change in the jBPM configuration.
I understand SOA-P uses its own jBPM and Hibernate configuration files.
We should change those files directly.
Julian, can you confirm whether SOA-P uses a separate jBPM configuration
file? If so, please let me know how can I change it. Alternatively I can
post the required changes in a comment to the Jira issue.
-Alejandro
El lun, 24-11-2008 a las 09:08 +0100, Thomas Diesler escribió:
> > Hi Alejandro,
> >
> > this issue https://jira.jboss.org/jira/browse/JBPM-1450 is still open,
> > but CP03 has been tagged already. What do we need to do about it?
> >
> > cheers
> > -thomas
> >
> Disable jBPM logging
> --------------------
>
> Key: JBPM-1450
> URL: https://jira.jboss.org/jira/browse/JBPM-1450
> Project: JBoss jBPM
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Mark Little
> Assignee: Alejandro Guizar
> Fix For: SOA 4.2 CP03, SOA 4.3
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months