Confirmed: it is a problem related to how weblogic handles
authorization by default.
The solution is to add the stanza:
false
in the config.xml of the domain.
2012/8/2 helix84 :
> On Wed, Aug 1, 2012 at 1:26 PM, Domingo Iglesias wrote:
>> Thanks for the suggestion. I have checked web.xml and it
On Wed, Aug 1, 2012 at 1:26 PM, Domingo Iglesias wrote:
> Thanks for the suggestion. I have checked web.xml and it's correct.
I'm glad it worked.
> authenticating with BASIC 'weblogic'@dipositint9.ub.edu:8
Sorry, no idea. But this line looks wrong - 1) there are apotrophes
around "weblogic" and
Hi
Thanks for the suggestion. I have checked web.xml and it's correct.
Using the "sword client" and activating the debug, it seems that the
problem could be linked more with how weblogic handles basic http
authorization than with the sword server.
DEBUG [org.purl.sword.client.GuiClient] the prox
Sounds like exactly what I would do.
I think I know what the problem might be. ConfigurationManager uses a
different method of determining the modules directory - it's based on
dspace.dir, not on location of dspace.cfg, look here:
https://github.com/DSpace/DSpace/blob/dspace-1_8_x/dspace-api/src/m
Hi Ivan,
thanks for your response.
I have followed Stuart's solution in the previous versions, and I am
trying to implement it in 1.8.2 version of dspace as you propose.
I have "cloned" all the [dpace.dir], so I have: ./dspace and ./dspace_sword
In ./dspace_sword there are symlinks to all the ./
Hi Domingo,
this post from Stuart describes the approach or separate configuration
file for the sword webapp:
http://dspace.2283337.n4.nabble.com/Dspace-tech-Shibboleth-Sword-problem-td3286764.html
Maybe it will help or it just describes what you already tried. You
should describe the details of
Hi all,
thanks Stuart for the reply.
You are right. The problem is solved changing the load order of the
libraries.
Oracle Application Server users can find more information at:
http://download.oracle.com/docs/cd/B31017_01/web.1013/b28952/classload.htm#CIHFJEEF
Regards!
2010/4/15 Stuart Lewis
Hi Domingo,
> Caused by: org.jdom.JDOMException:
> http://apache.org/xml/features/validation/schema feature not recognized for
> SAX driver oracle.xml.parser.v2.SAXParser
>
> I suspect the error is related with the oracle parser since we are running
> dspace in a OC4J hosted on an OAS 10.1.3,
8 matches
Mail list logo
