[
https://jira.duraspace.org/browse/DS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Dietz updated DS-841:
---------------------------
Affects Version/s: 1.7.0
Hardy additionally says: DS-841, which is another Oracle bug with DSpace 1.7.x
and Trunk--you can't edit or add ePeople in XMLUI if you're using Oracle.
> 'IllegalArgumentException: No such column rnum' error in DSpace 1.7.x XMLUI
> admin eperson (with Oracle backend)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DS-841
> URL: https://jira.duraspace.org/browse/DS-841
> Project: DSpace
> Issue Type: Bug
> Affects Versions: 1.7.0, 1.7.1
> Environment: RHEL5, with Oracle on the back end
> Reporter: Hardy Pottinger
> Attachments: DS-841-fix-Oracle-compatibility-for-ePerson.patch
>
>
> In using the 1.7.x branch for testing with Oracle. Everything installed fine,
> and I've got a bare-bones repository up and running. However, in the XMLUI,
> when I click on the admin ePeople link, I get the following error:
> java.lang.IllegalArgumentException: No such column rnum
> Here are the first few lines of the stack trace:
> java.lang.IllegalArgumentException: No such column rnum
> at
> org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:581)
> at org.dspace.storage.rdbms.TableRow.setColumn(TableRow.java:433)
> at
> org.dspace.storage.rdbms.DatabaseManager.process(DatabaseManager.java:1111)
> at
> org.dspace.storage.rdbms.TableRowIterator.next(TableRowIterator.java:151)
> at
> org.dspace.storage.rdbms.TableRowIterator.toList(TableRowIterator.java:204)
> at org.dspace.eperson.EPerson.search(EPerson.java:358)
> at
> org.dspace.app.xmlui.aspect.administrative.eperson.ManageEPeopleMain.addBody(ManageEPeopleMain.java:121)
> at
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:223)
> at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at $Proxy66.startElement(Unknown Source)
> at
> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
> at
> org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
> at
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:240)
> at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
> at $Proxy49.startElement(Unknown Source)
> No such error is thrown when using the JSPUI.
> > org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:581
> Looking more closely at the stack trace, the problem appears to be that the
> canonicalizeAndCheck method in TableRow is failing when it attempts to verify
> the rnum column, which is created back in org.dspace.eperson.EPerson.search.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and publish
your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
