[appengine-java] Re: JSP Question - Errors with servlet mapping
http://groups.google.com/group/google-appengine-java/browse_thread/thread/93ab73891be5518e http://groups.google.com/group/google-appengine-java/browse_thread/thread/dd17f4150950374cusg=AFQjCNHcdbQAaW_akVBTvb70Cu6zw_pRVg -- 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-j...@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] Necessity for Java graphics
IMPO, the best Java charting library in the world is JFreeChart. But you cannot use it for GAE. GAE architects would be overlooking one big phenomenon, if they ever recommend that we use client-side GWT graphics - you cannot and you should not if you are performing enterprise business charting. When I used to code in Cobol and Fortran 20 years ago, we would produce a 4 foot tall 50 lb stack of report per manager. A manager would pull out an inch of that report - the rest is collected by the janitor at 6 pm. So web-based dynamism has saved a lot of trees - we compelled people to print their own reports. So now, should we think we should compel users to give up on JPG, PNG or GIF charts in favour of javascripted images? No, javascripted images is not acceptable for charting. Javascripted images are good for SPC (statistical process control)/Shewhart, stock monitoring or various other real-time monitoring. But, when it comes to business reports, the user has to be able to right-click on the image and drag to paste on Open Office or MS Excel or Presentation. The user has to be able to edit the chart to place their own annotation in an Office graphics editor. Javascripted images is not usable that way. I realise the problem with JFreeChart and other Java graphics library is their dependency on AWT - and I recall having to set up video display emulators on headless servers hosting Tomcat to allow charting servlets to run. I think someone from Google recommended that people try using an Apache incubator library called something-something but first, are you sure GAE allows BufferedImage - isn't that an AWT thing? Secondly the features of that something-something... incubator lib compared to JFreeChart is like comparing the size of this planet to the Sun. So, if I need to sell my ideas to move things from local servers to GAE, Google needs to help me by providing means for Java graphics libraries to work on GAE (graphics which would either be stored on persistence repository or streamed directly to client). Otherwise, the only viable options are azure or ec2. -- 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-j...@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: What would you recommend: Objectify or Twig?
What a profound statement! On Jun 17, 1:05 am, Toby toby.ro...@gmail.com wrote: Actually by using it I started to understand the tricky parts of the datastore. The only thing I really regret is all the time I lost trying to make JDO work. -- 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-j...@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: Eclipse hangs at startup, Ubuntu
Is any of your resources sitting in a foreign file system like smb, ntfs or nfs? And do you have many projects mounted like I do? I had the same problem and I had to kill/restart the connector process to the foreign file system, whenever this happens. I would notice thrashing going own in the connection and eclipse got stuck. In my less than educated opinion, it looks like running datanucleus is too expensive during startup because it has to compete with rebuilds and other startup activities when automatic build is set on in eclipse and your data communication channels to those foreign file systems may not be able to cope with the traffic and somehow eclipse starts thrashing back and forth in its frenzy to get to what it wants, resulting in deadlocks. Therefore, the real question that I have been asking is - why did the eclipse designers make eclipse rebuild my projects on startup since they have already been rebuilt just before I shut eclipse down. Eclipse should memorise that fact that projects have already been rebuilt just before I shut it down. We should take a look if there is a bug report concerning this feature/bug. Perhaps, you could turn autobuild off everytime you exit eclipse so that it when eclipse is started, it would not autobuild - and turn it back on when eclipse startup has quieted down. In Galileo, when I switch autobuild off, I find that error highlights persists even though the code is error free until I restart autobuild. That is the disadvantage of switching autobuild off, because it would mislead me about the syntax integrity of the code. -- 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-j...@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] Datanucleaus enhancement not run when non-persistent superclass modified
I am using GWT 2, GAE 1.3.0 plugin on Eclipse Galileo. I have a class UtilJDO, which does not contain any persistent object. It merely pulls in the pm, pmf, and provide common methods for queries. My persistence classes extend UtilJDO so that they could all use the same utilities. Whenever I modify UtilJDO, without making modification to any persistence classes that extends it, development server at runtime croaks that it appears my persistence classes have not been enhanced and my queries, updates fail. To overcome this, I edit one of those persistence classes by introducing an insignificant space character and then saving it. Then datanucleaus reports 11 classes enhanced and my problem solved. Therefore, this is certainly a bug, isn't it? I mean, datanucleaus designers did not seem to have expected me to create persistent subclasses by extending a non-persistent class. -- 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-j...@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: Datanucleaus enhancement not run when non-persistent superclass modified
Or, is it because UtilJDO is an abstract generic class.
And that datanucleaus is not able to handle generics too well?
public class UtilJDOT extends UtilJDO?
{
}
Or, is it because UtilJDO does not have @PersistenceCapable
annotation. It shouldn't need the annotation because it has no
persistent objects.
--
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-j...@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] Where is jsp servlet source directory for jetty gae plugin linux?
A coding short-circuit I use to create servlets is first write a jsp, which the server then converts to a servlet java source. Then I locate the servlet source in Tomcat's runtime webapp directory and poach it and after making some changes to it, I use the source as the actual servlet. But where is the runtime webapp directory for jetty? I think someone also calls it the jetty jsp scratch directory. I managed to look for it for vista/xp but where is it for linux? Specifically for the case of google eclipse plugin. -- 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-j...@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] Where is jdoconfig.xml? Ref:JDO PersistanceManagerFactory transactions-optional failure
When I read the java section of http://code.google.com/appengine/docs/java/datastore/overview.html, there is no mention of jdoconfig.xml and the need of it being in war/WEB-INF/classes/META-INF/ . I followed this document as recommended, get the pmf factory singleton and then bam! I am hit with the verbose as described in: http://groups.google.com/group/google-appengine-java/browse_thread/thread/8b7677449f9a1f64/670b1b7c1b24d3de?#670b1b7c1b24d3de I searched (using find -name) and found a few copies of jdoconfig.xml at the demos in the gae eclipse plugin directory. I copied it over to the war and my problem was solved. I am using gae plugin 1.2.6, gwt 2 on karmic 64, galileo. Questions: 1. why gae plugin did not copy jdoconfig.xml to where it is needed? 2. otherwise, is http://code.google.com/appengine/docs/java/datastore/overview.html defective in its instructions in not mentioning I need jdoconfig somewhere in the war, or it presumes I am super-knowledgeable about jdo first before I should even try it? 3. Is it proper practice to have programmers look for jdoconfig.xml not anywhere more formal but in the demos? -- 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-j...@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: Why is it called Google App Engine for Java ?
Of course this should be called GAE Java, then what else? You could call every java feature you wish to, except that unsupported features will be met with runtime exception. If I made a robotic mainframe that we decided would be base on the JVM but certain Java features would cause inconsistencies or clashing of robotic limbs, we would simply preempt any catastrophe by runtime exceptions. Then we broadcast the java api to customers of the mainframe. Then customers request that we create an eclipse plugin that warns/ disallows them of any java code that would cause runtime exceptions and we tell our customers the name of the package is xyz robotic engine java. Should our customers complain to us and say, hey this is not java, you have to many exceptions. ??? -- 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-j...@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] why setter getter advised when using datanucleus ?
We are advised to have our persistent fields accessible only thro
setter/getter and not to allow public access, less the JDO mechanism
is bypassed.
We are also advised to implement persistenceCapable interface.
However, in gae java, we don't seem to require to implement
persistenceCapable interface, but merely place @PersistenceCapable
annotation appropriately.
A setter/getter is merely
setHello(hello){this.hello = hello;}
getHello{return this.hello;}
There is nothing else in between those lines that could be bypassed.
That set me thinking ...
Does @PersistenceCapable and all the other gae @ annotations modify/
enhance my java code and insert extra stuffs into my setters/getters
during compilation which would be bypassed if those fields were
accessed directly by non-persistence aware classes?
--
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-j...@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: why setter getter advised when using datanucleus ?
Also, does @PersistenceCapable cause gae sdk to insert implements PersistenceCapable for us or is it the case that gae simply/ inconsistently do not require us to implement PersistenceCapable? -- 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-j...@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.
