"walfreund" wrote : 
  | thanks for your reply! I totally agree on your remarks about the WSRP 
specification and it definitely makes no sense at all to tweak the 
implementation of the JBoss Portal producer BUT on connecting the same SAP EP 
to an open Oracle WSRP test portal 
(http://portalstandards.oracle.com/portletapp/portlets?WSDL) the 
mispelled/malformed "consumer agent" string poses no threat to anyone and i can 
consume portlets, clap my hands and say "yeah!".
  | 

+1 for the musical reference! :)

"walfreund" wrote : 
  | That seems strange to me and makes me question all these 
standard-conforming marketing phrases around the world.
  | 

It is actually not that strange. I have seen enough such cases with the 
consumer agent not being specification-compliant that I have been tempted to 
remove the validation several times just so that it is easier for our users. 
I have several options:
1. Keep a hard line as far as the specification goes. That makes us look like 
the bad guy as several producers are less strict and so will accept a 
non-conformant consumer agent (I know of at least 2 "big name" WSRP consumers 
that do not generate valid consumer agents). The only recourse then is to have 
our users who wish to use these WSRP consumers to contact their support and 
file for a bug... but we all know that with big, commercial products you might 
not see a fix before a while.

2. Introduce a configuration option to enable/disable consumer agent validation 
but that makes our code more complex (and using our producer more complex as 
well) for something that shouldn't even happen if the specification had a TCK.

3. Remove the consumer agent validation altogether because it seems that no one 
really cares about its format and the specification does not seem to leverage 
that specific format anywhere else either (i.e. the MUST in the specification 
might be too strong of a language since there doesn't seem to be a real value 
in providing a consumer agent formatted that way).

The bigger issue here is the lack of TCK with the specification. 
Interoperability and, ultimately, users suffer from this situation... :(

"walfreund" wrote : 
  | however, I really like JBoss portal and gonna get it running. Word!
  | 

Thank you for not giving up on Portal when it would have been easy to do so 
because we are actually more compliant (on this particular aspect, as we don't 
claim perfection ^_^) than some of our competitors! :)

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137793#4137793

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137793
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to