What Servlet API?

[Joshua Fox]

App Engine Standard Env uses the Java Servlet 2.5 API. Flexible Env uses Servlet 3.1 

The sample pom.xml for Standard Env -- apparently valid for compat -- and  the sample pom.xml for the new noncompat Flex env, with different Servlet versions in each, say  that the scope is provided.

As you know, our internal libraries are shared across Standard and Flexible Env. Although most of our servlets run in only one or the other, we want compatible code.

What do you recommend we do? Alter the pom that we use in noncompat Flex  to specify 2.5 to ensure backwards compatibility (while  the provided library will have a different version according to GAE environment type)?

[George (Cloud Platform Support)]

One can only congratulate you on the on the tendency to migrate away from the standard environment and onto flex. 

Your idea, to take advantage of the flexibility offered by the new flex environment and modify the pom.xml to your liking may work, depending on the structure and environment requirements of your app. It may constitute a temporary solution, till you migrate all your estate to the flex environment. 

For a more in-depth look at this situation, details such as your project name and relevant code information are necessary. You can send this info in confidential manner through a private email.

[Joshua Fox]

Thank you, but we are not migrating away from Standard Env.  We are  using Standard Env for frontends, and Flex Env for backends that need to go beyond the limits imposed by Standard.

Is there a long-term plan to deprecate Standard Env?

On Wed, Mar 1, 2017 at 8:45 PM, 'George (Cloud Platform Support)' via Google App Engine <google-a...@googlegroups.com> wrote:

One can only congratulate you on the on the tendency to migrate away from the standard environment and onto flex. 

Your idea, to take advantage of the flexibility offered by the new flex environment and modify the pom.xml to your liking may work, depending on the structure and environment requirements of your app.

Actually, we need a pom  that allows us to generate either build: frontend (Standard) or backend (Flex).

 

It may constitute a temporary solution, till you migrate all your estate to the flex environment. 

For a more in-depth look at this situation, details such as your project name and relevant code information are necessary. You can send this info in confidential manner through a private email.

Will do. 

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscribe@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0f68876a-e190-49f0-b11f-88c567ae34a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

JOSHUA FOX

Principal Software Architect | Freightos

☏ (Israel): +972-545691165 | ☏ (US):  +1-3123400953 | Skype: joshuafox.freightos

Smoother shipping with the world's online freight marketplace.

Online Marketplace / In the News / Freightos Blog

[Ramki Krishnan]

There are no short-term or long-term plans to deprecate the Standard environment.

Ramki Krishnan | App Engine Flex | 650.533.6816

On Wed, Mar 1, 2017 at 10:43 PM, Joshua Fox <jos...@freightos.com> wrote:

Thank you, but we are not migrating away from Standard Env.  We are  using Standard Env for frontends, and Flex Env for backends that need to go beyond the limits imposed by Standard.

Is there a long-term plan to deprecate Standard Env?

On Wed, Mar 1, 2017 at 8:45 PM, 'George (Cloud Platform Support)' via Google App Engine <google-appengine@googlegroups.com> wrote:

One can only congratulate you on the on the tendency to migrate away from the standard environment and onto flex. 

Your idea, to take advantage of the flexibility offered by the new flex environment and modify the pom.xml to your liking may work, depending on the structure and environment requirements of your app.

Actually, we need a pom  that allows us to generate either build: frontend (Standard) or backend (Flex).

 

It may constitute a temporary solution, till you migrate all your estate to the flex environment. 

For a more in-depth look at this situation, details such as your project name and relevant code information are necessary. You can send this info in confidential manner through a private email.

Will do. 

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscribe@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0f68876a-e190-49f0-b11f-88c567ae34a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

JOSHUA FOX

Principal Software Architect | Freightos

☏ (Israel): +972-545691165 | ☏ (US):  +1-3123400953 | Skype: joshuafox.freightos

Smoother shipping with the world's online freight marketplace.

Online Marketplace / In the News / Freightos Blog

--
You received this message because you are subscribed to the Google Groups "App Engine Flexible" group.
To unsubscribe from this group and stop receiving emails from it, send an email to app-engine-flexible+unsub...@googlegroups.com.
To post to this group, send email to app-engine-flexible@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/app-engine-flexible/CAD%3DB7cMdQsaxLN%3DxuH0tZHVwBq6ctps09z68K14CcSEn%2BMcDog%40mail.gmail.com.

[Amir Rouzrokh]

Hey guys, This is Amir Rouzrokh, GAE Product Manager. 

Hi Joshua, apologies for the mixed message. Standard and Flexible environments are both fully supported on App Engine and we can help you with your issues on both and should you decide to migrate from one to the other (either flex to standard or vice versa) we can help there as well. Can you please give us some more context so we can help you out here? 

Thanks,

Amir

 

On Thursday, March 2, 2017 at 1:58:24 AM UTC-5, Ramki Krishnan wrote:

There are no short-term or long-term plans to deprecate the Standard environment.

Ramki Krishnan | App Engine Flex | 650.533.6816

On Wed, Mar 1, 2017 at 10:43 PM, Joshua Fox <jos...@freightos.com> wrote:

Thank you, but we are not migrating away from Standard Env.  We are  using Standard Env for frontends, and Flex Env for backends that need to go beyond the limits imposed by Standard.

Is there a long-term plan to deprecate Standard Env?

On Wed, Mar 1, 2017 at 8:45 PM, 'George (Cloud Platform Support)' via Google App Engine <google-a...@googlegroups.com> wrote:

One can only congratulate you on the on the tendency to migrate away from the standard environment and onto flex. 

Your idea, to take advantage of the flexibility offered by the new flex environment and modify the pom.xml to your liking may work, depending on the structure and environment requirements of your app.

Actually, we need a pom  that allows us to generate either build: frontend (Standard) or backend (Flex).

 

It may constitute a temporary solution, till you migrate all your estate to the flex environment. 

For a more in-depth look at this situation, details such as your project name and relevant code information are necessary. You can send this info in confidential manner through a private email.

Will do. 

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.

Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0f68876a-e190-49f0-b11f-88c567ae34a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

JOSHUA FOX

Principal Software Architect | Freightos

☏ (Israel): +972-545691165 | ☏ (US):  +1-3123400953 | Skype: joshuafox.freightos

Smoother shipping with the world's online freight marketplace.

Online Marketplace / In the News / Freightos Blog

--
You received this message because you are subscribed to the Google Groups "App Engine Flexible" group.
To unsubscribe from this group and stop receiving emails from it, send an email to app-engine-flexible+unsub...@googlegroups.com.

To post to this group, send email to app-engin...@googlegroups.com.

[Les Vogel]

Hi Joshua,

It's my understanding that if you include 2.5 of the Servlet API it will also work on GAE Flex for Java (which uses Jetty 9.x).  The API's are compatible as 3.1 is about using annotations (for the most part).

Ramki mentioned Java 8 for GAE Standard -- that will support 3.1 and Jetty 9.x

Regards,

Les

To unsubscribe from this group and stop receiving emails from it, send an email to app-engine-flexible+unsubscribe...@googlegroups.com.

To post to this group, send email to app-engin...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/app-engine-flexible/CAD%3DB7cMdQsaxLN%3DxuH0tZHVwBq6ctps09z68K14CcSEn%2BMcDog%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

•  Les Vogel   •  Cloud Developer Relations   •  le...@google.com   •  +1-408-676-7023