[JBoss JIRA] Created: (JBREM-1014) Support injection of socket factory class name into AbstractInvoker
by Ron Sigal (JIRA)
Support injection of socket factory class name into AbstractInvoker
-------------------------------------------------------------------
Key: JBREM-1014
URL: https://jira.jboss.org/jira/browse/JBREM-1014
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.2.SP8
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP9
It is intended that org.jboss.remoting.AbstractInvoker can accept the class name of a SocketFactory, using the parameter org.jboss.remoting.Remoting.SOCKET_FACTORY_NAME (actual value "socketFactory"). Unfortunately, the parameter name "socketFactory" conflicts with the bean property of the same name. In particular, the problem is that the method
public void setSocketFactory(SocketFactory socketFactory)
in AbstractInvoker expects a SocketFactory instead of a String.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBPORTAL-2089) NPE with deleting a file in pending stage
by Prabhat Jha (JIRA)
NPE with deleting a file in pending stage
-----------------------------------------
Key: JBPORTAL-2089
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2089
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.6 Final
Reporter: Prabhat Jha
Assignee: Sohil Shah
Fix For: 2.6.6 Final
- Create a file.
- Keep it in pending state
- Select pending items from drop down menu
- Click on the the file you just created
- Select Delete file from drop down and confirm deletion
- Select pending items from drop down and hit approve. You will get NPE which is expected. Once file is deleted, it should not be in any list.
java.lang.NullPointerException
at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.internalDoView(CMSAdminPortlet.java:341)
at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.doView(CMSAdminPortlet.java:184)
at org.jboss.portlet.JBossPortlet.doDispatch(JBossPortlet.java:257)
at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:244)
at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:390)
at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeRender(PortletContainerImpl.java:483)
at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:405)
at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:86)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:106)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.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.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.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.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeRequired(TransactionInterceptor.java)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:72)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:50)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(ProducerCacheInterceptor.java:58)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.portlet.AjaxInterceptor.invoke(AjaxInterceptor
--
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
16 years, 2 months
[JBoss JIRA] Created: (JGRP-742) UNICAST connection trashing during merge
by Vladimir Blagojevic (JIRA)
UNICAST connection trashing during merge
----------------------------------------
Key: JGRP-742
URL: http://jira.jboss.com/jira/browse/JGRP-742
Project: JGroups
Issue Type: Bug
Reporter: Vladimir Blagojevic
Assigned To: Vladimir Blagojevic
Fix For: 2.6.3
JGRP-348 describes an edge case that causes interruption of unicast communication between two separate unmerged JGroups network islands. However, a fix for JGRP-348 introduced even a bigger edge case of the same problem described in JGRP-659.
For 2.6.3 release we will revert changes made in JGRP-348. To handle an edge case described in JGRP-348 we recommend use of FD_ALL failure detection protocol. JGRP-659 will be solved properly in 2.7 to handle both edge cases out of the box.
--
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
16 years, 2 months
[JBoss JIRA] Created: (JBPORTAL-2091) some CMS default behavior may need to change
by Prabhat Jha (JIRA)
some CMS default behavior may need to change
--------------------------------------------
Key: JBPORTAL-2091
URL: https://jira.jboss.org/jira/browse/JBPORTAL-2091
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.6 Final
Reporter: Prabhat Jha
Assignee: Sohil Shah
These are working as designed but I think this may need to change.
i. When you edit a txt/html file using WYSIWYG editor and approve it, version number is incremented by 2 (1.0, 1.2, 1.4). It may make a user wonder what happenned to 1.1 and 1.3..probably got deleted.
ii.After modifcation, created date and modified date both have same value. I think one should suffice if we keep both value same.
May be this needs to be discussed in forum.
--
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
16 years, 2 months