Displaying this new user also doesn't work: http://esmecloudserverapache.dickhirsch.staxapps.net/user/https%3A%2F%2Fme.yahoo.co.jp%2Fa%2Flonvldtve_oheols4cy4fzjc1jq-%23bef9c
Maybe, it is related to the long username for users being created via openid On Wed, Mar 3, 2010 at 9:06 AM, Richard Hirsch <[email protected]> wrote: > On Wed, Mar 3, 2010 at 9:03 AM, Vassil Dichev <[email protected]> wrote: >> Check the users page- there is a user generated by an OpenID login, >> which seems to have an empty message. The login URL starts with >> https://me.yahoo.co.jp >> >> I'm not sure if there's an empty message because of an earlier >> exception when posting or because the user deliberately posted an >> empty message. At least it's not possible to post an empty message >> through the Web UI. >> >> Or maybe the key is in some special Asian characters used... At any >> rate, I'll try to make this more robust so that the error doesn't >> occur. > > > There is already a jira item for this problem: > http://issues.apache.org/jira/browse/ESME-152 > > Maybe, it is the same problem..... > > >> >> >> On Wed, Mar 3, 2010 at 9:52 AM, Vassil Dichev <[email protected]> wrote: >>> Actually the problem is here: >>> >>> private[model] object text extends MappedText(this){ >>> override lazy val asJsExp = >>> JE.Str(is.replaceFirst("(?<=<body>).*(?=</body>)", >>> digestedXHTML.mkString)) >>> } >>> >>> But this would mean that a message has no body... or maybe an empty >>> body? Let me check this. >>> >>> >>> On Wed, Mar 3, 2010 at 9:35 AM, Richard Hirsch <[email protected]> >>> wrote: >>>> We have a strange exception on the stax environment. >>>> >>>> I've created a JIRA item for the problem: >>>> https://issues.apache.org/jira/browse/ESME-169 >>>> >>>> Obviously, it is based on some characteristic of a particular message. >>>> Unfortunately, I don't know which message. It appears to be coming >>>> from a RSS twitter feed. >>>> >>>> D. >>>> >>> >> >
