Is this how the jetspeed useragent should be working? We have added several new rows to the CLIENT table. A row on the MEDIA_TYPE table has also been added for each row added on the CLIENT table. These rows are linked to a MIMETYPE, using the PREFERRED_MIMETYPE_ID column. The MIMETYPE is the linked to the MEDIA_TYPE table through the MEDIATYPE_TO_MIMETYPE table.
Should there be a MIMETYPE 1 -> 1 MEDIATYPE relationship or a MIMETYPE * -> 1 MEDIATYPE relationship. We discovered that a MIMETYPE * -> 1 MEDIATYPE relationship would produce inconsistent results it would simply result in the first MEDIATYPE being returned. Is there any kind of ordering system involved here We are not sure exactly how the CapabilityCustomizerValveImpl in Jetspeed 2.1.3 should be working. If all the mediatypes being returned are not passed to the constructor of the CapabilityCustomizerValveImpl valve, the default media type will be used. Can anyone shed any light on the above observations and say whether this is the correct method for this system to be used? -- View this message in context: http://www.nabble.com/Jetspeed-UserAgent-Switching-...-tp16700356p16700356.html Sent from the Jetspeed - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
