[Building Sakai] Having multiple "direct" servlets?

[Maurer, Christopher Wayne]

Hmm, this might have been a false alarm.  I don't get that issue now.  Wonder how I got into that situation before?  If I can find a way to reproduce the problem, I'll file a jira.

Chris

From: Chris Maurer <chmaurer at iupui.edu<mailto:chmaurer at iupui.edu>>
Date: Thu, 7 Jul 2011 17:46:35 +0000
To: Sakai Dev <sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>>
Subject: [Building Sakai] Having multiple "direct" servlets?

With the work IU was doing for building out EB providers, we had created a "new" direct servlet called oauthdirect.  At one point we had just modified the direct servlet, but since the oauth stuff we were adding was placing restrictions on URL paths, we didn't want to adversely affect anything that was already using direct urls.  But, what seems to be happening is that the new oauthdirect seems to be overtaking the regular direct servlet.  If I go to /direct/describe, all the links on that page are written with /oauthdirect.  My guess is that I can only have one direct servlet…is that likely the case here?

Chris
_______________________________________________ sakai-dev mailing list sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110707/1c18d4b1/attachment.html