Skip to Content.
Sympa Menu

shibboleth-dev - Re: More defined custom extensions mechanism

Subject: Shibboleth Developers

List archive

Re: More defined custom extensions mechanism


Chronological Thread 
  • From: Tom Scavo <>
  • To: Scott Cantor <>
  • Cc: Chad La Joie <>, Walter Hoehn <>, Shibboleth Developers <>, Von Welch <>
  • Subject: Re: More defined custom extensions mechanism
  • Date: Wed, 6 Jul 2005 17:09:21 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d3uRxm+/PpYBjhc8QOSw5HmKu1dYcRRM6s9I1l3irmZ3IOow+d8RhoAzxoO60epn83ULYd5OalZvKHtG4+X/DZqugJkpxgjAhrFopAOE71E6a+FXv77uunTMrh9O9Z+mtgu2KXzwEjqO8bVn3rDx5nhzuJWzmHZKl8Us2NAZw9A=
On 7/6/05, Scott Cantor
<>
wrote:
>
> > This is where I'm stuck. How do the modified files in $IDP_HOME$ get
> > into the tomcat webapp directory? I was thinking there would be a
> > tool that copied the files from $IDP_HOME$ to the webapp directory,
> > but from your comments, it sounds like you have a different idea.
>
> No, nothing ever gets copied *from* IDP_HOME. Those are the authority
> copies. Referencing things inside the war is the old way of doing things
> that nobody would use in production, it's too confusing. That's why we
> created this new IDP_HOME tree.

So the plugin is reading directly from $IDP_HOME$?

Thanks,
Tom

Archive powered by MHonArc 2.6.16.

Top of Page