[appengine-java] How to use ResourceBundle on GAE ?
I don't understand why ResourceBundle doesn't work on GAE (however on app engine white list) ... Should we do something special/unusual to use it in production ? Thx ! =D -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re : GAE and Logback - A little solution
It seems nobody use logback yet xD -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] GAE and Logback - A little solution
Hi everybody !
For my e-commerce app on GAE, I wanted to use logback but, like everybody
know, that solution doesn't display the correct log levels in the console.
So I've written a logback appender (based on
http://androidisland.blogspot.com/2010/10/gae-and-log4j-getting-them-to-work-bit.html)
which passes on logback severity levels to GAE's JUL framework.
You probably should not use the JUL configuration and let it as simple as it
can (logging.properties) :
logback.level = ALL
Here is the convenient appender :
public class GAELogAppender extends AppenderBase {
private static final Logger log = Logger.getLogger("logback");
PatternLayoutEncoder encoder;
public GAELogAppender() {
}
@Override
protected void append(ILoggingEvent event) {
Level level = event.getLevel();
//To optimize, reorder according to how often levels are hit
if (level.equals(Level.ERROR))
log.severe(encoder.getLayout().doLayout(event));
else if (level.equals(Level.WARN))
log.warning(encoder.getLayout().doLayout(event));
else if (level.equals(Level.INFO))
log.info(encoder.getLayout().doLayout(event));
else if (level.equals(Level.DEBUG))
log.fine(encoder.getLayout().doLayout(event));
else
// if (level.equals(Level.TRACE))
log.finest(encoder.getLayout().doLayout(event));
}
public PatternLayoutEncoder getEncoder() {
return encoder;
}
public void setEncoder(PatternLayoutEncoder encoder) {
this.encoder = encoder;
}
}
And configure log with logback xml file. Here is a snippet of code :
%date{dd/MM/ HH:mm:ss} %level %logger:%line -
%message%n
I think it can help other people and I'd love to hear some feedback or way
to improve it. ;)
Regards,
Simon Debaecke
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] JPA/JDO vs low level API
Ok thank you, it's just what I thought ;) -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] JPA/JDO vs low level API
Hi Jeff' In fact, I'm not sure to understand what you means by “Because of GAE's transaction model, this is actually necessary quite often.” : what are the characteristics/limitations of GAE's transaction model you thinking about ? Thx -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: JPA/JDO vs low level API
Thanks you so much for all this responses everybody ! -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] JPA/JDO vs low level API
I have a question : What are the differences between JPA/JDO and low level API (and Objectify) in practice ? I read everywhere the low level API provides more flexibility, but there are never samples code or evidences to demonstrate it. So I'm wondering in which cases exactly, the low level API is useful ? Thanks in advance -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
