[appengine-java] Error while installing Eclipse Plugin
I'm trying install Eclipse plugin for GAE with GAE SDK on Eclipse Helios but following error occurs while installation. Any Help??? An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Unable to read repository at http://dl.google.com/eclipse/plugin/3.6/plugins/com.google.appengine.eclipse.sdkbundle.1.4.0_1.4.0.v201012021502.jar . Read timed out Unable to read repository at http://dl.google.com/eclipse/plugin/3.6/plugins/com.google.gwt.eclipse.sdkbundle.2.1.0_2.1.0.v201010280102.jar . Read timed out Regards, Zeeshan Hanif -- 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.
Re: [appengine-java] no async queries on AsyncDatastoreService for 1.4.0?
Hi Max,
Could you please provide input on the following design:
We design for DataSource redundancy. For this we've built a flow which
obtains data from 2 sources: First from GAE DataSource using PreparedQuery
and if that fails (0.5sec timeout) from our backup service feed which we
access using URLFetch (auto scaled EC2 nodes).
We strive for maximum performance, So we plan to issue async call to each of
the data sources and later when the data becomes required poll the 2
sources, using the first one available.
As for the URLFetch service, we will use this patten:
FutureHTTPResponse f = fetchService.fetchAsync(request);
...
if(f.isDone()) { ... }
But for PreparedQuery.asIterator(), I'm not sure how this is implement on
your side. I would love an answer confirming that this code will not block
on hasNext() (While datasource is asynchronously getting results)?
IteratorEntity iterator =
getAsyncDatastoreService().prepare(findGeoIP).asIterator();
if(iterator.hasNext()) { ... }
Thanks for the insights.
Maxim.
On Mon, Nov 29, 2010 at 9:08 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Hi Luke,
First the awesome news:
As of 1.4.0, many queries are implicitly asynchronous. When you call
PreparedQuery.asIterable() or PreparedQuery.asIterator(), we initiate the
query in the background and then immediately return. This lets you do work
while the first batch of results is being fetched. And, when the first
batch has been consumed we immediately request the next batch. If you're
performing a significant amount of work with each Entity as you iterate you
will probably see a latency win as a result of this.
Now the less awesome news:
We didn't get around to making the List returned by PreparedQuery.asList()
work this same magic, but you can expect this in a future release.
Some deeper thoughts:
The underlying RPCs between your app and the datastore fetch results in
batches. We fetch an initial batch of results, and once that batch has been
consumed we fetch the next batch. But, there's nothing in the API that maps
to these batches - it's either a List containing the entire result set or an
Iterable/Iterator that returns Entities one at a time. An API that provides
async access to the individual results returned by an Iterable/Iterator
(IteratorFutureEntity) doesn't really make sense since you don't know
which call to hasNext() is going to require a new batch to be fetched, and
without that knowledge, the knowledge of what is going to trigger something
expensive, you can't really make appropriate use of an asynchronous API.
Going forward, we're definitely interested in exposing these batches
directly, and an explicitly async API for these batches makes a lot of sense
since fetching these batches would map directly to something expensive on
the server side.
Hope this helps,
Max
On Fri, Nov 26, 2010 at 4:41 PM, Luke lvale...@gmail.com wrote:
i was taking a look at the 1.4.0 javadoc for AsyncDatastoreService. i
see the get, put and delete operations return a Future, but the
prepare methods return a naked PreparedQuery object, and it doesn't
look like PreparedQuery has any async get methods.
does the AsyncDatastoreService not support asynchronous queries, or is
there something i'm missing?
glad to see at lets the get and put methods are async, hoping to get
async queries too (as well as async interfaces to more services).
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
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] petstore deployment
Hi All, I'm trying to deploy petstore 2.0 on Google app engine (SDK 1.3.8). So many limitations from app engine... I had to many changes on JSF side to deploy the app. After the deployment process, I'm stuck with JSF rendering issue... no clue how to proceed with the same. --- SEVERE: JSF1054: (Phase ID: RENDER_RESPONSE 6, View ID: /index.jsp) Exception thrown during phase execution: javax.faces.event.phaseevent[source=com.sun.faces.lifecycle.lifecyclei...@aaf063] javax.servlet.ServletException at javax.faces.webapp.FacesServlet.service(FacesServlet.java:325) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) ... --- Major problem I'm having is no logs being generated on development environment. Exception stack says, more information could be found at 'server logs' but, no logs are generated on local machine. When I try to host it on app. engine ( so that, I can view logs from app. engine dashboard)... the deployment fails with following exception. Latest SDK: Release: 1.4.0 Timestamp: Thu Dec 02 04:44:18 GMT+05:30 2010 API versions: [1.0] --- Your SDK: Release: 1.3.8 Timestamp: Wed Oct 13 20:36:43 GMT+05:30 2010 API versions: [1.0] --- Please visit http://code.google.com/appengine for the latest SDK. Creating staging directory Scanning for jsp files. Compiling jsp files. Scanning files on local disk. Scanned 250 files. Scanned 500 files. Initiating update. java.io.IOException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=petstore5version=1; 404 Not Found This application does not exist (app_id=u'petstore5'). I have SDK 1.3.8; does this mean, I can't use this version anymore? Any pointers would be highly appreciated. Thanks, Suresh -- 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.
Re: [appengine-java] no async queries on AsyncDatastoreService for 1.4.0?
Currently hasNext() will block on the first batch of results. There is
currently no way to do what you are asking in Java.
On Tue, Dec 7, 2010 at 2:40 AM, Maxim Veksler ma...@vekslers.org wrote:
Hi Max,
Could you please provide input on the following design:
We design for DataSource redundancy. For this we've built a flow which
obtains data from 2 sources: First from GAE DataSource using PreparedQuery
and if that fails (0.5sec timeout) from our backup service feed which we
access using URLFetch (auto scaled EC2 nodes).
We strive for maximum performance, So we plan to issue async call to each
of the data sources and later when the data becomes required poll the 2
sources, using the first one available.
As for the URLFetch service, we will use this patten:
FutureHTTPResponse f = fetchService.fetchAsync(request);
...
if(f.isDone()) { ... }
But for PreparedQuery.asIterator(), I'm not sure how this is implement on
your side. I would love an answer confirming that this code will not block
on hasNext() (While datasource is asynchronously getting results)?
IteratorEntity iterator =
getAsyncDatastoreService().prepare(findGeoIP).asIterator();
if(iterator.hasNext()) { ... }
Thanks for the insights.
Maxim.
On Mon, Nov 29, 2010 at 9:08 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Hi Luke,
First the awesome news:
As of 1.4.0, many queries are implicitly asynchronous. When you call
PreparedQuery.asIterable() or PreparedQuery.asIterator(), we initiate the
query in the background and then immediately return. This lets you do work
while the first batch of results is being fetched. And, when the first
batch has been consumed we immediately request the next batch. If you're
performing a significant amount of work with each Entity as you iterate you
will probably see a latency win as a result of this.
Now the less awesome news:
We didn't get around to making the List returned by PreparedQuery.asList()
work this same magic, but you can expect this in a future release.
Some deeper thoughts:
The underlying RPCs between your app and the datastore fetch results in
batches. We fetch an initial batch of results, and once that batch has been
consumed we fetch the next batch. But, there's nothing in the API that maps
to these batches - it's either a List containing the entire result set or an
Iterable/Iterator that returns Entities one at a time. An API that provides
async access to the individual results returned by an Iterable/Iterator
(IteratorFutureEntity) doesn't really make sense since you don't know
which call to hasNext() is going to require a new batch to be fetched, and
without that knowledge, the knowledge of what is going to trigger something
expensive, you can't really make appropriate use of an asynchronous API.
Going forward, we're definitely interested in exposing these batches
directly, and an explicitly async API for these batches makes a lot of sense
since fetching these batches would map directly to something expensive on
the server side.
Hope this helps,
Max
On Fri, Nov 26, 2010 at 4:41 PM, Luke lvale...@gmail.com wrote:
i was taking a look at the 1.4.0 javadoc for AsyncDatastoreService. i
see the get, put and delete operations return a Future, but the
prepare methods return a naked PreparedQuery object, and it doesn't
look like PreparedQuery has any async get methods.
does the AsyncDatastoreService not support asynchronous queries, or is
there something i'm missing?
glad to see at lets the get and put methods are async, hoping to get
async queries too (as well as async interfaces to more services).
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
[appengine-java] Re: Chanel API Java Client
AFAIK You cannot use the Channel API from Android unless you write the Java Client library yourself. There is a relevant issue opened here: http://code.google.com/p/googleappengine/issues/detail?id=4189 You can star it if you are interested. It has already 36 votes. On Dec 7, 2:26 pm, Christian Kosmowski ksm...@googlemail.com wrote: Hi! I was wondering if there is a way to use the channels API directly through java. I'd like to use it in Android and i thought it would be a bit heavyweight to use a JavaScript Implementation just for communication with the channels API. -- 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.
Re: [appengine-java] no async queries on AsyncDatastoreService for 1.4.0?
Thank you for the information.
We kinda expected that the current implementation will block...
In case anyone wonders our current worked out design is as following: Do
async get to EC2 (takes ~270ms) and right after that do blocking get to
datastore (with timeout of 300ms).
Because we know URLFetch to ec2 takes ~270ms and is async we get to enjoy
both worlds even with a blocking DataStore:
Option A: Datastore has no problems, meaning that it will reply to
PreparedQuery with 15ms. In this case we don't bother with the async call we
just did and just continue normal flow.
Option B: Datastore has problems, and will block. In this case the 300ms
query will time out, after which we will attempt to access the Future.get()
of URLFetch where we expect to have a result.
So... If today we did (at maximum) 500ms datastore get + 270ms URLFetch get
= total of 770ms just for the query after I get implemented we should be
doing (at maximum) query in 300ms.
Kinda of cool.
Maxim.
On Tue, Dec 7, 2010 at 3:39 PM, Alfred Fuller
arfuller+appeng...@google.comarfuller%2bappeng...@google.com
wrote:
Currently hasNext() will block on the first batch of results. There is
currently no way to do what you are asking in Java.
On Tue, Dec 7, 2010 at 2:40 AM, Maxim Veksler ma...@vekslers.org wrote:
Hi Max,
Could you please provide input on the following design:
We design for DataSource redundancy. For this we've built a flow which
obtains data from 2 sources: First from GAE DataSource using PreparedQuery
and if that fails (0.5sec timeout) from our backup service feed which we
access using URLFetch (auto scaled EC2 nodes).
We strive for maximum performance, So we plan to issue async call to each
of the data sources and later when the data becomes required poll the 2
sources, using the first one available.
As for the URLFetch service, we will use this patten:
FutureHTTPResponse f = fetchService.fetchAsync(request);
...
if(f.isDone()) { ... }
But for PreparedQuery.asIterator(), I'm not sure how this is implement on
your side. I would love an answer confirming that this code will not block
on hasNext() (While datasource is asynchronously getting results)?
IteratorEntity iterator =
getAsyncDatastoreService().prepare(findGeoIP).asIterator();
if(iterator.hasNext()) { ... }
Thanks for the insights.
Maxim.
On Mon, Nov 29, 2010 at 9:08 PM, Max Ross (Google)
maxr+appeng...@google.com maxr%2bappeng...@google.com wrote:
Hi Luke,
First the awesome news:
As of 1.4.0, many queries are implicitly asynchronous. When you call
PreparedQuery.asIterable() or PreparedQuery.asIterator(), we initiate the
query in the background and then immediately return. This lets you do work
while the first batch of results is being fetched. And, when the first
batch has been consumed we immediately request the next batch. If you're
performing a significant amount of work with each Entity as you iterate you
will probably see a latency win as a result of this.
Now the less awesome news:
We didn't get around to making the List returned by
PreparedQuery.asList() work this same magic, but you can expect this in a
future release.
Some deeper thoughts:
The underlying RPCs between your app and the datastore fetch results in
batches. We fetch an initial batch of results, and once that batch has been
consumed we fetch the next batch. But, there's nothing in the API that maps
to these batches - it's either a List containing the entire result set or an
Iterable/Iterator that returns Entities one at a time. An API that provides
async access to the individual results returned by an Iterable/Iterator
(IteratorFutureEntity) doesn't really make sense since you don't know
which call to hasNext() is going to require a new batch to be fetched, and
without that knowledge, the knowledge of what is going to trigger something
expensive, you can't really make appropriate use of an asynchronous API.
Going forward, we're definitely interested in exposing these batches
directly, and an explicitly async API for these batches makes a lot of sense
since fetching these batches would map directly to something expensive on
the server side.
Hope this helps,
Max
On Fri, Nov 26, 2010 at 4:41 PM, Luke lvale...@gmail.com wrote:
i was taking a look at the 1.4.0 javadoc for AsyncDatastoreService. i
see the get, put and delete operations return a Future, but the
prepare methods return a naked PreparedQuery object, and it doesn't
look like PreparedQuery has any async get methods.
does the AsyncDatastoreService not support asynchronous queries, or is
there something i'm missing?
glad to see at lets the get and put methods are async, hoping to get
async queries too (as well as async interfaces to more services).
--
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
[appengine-java] Re: 1.4 eclipse plugin
I have the same problem - .jsp's work fine after moving the App Engine SDK to the top of the Order and Export list, but JSP-mappings don't work. I can also confirm that it works on the App Engine servers, deployed with the 1.4 SDK. Mac OS X 10.6.5 Eclipse SDK, Version: 3.5.2 Google Plugin for Eclipse 3.5, 1.4.0.v201010280047 This is the error I'm getting in the browser: HTTP ERROR 500 Problem accessing /admin/. Reason: Unable to compile class for JSP: An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type ... On Dec 6, 8:39 pm, mscwd01 mscw...@gmail.com wrote: I'm running: Eclipse Java EE IDE for Web Developers. Build id: 20100218-1602 With V1.4 of the App Engine SDK and cannot get servlets mapping to jsp files, i.e. servlet servlet-nameabout/servlet-name jsp-file/about.jsp/jsp-file /servlet servlet-mapping servlet-nameabout/servlet-name url-pattern/about/url-pattern /servlet-mapping However, other servlets work fine for example I have servlets which issue a redirect to a jsp file in my WEB-INF folder and they work fine. It's baffling me now. -- 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: OpenID: What's the use of the createLoginURL attributesRequest parameter
I'd like some clarification on this as well. According to the javadoc: attributesRequest - additional attributions requested for this login, IDP may not may not support these attributes. So what are some examples of this? The User object returned from UserService.getCurrentUser() after openId authentication is very different depending on the provider. In particular some (google yahoo) have an email address on the user, others(myopenid.com) do not. Does specifying attributes ask the provider to return data like email addresses? Do I have to specify different attributes for each provider implementation? On Nov 5, 6:00 am, Alex alex.jong...@gmail.com wrote: Hi, the createLoginURL method for federated login with OpenID has a Set of Strings parameter attribuesRequest. The JavaDoc states the following about this parameter: attributesRequest - additional attributions requested for this login, IDP may not may not support these attributes. Until now I didn't require to fill this attribute to use OpenID with parties like Google, Yahoo etc. But I was wondering what kind of requests I might encounter / use here. Are there any (Java) examples where this parameter is used? And what does IDP mean? Alex -- 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: 1.4 eclipse plugin
I created an issue 4216 - see the url above. Hope the GAE guys will get to it soon. For now it looks like it is safe to keep using 1.3.8 since the actual app engine is not affected by this. On Dec 7, 5:22 am, Thomas Meyer meyer...@gmail.com wrote: I have the same problem - .jsp's work fine after moving the App Engine SDK to the top of the Order and Export list, but JSP-mappings don't work. I can also confirm that it works on the App Engine servers, deployed with the 1.4 SDK. Mac OS X 10.6.5 Eclipse SDK, Version: 3.5.2 Google Plugin for Eclipse 3.5, 1.4.0.v201010280047 This is the error I'm getting in the browser: HTTP ERROR 500 Problem accessing /admin/. Reason: Unable to compile class for JSP: An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type ... On Dec 6, 8:39 pm, mscwd01 mscw...@gmail.com wrote: I'm running: Eclipse Java EE IDE for Web Developers. Build id: 20100218-1602 With V1.4 of the App Engine SDK and cannot get servlets mapping to jsp files, i.e. servlet servlet-nameabout/servlet-name jsp-file/about.jsp/jsp-file /servlet servlet-mapping servlet-nameabout/servlet-name url-pattern/about/url-pattern /servlet-mapping However, other servlets work fine for example I have servlets which issue a redirect to a jsp file in my WEB-INF folder and they work fine. It's baffling me now. -- 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.
Re: [appengine-java] Xls uploader
I don't know if these examples will work since they may require whitelisted classes, but there are quite a few examples of how to read XLS files using Java: http://www.google.com/search?sourceid=chromeie=UTF-8q=read+xls+file+java Let us know which one of these works and which ones don't. It'll be very helpful. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Tue, Dec 7, 2010 at 1:18 AM, Srikanth PB srikanthprathiv...@gmail.comwrote: Hi My Application requires to upload data in the java datastore , I am able to do that using csv , but I want to upload using xls Because I have images inside the cells which are to be uploaded to data store , Can anyone provide a working example? -- 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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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] JSF: sudden ViewExpiredException on GAE
Hello all,
I've suddenly stuck with JavaServer Faces application stopped working
at GAE. Investigation shows that view state is not being stored in
session correctly.
What I also found out is that when the first request is being done
(i.e. with clean session), ajax requests are working; but when another
view is requested, ajax is not working there anymore. I assumed this is
because updated view state is not being stored, and tried to make a
slight change:
a) as is:
Map statesMap = session.get(state);
if (statesMap == null) {
statesMap = new HashMap();
session.put(state, statesMap);
}
statesMap.put(..., state);
//force update in cluster
session.put(state, statesMap);
b) with the slight change:
Map statesMap = session.get(state);
if (statesMap == null) {
statesMap = new HashMap();
session.put(state, statesMap);
}
statesMap.put(..., state);
//force update in cluster
session.remove(state);
session.put(state, statesMap);
However the solution is not very good, so can please someone help with
the problem?
P.S. Runnable demo example is available here:
http://java.net/jira/browse/JAVASERVERFACES-1886
--
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: 1.3.8 Console Logging Issue
Yep, still not working as in the past. So here goes my fundamental question: is it a bug or a feature (http:// globalnerdy.com/wordpress/wp-content/uploads/2007/12/ bug_vs_feature.gif)? Please answer! On 4 Gru, 00:50, MarkH markh.ne...@gmail.com wrote: I'm still having Eclipse console logging issues with 1.4.0. (OSX10.6.5/ Helios). I tried the following: 1. Used the Eclipse plugin to generate a new GWT/AppEngine app. 2. Added a java.util.logging.Logger to the GreetingServiceImpl 3. Added logger.fine(test); to the greetServer call 4. set logging.properites level to .level = FINE As per 1.3.8 there are still no logger.fine log message in the Eclipse console. As per 1.3.8 logger.info adds messages to the console in the same format as the Jetty startup phase - message text only (no date, or logger info). As per 1.3.8 setting the Run Configuration - Arguments - Program Arguments to, -logLevel DEBUG does causes logger.fine messages (message text only) to appear on the console, along with the associated GWT noise. Is it possible to restore 1.3.7 like 'SimpleFormatter' style logging: date, logger, message in the Eclipse console? On Nov 22, 4:23 pm, timzon jerome.bre...@gmail.com wrote: Thank you. Looking forward to get 1.4.0. On Nov 4, 9:33 am, Rajeev Dayal rda...@google.com wrote: We're going to fix this for the App Engine 1.4.0 release. What we'll do is have messages at Log.INFO level be outputted when you've got your Launch Configuration's log level set to INFO. In the Google Plugin for Eclipse, we'll make a change such that any new launch configurations created have a default log level of WARN. On Thu, Nov 4, 2010 at 4:23 AM, Stefano Ciccarelli stef...@indacosoftware.it wrote: I changed the GWT log level to TRACE solving partially the problem, infact now I have very verbose logs. On Wed, Nov 3, 2010 at 15:33, Rajeev Dayal rda...@google.com wrote: No, I did not mean dropping it there - I meant changing it in the Web App Launch Configuration UI - edit your launch configuration (in Eclipse), and set the log level to TRACE. Does that help? On Tue, Nov 2, 2010 at 10:38 PM, timzon jerome.bre...@gmail.com wrote: Dropping default log level (.level) to TRACE, INFO or FINEST doesn't fix the problem. log.info (with default INFO level) used to work before 1.3.8 upgrade and doesn't work after the upgrade. On Oct 29, 2:49 pm, Rajeev Dayal rda...@google.com wrote: Drop you launch configuration's log level down to TRACE. Do you see the messages now? On Fri, Oct 29, 2010 at 1:23 PM, John Bito j...@bobberinteractive.com wrote: Starred the issue: http://code.google.com/p/googleappengine/issues/detail?id=3969 -- 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.comgoogle-appengine-java%2B unsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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
Re: [appengine-java] JSF: sudden ViewExpiredException on GAE
Well, I'll take a wild stab at it since I don't know Java Server Faces, but
since you say it was working and now has stopped. Do you have
sessions-enabledtrue/sessions-enabled in your appengine-web.xml? If not,
add it. As of 1.4 this is now being adhered to whereas prior to this
sessions were enabled regardless. So perhaps even with sessions not enabled
you are able to get a session object from the servlet context for that
initial request but the appengine isn't saving state to the datastore so the
next request gets told that the requested session identifer is not
valid/expired.
On Tue, Dec 7, 2010 at 12:50 PM, Nick Belaevski mika...@gmail.com wrote:
Hello all,
I've suddenly stuck with JavaServer Faces application stopped working at
GAE. Investigation shows that view state is not being stored in session
correctly.
What I also found out is that when the first request is being done (i.e.
with clean session), ajax requests are working; but when another view is
requested, ajax is not working there anymore. I assumed this is because
updated view state is not being stored, and tried to make a slight change:
a) as is:
Map statesMap = session.get(state);
if (statesMap == null) {
statesMap = new HashMap();
session.put(state, statesMap);
}
statesMap.put(..., state);
//force update in cluster
session.put(state, statesMap);
b) with the slight change:
Map statesMap = session.get(state);
if (statesMap == null) {
statesMap = new HashMap();
session.put(state, statesMap);
}
statesMap.put(..., state);
//force update in cluster
session.remove(state);
session.put(state, statesMap);
However the solution is not very good, so can please someone help with the
problem?
P.S. Runnable demo example is available here:
http://java.net/jira/browse/JAVASERVERFACES-1886
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
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] Blobstore Code Works On Dev Server, Not Production
My blobstore code works just great in the dev server (running on Mac) but I receive an error when uploading to production. I receive an Error: HTTP method GET is not supported by this URLeven though the sample refers to post. As I said, works fine in Dev. Please help! -- 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] Found a jar file too large to upload:appengine-api-1.0-sdk-1.3.7.jar. Consider using --enable_jar_splitting.
I just now started to get this error while deploying to app engine. This project was deployed without this error with the same jar until last night without any problem. I tried using the -- enable_jar_splitting but the error is still coming..any help is appreciated.. -- 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.
Re: [appengine-java] Blobstore Code Works On Dev Server, Not Production
You can solve that handling GETs and POSTs with a common handler.
void doGet(... req,... resp) {
handle(req, resp);
}
void doPost(... req,... resp) {
handle(req, resp);
}
void handle(... req,... resp) {
}
On Tue, Dec 7, 2010 at 6:21 PM, Andy Haaf ah...@google.com wrote:
My blobstore code works just great in the dev server (running on Mac) but I
receive an error when uploading to production. I receive an Error: HTTP
method GET is not supported by this URL even though the sample refers to
post. As I said, works fine in Dev. Please help!
--
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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
Guit: Elegant, beautiful, modular and *production ready* gwt applications.
http://code.google.com/p/guit/
--
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.
Re: [appengine-java] Blobstore Code Works On Dev Server, Not Production
So, I did that, but now I am receiving the following error:
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; line-height: 19.0px; font:
13.0px Courier New}
java.lang.IllegalStateException: Must be called from a blob upload
callback request
Plus, I needed to change my .jsp form code to a get versus a post
which is not what the sample recommended. And once again, this was
working fine on the dev server. Why is production different?
--
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.
