It should be fixed in subversion. Please let me know how it goes.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163086#4163086
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163086
Chris, I just did an update (it's been a while), could you provide a diff of
what happened, or let me know the revision?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163097#4163097
Reply to the post :
Revision 11352.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163101#4163101
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163101
___
jboss-user mailing list
Initial looks are good
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163161#4163161
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163161
___
jboss-user mailing list
Found the problem, but I'm really not sure of good solution :)
Because we're using the relaxed checking it tries to do a substitution on a
null string. We figure out the capabilities (which handles the markupTypes)
before we do the MetaInfo and PortletInfo so we could use the first locale in
Yes. Looks like invalid XML... According to the XML spec:
http://www.w3.org/TR/REC-xml/#sec-lang-tag[/url], xml:lang attributes should
conform to [url]http://www.ietf.org/rfc/rfc3066.txt... lang attribute on
LocalizedString is defined by WSRP as an xml:lang attribute.
Looking at the service
