September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1016) Allow creation and deployment of WSRP portlets from descriptors

by Chris Laprun (JIRA)

Allow creation and deployment of WSRP portlets from descriptors --------------------------------------------------------------- Key: JBPORTAL-1016 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1016 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.4.1 Final Right now, the only way to deploy WSRP portlets is via the management portlet. We should be able to do this via the descriptors. Proposed solution is to evolve the -wsrp.xml file to accomodate portlet definition. -- 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

14 years

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2009) error while creating portlet instance from remote producer

by Prabhat Jha (JIRA)

error while creating portlet instance from remote producer ---------------------------------------------------------- Key: JBPORTAL-2009 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2009 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Reporter: Prabhat Jha Assigned To: Chris Laprun 1. Create a consumer using bea's WSDL 2. Register as "public" 3. Go to porltet definitions and select bea as provider. 4. Try to create an instance of Hello World Server log says: Caused by: org.jboss.portal.portlet.InvokerUnavailableException: Couldn't update ProducerInfo for Consumer 'bea' at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsumerImpl.java:156) at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerService.getPortlets(FederatedPortletInvokerService.java:90) at org.jboss.portal.core.management.PortletDiscoveryService.processPortletDiscovery(PortletDiscoveryService.java:88) at sun.reflect.GeneratedMethodAccessor526.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) ... 20 more Caused by: org.hibernate.HibernateException: Illegal attempt to associate a collection with two open sessions at org.hibernate.collection.AbstractPersistentCollection.setCurrentSession(AbstractPersistentCollection.java:410) at org.hibernate.event.def.OnUpdateVisitor.processCollection(OnUpdateVisitor.java:43) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:101) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:61) at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:55) at org.hibernate.event.def.AbstractVisitor.process(AbstractVisitor.java:123) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:293) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:223) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:89) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:507) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:499) at org.hibernate.engine.CascadingAction$1.cascade(CascadingAction.java:218) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.engine.Cascade.cascade(Cascade.java:97) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.cascadeOnUpdate(DefaultSaveOrUpdateEventListener.java:357) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:329) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:223) at org.hibernate.event.def.DefaultUpdateEventListener.performSaveOrUpdate(DefaultUpdateEventListener.java:33) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireUpdate(SessionImpl.java:564) at org.hibernate.impl.SessionImpl.update(SessionImpl.java:552) at org.hibernate.impl.SessionImpl.update(SessionImpl.java:544) at org.jboss.portal.wsrp.consumer.ConsumerRegistryService.org$jboss$portal$wsrp$consumer$ConsumerRegistryService$updateProducerInfo$aop(ConsumerRegistryService.java:246) at org.jboss.portal.wsrp.consumer.ConsumerRegistryService$updateProducerInfo_N3464050590403709888.invokeNext(ConsumerRegistryService$updateProducerInfo_N3464050590403709888.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.wsrp.consumer.ConsumerRegistryService$updateProducerInfo_N3464050590403709888.invokeNext(ConsumerRegistryService$updateProducerInfo_N3464050590403709888.java) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.portal.wsrp.consumer.ConsumerRegistryService$updateProducerInfo_N3464050590403709888.invokeNext(ConsumerRegistryService$updateProducerInfo_N3464050590403709888.java) at org.jboss.portal.wsrp.consumer.ConsumerRegistryService.updateProducerInfo(ConsumerRegistryService.java) at org.jboss.portal.wsrp.consumer.ProducerInfo.internalRefresh(ProducerInfo.java:316) at org.jboss.portal.wsrp.consumer.ProducerInfo.detailedRefresh(ProducerInfo.java:273) at org.jboss.portal.wsrp.consumer.ProducerInfo.refresh(ProducerInfo.java:268) at org.jboss.portal.wsrp.consumer.ProducerInfo.getPortletMap(ProducerInfo.java:608) at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsumerImpl.java:151) -- 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

14 years

3
14
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1251) Tie clones to registration context

by Chris Laprun (JIRA)

Tie clones to registration context ---------------------------------- Key: JBPORTAL-1251 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1251 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Beta1 -- 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

14 years

2
11
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2299) WSRP producer vs. consumer web page design inconsistency

by Viliam Rockai (JIRA)

WSRP producer vs. consumer web page design inconsistency -------------------------------------------------------- Key: JBPORTAL-2299 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2299 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.1 Final Environment: lenovo t61, java 1.5 Reporter: Viliam Rockai Assignee: Chris Laprun Priority: Minor only a small cosmetic issue - inconsistency in design between WSRP consumers and producer page. they differ in the header "style", you can see that at attached pictures. I understand that producers doesn't have subpages, but anyway I think, that the whole page would look more "consistent" if producers had their own header "Producer" like consumers have. -- 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

14 years

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1252) Add releaseSessions support on Consumer

by Chris Laprun (JIRA)

Add releaseSessions support on Consumer --------------------------------------- Key: JBPORTAL-1252 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1252 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Beta1 -- 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

14 years

2
10
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2338) NullPointerException in PortletManagementHandler.getPortletProperties

by Lionel ROSIER (JIRA)

NullPointerException in PortletManagementHandler.getPortletProperties --------------------------------------------------------------------- Key: JBPORTAL-2338 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2338 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.7 Final Environment: Tested on JBoss AS 4.2.3 and Portal 2.6.6 Reporter: Lionel ROSIER Assignee: Chris Laprun It's possible to create new properties with "InstanceDefinition.setProperties" on remote portlet with WSRP but when we try to read these new properties, we have a NPE in getPortletProperties from PortletManagementHandler. -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2071) Investigate non-isolation of WSRP tests

by Chris Laprun (JIRA)

Investigate non-isolation of WSRP tests --------------------------------------- Key: JBPORTAL-2071 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2071 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 Alpha1 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.7.0 Beta1 It seems that test set up is not done in complete isolation of the environment. I have lost a day trying to figure out what changed in my code that was causing tests to fail with an NPE related to a null registration policy when it seems that the issue came from the database state of the AS instance... :( Need to find exactly what is causing the problem (seems like RegistrationManager might be the culprit) and use a properly isolated test set up. -- 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

14 years

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2101) Remove reference to jboss-ejb3-metadata-deployers from bom-eap5.

by Carlo de Wolf (JIRA)

Remove reference to jboss-ejb3-metadata-deployers from bom-eap5. ---------------------------------------------------------------- Key: EJBTHREE-2101 URL: https://jira.jboss.org/browse/EJBTHREE-2101 Project: EJB 3.0 Issue Type: Task Components: bom Affects Versions: bom-eap5-0.1.2 Reporter: Carlo de Wolf Fix For: bom-eap5-0.1.3 jboss-ejb3-metadata-deployers is an AS 6 artifact and not used in EAP 5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2052) Use an L1 Cache for SFSB context stored in a DIST mode Infinispan

by Brian Stansberry (JIRA)

Use an L1 Cache for SFSB context stored in a DIST mode Infinispan ----------------------------------------------------------------- Key: EJBTHREE-2052 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2052 Project: EJB 3.0 Issue Type: Sub-task Components: cache, Clustering Reporter: Brian Stansberry With Infinispan DIST, an SFSB context may not be stored in Infinispan on the local node. (Even if it's originally stored locally, it may move due to a rehash following a topology change). Keep an L1 cache on the node that's servicing the session to improve read performance. The session ownership system discussed in EJBTHREE-2051 can be used to detect failover and the need to invalidate the session out of L1. The locking system should return whether the call required obtaining the lock from a remote node; if yes that implies failover and an invalid L1. -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2049) Create an Infinispan-backed SFSB cache

by Brian Stansberry (JIRA)

Create an Infinispan-backed SFSB cache -------------------------------------- Key: EJBTHREE-2049 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2049 Project: EJB 3.0 Issue Type: Task Components: cache, Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Infinispan is replacing JBC in the AS; need a Cache impl that integrates with Infinispan. -- 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

14 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010