portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian McCallister <mccallis...@forthillcompany.com>
Subject Re: [jira] Commented: (JS2-47) OJB problems: Failure to run RoleSecurityTest Portlet
Date Wed, 09 Jun 2004 00:10:46 GMT
Happy to help, just never got any detailed information on how to  
replicate the issues.

Will look into this bug and see if I can find OJB issues.


On May 23, 2004, at 1:48 PM, jira@apache.org wrote:

> The following comment has been added to this issue:
>      Author: Scott T Weaver
>     Created: Sun, 23 May 2004 10:46 AM
>        Body:
> Great job, Ate!  OJB still remains the largest thorn in our side :(   
> We were supposed to have been getting a little "extra love" from the  
> OJB guys, but it looks like that was just wishful thinking.
> With each RC of OJB (some) old issues get resolved and new ones arise,  
> and it is way past the "getting old" stage.  I still think we should  
> continue to evaluate other options, most specifically Hibernate, for  
> future implenetations of the PersistenceStore api.
> ---------------------------------------------------------------------
> View this comment:
> http://issues.apache.org/jira/browse/JS2-47?page=comments#action_35688
> ---------------------------------------------------------------------
> View the issue:
>   http://issues.apache.org/jira/browse/JS2-47
> Here is an overview of the issue:
> ---------------------------------------------------------------------
>         Key: JS2-47
>     Summary: OJB problems: Failure to run RoleSecurityTest Portlet
>        Type: Bug
>      Status: Closed
>    Priority: Blocker
>  Resolution: FIXED
>     Project: Jetspeed 2
>    Fix Fors:
>              2.0-a1
>    Versions:
>              2.0-a1
>    Assignee: David Le Strat
>    Reporter: Ate Douma
>     Created: Sat, 22 May 2004 10:16 AM
>     Updated: Sun, 23 May 2004 10:46 AM
> Environment: Windows XP SP1, Tomcat 4.1.29, J2SE 1.4.2_03
> Description:
> The latest changes in cvs have broken the RoleSecurityTest portlet. It  
> seems that most these problems are caused by the upgrade to  
> OJB-1.0-rc6.
> On the mailing list there is a thread going on about this:
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=jetspeed- 
> dev@jakarta.apache.org&msgNo=14500
> I've looked into this and created a multi-file patch to solve a few of  
> the problems which I will attach it to this issue.
> By removing the proxy="dynamic" for SecurityRoleRefImpl and  
> SecurityRoleImpl I got rid of the RowReader exception as predicted by  
> Scott. Although this is a quick fix I certainly don't like it we need  
> to fall back to this to be able to use OJB.
> Certainly these classloader problems MUST be resolved I think to be  
> able to rely on OJB in the future.
> Then I fixed a NPE in ServletRequestImpl where the size of a returned  
> USER_INFO map is logged. If its null that leads of course to a NPE.
> Finally, I modified the demo security/roles.jsp to only display the  
> USER_INFO when a user is logged on (no use testing this for a  
> non-logged on user as it MUST be null in that case).
> Although the class not found error on o.a.j.prefs.om.impl.NodeImpl is  
> still thrown and displayed (only) in the console the page now is  
> rendered without a problem. Seems the exception is suppressed  
> somewhere in the code or just not communicated back into the  
> application?
> For these three changes, and the modifications I made to the  
> .classpath to get Eclipse building again, I created a multi-file  
> patch.
> I did send a message to the list with the Eclipse .classpath patch  
> earlier but for some reason I haven't received it back (yet).  
> Something wrong with the list or yaybe I'm not allowed to attach a  
> patch file?
> Well, here is the reason for the .classpath fix:
> The .classpath problems are related to multiple log4j.properties and  
> Log4j.properties files causing Eclipse having a conflict which file to  
> copy to its bin folder and also a conflict with the mixed case of  
> these files. I resolved this by setting an exclusion filter on all  
> log4j.properties.
> I will continue looking into the NodeImpl class not found exception...
> ---------------------------------------------------------------------
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message