This problem finds its roots in a Scala bug. Turns out that:
def accessPools(in: NodeSeq): NodeSeq = {
for(user - User.currentUser.toSeq;
p- Privilege.findWritablePools(user.id))
// slow?
yield option value={p}
{AccessPool.find(p).get.getName}
I updated source code from SVN and could not open message main page now.
I could not find what's wrong, and I can open other pages.
Did anyone meet the some and help?
The exception is :
Exception occured while processing /
Message: java.lang.UnsupportedOperationException: unsuitable as hash
try mvn clean install. David did some major Lift-related commits yesterday.
I did a SVN update on Friday and then a deplóyment for Stax and it worked.
D.
On Sat, Oct 24, 2009 at 2:23 PM, Xuefeng Wu ben...@gmail.com wrote:
I updated source code from SVN and could not open message main page now.
It worked when I use other user login.
This exception related with my exist date.
Other thing,
did you notice this ?
[WARNING]
D:\Workstation\scala\esme_server\src\main\scala\org\apache\esme\actor\
UserActor.scala:248: warning: match is not exhaustive!
[WARNING] missing combination ScalaInterpret
It worked when I use other user login.
Good
UserActor.scala:248: warning: match is not exhaustive!
I know there are a variety of warnings when compiling. I've never
looked at them more closely. We will have to do this at some point
though.
D.
On Sat, Oct 24, 2009 at 4:23 PM, Xuefeng Wu
I know there are a variety of warnings when compiling. I've never
looked at them more closely. We will have to do this at some point
though.
I've made it a point to clear off all warnings, because it made a
negative impression on someone who tried to build ESME (Michael
Galpin, I think). One
