hat you cannot open multiple browser
> tabs with different data. Think about having a list of Cars and then
> opening 2 different car-edit dialoges in new browser tabs. That would not
> work using @SessionScoped and is the reason why we invented @WindowScoped
> and consorts.
> >&
would not work using
>>@SessionScoped and is the reason why we invented @WindowScoped and consorts.
>>>
>>>
>>>LieGrue,
>>>strub
>>>
>>>
>>>
>>>
>>>- Original Message -
>>>> From: "Howard W
> strub
>>
>>
>>
>>
>> - Original Message -
>> > From: "Howard W. Smith, Jr."
>> > To: MyFaces Discussion
>> > Cc:
>> > Sent: Wednesday, November 21, 2012 11:55 AM
>> > Subject: Re: Migration to TomEE
> > To: MyFaces Discussion
> > Cc:
> > Sent: Wednesday, November 21, 2012 11:55 AM
> > Subject: Re: Migration to TomEE/CDI complete, regression testing,
> ViewAccessScoped
> >
> >T hanks Gerhard, will take a look.
> >
> > Honestly, @SessionScoped f
; So really nothing to worry about.
>
> LieGrue,
> strub
>
>
>
>
> - Original Message -
> > From: "Howard W. Smith, Jr."
> > To: MyFaces Discussion
> > Cc:
> > Sent: Wednesday, November 21, 2012 11:29 AM
> > Subject: Re: Migration
consorts.
LieGrue,
strub
- Original Message -
> From: "Howard W. Smith, Jr."
> To: MyFaces Discussion
> Cc:
> Sent: Wednesday, November 21, 2012 11:55 AM
> Subject: Re: Migration to TomEE/CDI complete, regression testing,
> ViewAccessScoped
>
>
rom: "Howard W. Smith, Jr."
> To: MyFaces Discussion
> Cc:
> Sent: Wednesday, November 21, 2012 11:29 AM
> Subject: Re: Migration to TomEE/CDI complete, regression testing,
> ViewAccessScoped
>
>T he most users that will be using the app concurrently is 4 to 5 users
Thanks Gerhard, will take a look.
Honestly, @SessionScoped fits the current design of my app the best, only
because I'm always returning null or void from bean to JSF
commandButton/Link actionListener="...", and also, I have index.xhtml which
is parent to all ui:include src="#{bean.page}".
Honest
hi howard,
you can have a look at [1] (e.g. slide #9)
the mentioned public application is using codi scopes like
@ViewAccessScoped without any performance and/or memory issue.
regards,
gerhard
[1] http://os890.blogspot.co.at/2012/11/slides-apache-myfaces-universe.html
http://www.irian.at
Your
The most users that will be using the app concurrently is 4 to 5 users (my
family), and there are times that they are doing some 'heavy lifting'
(database retrievals/updates, as well as PDF files generated in memory and
printed/viewed/emailed/faxed, and occasional data push to Google Calendar
via G
Can i ask you how much users serves your app?
Currently our app takes only 20mb session size with 200 (or 100, can't
remember exactly) concurrent users and we don't use that much
View(Access)Scoped beans.
2012/11/21 Howard W. Smith, Jr.
> Thomas,
>
> Well, for now, I opt to do/use CDI @RequestSc
Thomas,
Well, for now, I opt to do/use CDI @RequestScoped, ASAP, since production
box/server is running Windows 2003 Server, where 4GB RAM is max...shaking
my head. I'm sure we will upgrade when necessary, but right now that app is
lighting fast now with Glassfish 3.1.2.2 and MyFaces Core 2.1.9 an
Howard, there is nothing against ViewScoped/ViewAccessScoped.
But many data in ViewScoped/ViewAccessScoped leads to high memory usage, so
it's better to use RequestScoped if possible.
2012/11/21 Howard W. Smith, Jr.
> I'd like to take time to thank you all that helped me migrate from
> Glassfish
13 matches
Mail list logo
