[JBoss JIRA] Closed: (JBCACHE-209) Expand the JBossCache tutorial page
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-209?page=all ]
Manik Surtani closed JBCACHE-209.
---------------------------------
Resolution: Done
> Expand the JBossCache tutorial page
> -----------------------------------
>
> Key: JBCACHE-209
> URL: http://jira.jboss.com/jira/browse/JBCACHE-209
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Manik Surtani
> Priority: Minor
> Fix For: 2.0.0.GA
>
>
> Currently our tutorial page is not up to date with the new features. For example, we should have a eviction tutorial.
> On the JbossCacheAop side, we need to have a tutorial that illustrate:
> 1. Example to illsutrate the POJO relationship management (person and object, for example)
> 2. Annotation based example tutorial
> 3. Interaction with CacheLoader (that also hightlight the perservation of relationship)
> 4. Illustrate the getObject during failover (from another node)
--
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
19 years, 3 months
[JBoss JIRA] Created: (JBMESSAGING-622) JBossMessage.setJMSReplyTo() method does not allow to set up nulls
by Ilya Bochkov (JIRA)
JBossMessage.setJMSReplyTo() method does not allow to set up nulls
------------------------------------------------------------------
Key: JBMESSAGING-622
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-622
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.0.1.GA
Reporter: Ilya Bochkov
Assigned To: Ovidiu Feodorov
The method body checks if a destination is an instance of JBossDestination. If you pass null then an exception is thrown, though null is a valid value.
public void setJMSReplyTo(Destination replyTo) throws JMSException
{
if (!(replyTo instanceof JBossDestination))
{
throw new InvalidDestinationException("Replyto cannot be foreign");
}
this.replyToDestination = (JBossDestination)replyTo;
}
I've changed the method definition to:
public void setJMSReplyTo(Destination replyTo) throws JMSException
{
if(replyTo == null){
this.replyToDestination = null;
return;
}
if (!(replyTo instanceof JBossDestination))
{
throw new InvalidDestinationException("Replyto cannot be foreign");
}
this.replyToDestination = (JBossDestination)replyTo;
}
Please, if this is a correct fix incorporate it in future releases.
Thanks!
--
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
19 years, 3 months
[JBoss JIRA] Commented: (JBPORTAL-455) Relax portlet security roles declaration
by Julien Viet (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-455?page=comments#action_12359572 ]
Julien Viet commented on JBPORTAL-455:
--------------------------------------
PortletRequestImpl.isUserInRole(String s)
it reads metadata and make the mapping.
with extended meta data telling that it should not map, it could be done here
> Relax portlet security roles declaration
> ----------------------------------------
>
> Key: JBPORTAL-455
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-455
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal Portlet
> Affects Versions: 2.0 Final
> Reporter: Julien Viet
>
> Today when a portlet uses the req.isUserInRole(String roleName), this role must be declared in the portlet.xml otherwise the method returns false.
> <portlet>
> ...
> <security-role-ref>
> <role-name>Admin</role-name>
> </security-role-ref>
> ...
> </portlet>
> This is what the portlet spec tells to do.
> But it could be possible to avoid this declaration and let all the role checks pass through and delegate the call to the servlet container when configuring jboss portal
> in a certain mode (at server level or webapp level)
--
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
19 years, 3 months