[JBoss JIRA] Created: (GPD-78) configInfoElements of semantic elements are not always added to XML adapters
by John Ruud (JIRA)
configInfoElements of semantic elements are not always added to XML adapters
----------------------------------------------------------------------------
Key: GPD-78
URL: http://jira.jboss.com/jira/browse/GPD-78
Project: JBoss jBPM GPD
Issue Type: Bug
Reporter: John Ruud
Assigned To: Koen Aers
For example, if a node that contains an Action with a non-empty configInfoElements collection is added to the diagram, the configInfoElements collection is not assigned in the ActionDomAdapter.
I added the following line to the end of the "if (action != null)" clause in ActionDomAdapter.initialize():
addElements(action.getConfigInfoElements());
.. and then things seems to work. I believe this is similar to for example how the events collection is currently initialized in DecisionDomAdapter.initialize(), while of course there may be side effects that I'm not aware of.
It would be great if a fix (possibly the one described above) can be included in GD 3.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 11 months
[JBoss JIRA] Created: (JBPORTAL-1294) JBP_CMS_WSP_PROP.PK unique contraint violated
by Ian White (JIRA)
JBP_CMS_WSP_PROP.PK unique contraint violated
---------------------------------------------
Key: JBPORTAL-1294
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1294
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.Alpha2
Environment: AS 4.0.5.GA
Oracle 9i
Reporter: Ian White
Assigned To: Roy Russo
Try to create a content item using the CMS Admin Portlet.
Get oracle sql exception - primary key unique contraint violated - JBP_CMS_SWP_PROP.PK:
16:32:14,171 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-80
16:32:14,328 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:9
16:32:14,343 INFO [JkMain] Jk running ID=0 time=0/78 config=null
16:32:14,359 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:12s:797ms
16:32:57,671 WARN [JDBCExceptionReporter] SQL Error: 1, SQLState: 23000
16:32:57,671 ERROR [JDBCExceptionReporter] ORA-00001: unique constraint (JBPORTAL26.SYS_C0032370) violated
16:32:57,671 WARN [JDBCExceptionReporter] SQL Error: 1, SQLState: 23000
16:32:57,671 ERROR [JDBCExceptionReporter] ORA-00001: unique constraint (JBPORTAL26.SYS_C0032370) violated
16:32:57,671 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:235)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:41)
at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.loadManagedNode(PortalCMSCacheLoader.java:757)
at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.saveWSPPropNodeEntry(PortalCMSCacheLoader.java:560)
at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.put(PortalCMSCacheLoader.java:305)
at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.put(PortalCMSCacheLoader.java:389)
at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.prepare(PortalCMSCacheLoader.java:479)
at org.jboss.cache.interceptors.CacheStoreInterceptor.prepareCacheLoader(CacheStoreInterceptor.java:296)
at org.jboss.cache.interceptors.CacheStoreInterceptor.invoke(CacheStoreInterceptor.java:130)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:804)
at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1069)
at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75)
at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1491)
at org.jboss.tm.TransactionImpl.beforePrepare(TransactionImpl.java:1110)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:324)
at org.jboss.tm.TxManager.commit(TxManager.java:240)
at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87)
at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 11 months
[JBoss JIRA] Created: (JBPORTAL-1325) ConsumerCacheInterceptor : should not use the cache just after login
by Antoine Herzog (JIRA)
ConsumerCacheInterceptor : should not use the cache just after login
--------------------------------------------------------------------
Key: JBPORTAL-1325
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1325
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Core
Environment: jbp 2.4.0
Reporter: Antoine Herzog
Assigned To: Julien Viet
Use case :
- user come to the site.
- Portlet show views for unchecked user. These views are put in the cache.
- user log in, let's say as admin
- the cached views still show the previous things, not taking into account the change of authorizations
- the user can't see the proper things
usual needs :
- for I18n portals : change of locale when user log in. all the portlets must do the change, not depending on cache
- for admin or special roles features in the portlet views
- for modes depending on roles (see forum post)
In the default portal, there are no use of cache. so all these use cases are fullfiled.
to reproduce the problem :
- put some cache on the user portlet (great feature for prod), the user portlet window may not update after logging.
resolution :
in the ConsumerCacheInterceptor
the CacheKey do not take into account the login state.
see : public CacheKey(StateString navigationalState, WindowState windowState, Mode mode)
so store the user name (or "unchecked") in the CacheEntry.
put the parameter "userOfFragment" in the CacheKey.
when retrieving the CacheEntry, compare the currentUser and the userOfFragment, and don't use the cache if different.
just to see : can we have access to the logued user in this interceptor ? (that, i don't know)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 11 months