Mark, the dspace/pom.xml is the only place that the jscosign is listed, and it
seems like it would hold for all the apps.
Take a look.
From: Mark Diggory [mailto:[email protected]]
Sent: Friday, June 24, 2011 1:48 AM
To: Blanco, Jose
Cc: [email protected]
Subject: Re: [Dspace-tech] adding cosing to manakin
Yes, you need to look for the dependency for cosign in your jspui pom.xml and
add it to your xmlui pom.xml
Best,
Mark
On Thu, Jun 23, 2011 at 12:00 PM, Blanco, Jose
<[email protected]<mailto:[email protected]>> wrote:
I have cosign running in my jspui, and I'm trying to run it now in xmlui, so I
added the following to the xmui web.xml file:
<filter>
<filter-name>Cosign Authentication Filter</filter-name>
<filter-class>edu.umich.auth.cosign.CosignAuthenticationFilterIII</filter-class>
<init-param>
<param-name>Cosign.ConfigurationFile</param-name>
<param-value>/l1/dspace/repository/dev/config/cosignConfigBlancoj.xml</param-value>
</init-param>
<init-param>
<param-name>Auth.JAASConfigurationFile</param-name>
<param-value>/l/local/apache-tomcat/conf/jaas.conf</param-value>
</init-param>
</filter>
<servlet-mapping>
<servlet-name>webiso-login</servlet-name>
<url-pattern>/webiso-login</url-pattern>
</servlet-mapping>
<filter-mapping>
<filter-name>Cosign Authentication Filter</filter-name>
<url-pattern>/webiso-login</url-pattern>
</filter-mapping>
And I'm getting this error:
SEVERE: Parse error in application web.xml file at
jndi:/blancoj.dev.deepblue.lib.umich.edu/WEB-INF/web.xml<http://blancoj.dev.deepblue.lib.umich.edu/WEB-INF/web.xml>
java.lang.IllegalArgumentException: Filter mapping specifies an unknown filter
name Cosign Authentication Filter
at
org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2726)
at
org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2752)
at
org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1061)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2938)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
===
I don't kwow why it can't find it. It finds it just fine in jspui. Do I need
to change something in one of the pom.xml files?
-Jose
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
--
Mark R. Diggory
@mire - www.atmire.com<http://www.atmire.com/>
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Esperantolaan 4 - Heverlee 3001 - Belgium
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
<modelVersion>4.0.0</modelVersion>
<groupId>org.dspace</groupId>
<artifactId>dspace</artifactId>
<name>DSpace Assembly and Configuration</name>
<packaging>pom</packaging>
<description>
The DSpace Project provides all the functionality required to
build, install and upgrade and dspace instance.
</description>
<url>http://projects.dspace.org/dspace</url>
<!--
A Parent POM that Maven inherits DSpace Default
POM atrributes from.
-->
<parent>
<groupId>org.dspace</groupId>
<artifactId>dspace-parent</artifactId>
<version>1.7.0</version>
</parent>
<!--
The Subversion repository location is used by Continuum to update against
when changes have occured, this spawns a new build cycle and releases snapshots
into the snapshot repository below.
-->
<scm>
<connection>scm:svn:http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.7.0/dspace</connection>
<developerConnection>scm:svn:https://scm.dspace.org/svn/repo/dspace/tags/dspace-1.7.0/dspace</developerConnection>
<url>http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.7.0/dspace</url>
</scm>
<profiles>
<!--
This profile is used by all children such that
when activated a dspace.config configuration
file location passed on the commandline
(-Ddspace.config=...) can be passed through
to be used as a filter source by projects for
tasks such as updating the ${dspace.dir} in
web.xml etc.
When activated, the child project will inherit
the configuration.
-->
<profile>
<activation>
<property>
<name>dspace.config</name>
</property>
</activation>
<build>
<filters>
<filter>${dspace.config}</filter>
</filters>
</build>
</profile>
<!--
These profiles activate the inclusion of various modules into
the DSpace Build process. They activate automatically if the
source module is in the local file system, correctly located
relative to this file.
-->
<!--
Builds central API for DSpace
-->
<profile>
<id>dspace-api</id>
<activation>
<file>
<exists>../dspace-api/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-api</module>
</modules>
</profile>
<!--
Builds DSpace Solr Stats for DSpace
-->
<profile>
<id>dspace-stats</id>
<activation>
<file>
<exists>../dspace-stats/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-stats</module>
</modules>
</profile>
<!--
Builds DSpace discovery for DSpace
-->
<profile>
<id>dspace-discovery</id>
<activation>
<file>
<exists>../dspace-discovery/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-discovery</module>
</modules>
</profile>
<!--
Builds OAI Gateway WAR for DSpace
-->
<profile>
<id>dspace-oai-api</id>
<activation>
<file>
<exists>../dspace-oai-api/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-oai-api</module>
</modules>
</profile>
<!--
Builds OAI Gateway WAR for DSpace
-->
<profile>
<id>dspace-oai-webapp</id>
<activation>
<file>
<exists>../dspace-oai-webapp/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-oai-webapp</module>
</modules>
</profile>
<!--
Builds OAI Gateway WAR for DSpace
-->
<profile>
<id>dspace-oai</id>
<activation>
<file>
<exists>../dspace-oai/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-oai</module>
</modules>
</profile>
<!--
Builds JSPUI WAR for DSpace
-->
<profile>
<id>dspace-jspui-api</id>
<activation>
<file>
<exists>../dspace-jspui-api/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-jspui-api</module>
</modules>
</profile>
<!--
Builds JSPUI WAR for DSpace
-->
<profile>
<id>dspace-jspui-webapp</id>
<activation>
<file>
<exists>../dspace-jspui-webapp/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-jspui-webapp</module>
</modules>
</profile>
<!--
Builds JSPUI WAR for DSpace
-->
<profile>
<id>dspace-jspui</id>
<activation>
<file>
<exists>../dspace-jspui/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-jspui</module>
</modules>
</profile>
<!--
Builds SWORD WAR for DSpace
-->
<profile>
<id>dspace-sword-api</id>
<activation>
<file>
<exists>../dspace-sword-api/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-sword-api</module>
</modules>
</profile>
<!--
Builds SWORD WAR for DSpace
-->
<profile>
<id>dspace-sword-webapp</id>
<activation>
<file>
<exists>../dspace-sword-webapp/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-sword-webapp</module>
</modules>
</profile>
<!--
Builds SWORD WAR for DSpace
-->
<profile>
<id>dspace-sword</id>
<activation>
<file>
<exists>../dspace-sword/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-sword</module>
</modules>
</profile>
<!--
Builds each separate XMLUI module for the XMLUI war (for development/Eclipse)
-->
<profile>
<id>dspace-xmlui-api</id>
<activation>
<file>
<exists>../dspace-xmlui-api/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-xmlui-api</module>
</modules>
</profile>
<profile>
<id>dspace-xmlui-wing</id>
<activation>
<file>
<exists>../dspace-xmlui-wing/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-xmlui-wing</module>
</modules>
</profile>
<profile>
<id>dspace-xmlui-webapp</id>
<activation>
<file>
<exists>../dspace-xmlui-webapp/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-xmlui-webapp</module>
</modules>
</profile>
<profile>
<id>dspace-xmlui-lang</id>
<activation>
<file>
<exists>../dspace-xmlui-lang/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-xmlui-lang</module>
</modules>
</profile>
<!--
Builds XMLUI WAR for DSpace
-->
<profile>
<id>dspace-xmlui</id>
<activation>
<file>
<exists>../dspace-xmlui/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-xmlui</module>
</modules>
</profile>
<!--
Builds each separate LNI module for the LNI war (for development/Eclipse)
-->
<profile>
<id>dspace-lni-core</id>
<activation>
<file>
<exists>../dspace-lni-core/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-lni-core</module>
</modules>
</profile>
<profile>
<id>dspace-lni-webapp</id>
<activation>
<file>
<exists>../dspace-lni-webapp/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-lni-webapp</module>
</modules>
</profile>
<profile>
<id>dspace-lni-client</id>
<activation>
<file>
<exists>../dspace-lni-client/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-lni-client</module>
</modules>
</profile>
<!--
Builds LNI WAR for DSpace
-->
<profile>
<id>dspace-lni</id>
<activation>
<file>
<exists>../dspace-lni/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-lni</module>
</modules>
</profile>
<!--
Builds Language Packs for DSpace
-->
<profile>
<id>dspace-api-lang</id>
<activation>
<file>
<exists>../dspace-api-lang/pom.xml</exists>
</file>
</activation>
<modules>
<module>../dspace-api-lang</module>
</modules>
</profile>
<!--
These profiles setup properties and build configuration
appropriate to the database that DSpace will be installed
against.
They are activated by using the profile id - ie. -Ppostgres,
or defining db.name - ie. -Ddb.name=oracle
-->
<!--
Default profile for Postgres database configuration
Use -Ppostgres to activate.
-->
<profile>
<id>postgres</id>
<activation>
<property>
<name>!db.name</name>
</property>
</activation>
<properties>
<default.db.name>postgres</default.db.name>
<default.db.driver>org.postgresql.Driver</default.db.driver>
<default.db.url>
jdbc:postgresql://localhost:5432/dspace
</default.db.url>
<default.db.username>dspace</default.db.username>
<default.db.password>dspace</default.db.password>
</properties>
</profile>
<profile>
<id>postgres-support</id>
<activation>
<property>
<name>!db.name</name>
</property>
</activation>
<dependencies>
<dependency>
<groupId>postgresql</groupId>
<artifactId>postgresql</artifactId>
</dependency>
</dependencies>
</profile>
<!--
Default profile for Oracle database configuration
Use -Poracle or -Ddb.name=oracle to activate.
-->
<profile>
<id>oracle</id>
<activation>
<property>
<name>db.name</name>
<value>oracle</value>
</property>
</activation>
<properties>
<default.db.name>oracle</default.db.name>
<default.db.driver>
oracle.jdbc.OracleDriver
</default.db.driver>
<default.db.url>
jdbc:oracle:thin:@//localhost:1521/xe
</default.db.url>
<default.db.username>dspace</default.db.username>
<default.db.password>dspace</default.db.password>
</properties>
</profile>
<profile>
<id>oracle-support</id>
<activation>
<property>
<name>db.name</name>
<value>oracle</value>
</property>
</activation>
<dependencies>
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc6</artifactId>
</dependency>
</dependencies>
</profile>
<!--
Using xpdf filters requires the inclusion
Of Sun dependencies these are not redistributable
and you will need to install them locally in your
maven repository prior to building your dspace instance
-->
<profile>
<id>xpdf-mediafilter-support</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>com.sun.media</groupId>
<artifactId>jai_imageio</artifactId>
<version>1.0_01</version>
</dependency>
<dependency>
<groupId>javax.media</groupId>
<artifactId>jai_core</artifactId>
<version>1.1.2_01</version>
</dependency>
</dependencies>
</profile>
</profiles>
<!--
Builds Overlay Modules for DSpace
-->
<modules>
<module>modules</module>
</modules>
<build>
<plugins>
<!-- overall project assembly -->
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-1</version>
<configuration>
<descriptors>
<descriptor>src/assemble/assembly.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>directory-single</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-api</artifactId>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-api-lang</artifactId>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-services-impl</artifactId>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-services-utils</artifactId>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-stats</artifactId>
</dependency>
<dependency>
<groupId>org.dspace</groupId>
<artifactId>dspace-discovery-provider</artifactId>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
</dependency>
<dependency>
<artifactId>jcosign</artifactId>
<groupId>edu.umich.auth.cosign</groupId>
<version>3.0</version>
</dependency>
</dependencies>
</project>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
