Its actually non-trivial to derive that from anything but runtime data. The ServletContext does not appear to expose that (even in Java EE5) though the ContextPath is available at the ServletContext level. Even at run-time, for the request, its probably based on the Host header sent
Do you know of another way? Cheers, Scott On Mon, Jun 29, 2009 at 1:38 PM, Marvin Addison <marvin.addi...@gmail.com>wrote: > > Assuming then that we use a standard convention for the URL endpoints > > for the various profiles, that leave's the following to be configured: > > * Entity ID > > InCommon just released the following notice about EntityID, > > https://spaces.internet2.edu/display/InCCollaborate/IdP+entityID+Shift+to+URLs+--+FAQ > , > where they recommended basing it on IDP URL. In the case of CAS, this > could reasonably be the CAS root URL, e.g. > https://www.example.com/cas, which I would imagine you could derive > from other configuration data. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
