Mailing-List: contact users-help@tomee.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@tomee.apache.org
Received-SPF: pass (nike.apache.org: domain of maxtorzito@gmail.com designates
 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1382269878.92746.YahooMailNeo@web28905.mail.ir2.yahoo.com>
References: 
 <CAPyf0gf2qdk0ZrTU6i2sfYU_xXrSk2_413td511uDJyML2AF2w@mail.gmail.com>
	<CACLE=7On-+VCRsHMKOH9Psr0ZTTXv6Qm93mbWaf34z=GNyozfQ@mail.gmail.com>
	<CAPyf0gdrBqV4huR9-9=fDTpRp_FYqabSee02hy+ZUoNwxihyHg@mail.gmail.com>
	<CACLE=7MCHWTmX9UtBcESCxVW_qu_Q+WtfDCrFi8ANWk6FWfLdw@mail.gmail.com>
	<CAPyf0gfpoBDvCLBYRcK-HuyGUnpYj1KhwH+HQc958H9eUkZkWg@mail.gmail.com>
	<CAPyf0geatLpPw5SuuPzdAf2RcT1X64zaxmE6DLYOJZRbs9uiAg@mail.gmail.com>
	<CACLE=7ORc=XVtKgeXzB++_470PHWhp3RH83rsR0y_Zoxobyv6g@mail.gmail.com>
	<1382167015.36881.YahooMailNeo@web28901.mail.ir2.yahoo.com>
	<CAGV1rDJHf3iD5ZAOUHxCjW29xKWTauD_EPGR2DCO--Tpi-FbnA@mail.gmail.com>
	<CACLE=7NzNzn18e=xduvGSVg8Kr3S3qZUPCBTDReMxeGLGMoe1Q@mail.gmail.com>
	<1382194175.59249.YahooMailNeo@web28902.mail.ir2.yahoo.com>
	<CAGV1rDL1BmG2ii7waVHNd6oz47HtO5oX6BqHWuBQ5UeqjdpOWg@mail.gmail.com>
	<1382211989.70533.YahooMailNeo@web28905.mail.ir2.yahoo.com>
	<CAGV1rDJsOrHWm5QC3AHJKCTn-y=EQ3VNkpjuYG4rpxCG21pyGA@mail.gmail.com>
	<CACLE=7NNbns8KcK6H7=fuAqqukRX3R7mQ8c4G_x9Xi+xmQ7hpQ@mail.gmail.com>
	<1382269878.92746.YahooMailNeo@web28905.mail.ir2.yahoo.com>
Date: Sun, 20 Oct 2013 11:04:07 -0500
Message-ID: 
 <CAPyf0gfhUsuf8cJkJ2VLPtJgF4rKUY8Liqdt_i=71sF+4H_8QA@mail.gmail.com>
Subject: Re: Entity cant be refreshed with new list values
From: =?ISO-8859-1?Q?Jos=E9_Luis_Cetina?= <maxtorzito@gmail.com>
To: users@tomee.apache.org
Content-Type: multipart/alternative; boundary=001a11c379ec413d9004e92e5158

--001a11c379ec413d9004e92e5158
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Responses inline.

El 20/10/2013 06:51, "Mark Struberg" <struberg@yahoo.de> escribi=F3:
>
> Romain, that's nowhere in the spec. Thus it must work. Really!

If this is true, what im doing wrong? Or this is openjpa or tomee issue?

>
> The only thing which is specified to be immutable are lists returned by
query.getResultList.
> That's the reason why you should not back a sortable h:dataTable by a
list you get from JPA directly.
> All other stuff is perfectly mutable.
>
> LieGrue,
> strub
>
>
>
>
> >________________________________
> > From: Romain Manni-Bucau <rmannibucau@gmail.com>
> >To: users@tomee.apache.org
> >Sent: Sunday, 20 October 2013, 10:00
> >Subject: Re: Entity cant be refreshed with new list values
> >
> >
> >Not really. An entity handles a state which can prevent it. Nothing
> >mandates it to work
> >
> >Le 20 oct. 2013 09:50, "Jos=E9 Luis Cetina" <maxtorzito@gmail.com> a =E9=
crit
:
> >
> >> What about using a detached entity?? The detached entity will work
like a
> >> DTO?
> >>
> >> From Real World Java EE Patterns (Adam Biem) 2009
> >> Problem
> >> The origin problem statement was: =93You want to transfer multiple dat=
a
> >> elements over a tier=94
> >> (
> >>
> >>
http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.htm=
l
> >> ).
> >> This particular problem was elegantly solved in Java EE 5 with
detachment
> >> of persistent entities. There is
> >> no need for the introduction of another class just for transferring th=
e
> >> entities data. JPA entities can
> >> implement a java.io.Serializable interface and be transferred between
> >> tiers, even remote ones.
> >> CMP 2.x entities weren=92t Serializable, the developer was forced to c=
opy
> >> their states to a remotely
> >> transferable structure=97the Transfer Object.
> >>
> >>
> >>
> >> 2013/10/19 Howard W. Smith, Jr. <smithh032772@gmail.com>
> >>
> >> > responses below...
> >> >
> >> > On Sat, Oct 19, 2013 at 3:46 PM, Mark Struberg <struberg@yahoo.de>
> >> wrote:
> >> >
> >> > > be careful with immediate=3Dtrue. You get all sorts of nasty side
> >> effects.
> >> > >
> >> > > see page 92 in
> >> > >
> >> >
> >>
http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pi=
tfalls%20in%20EE.pdf
> >> > >
> >> > >
> >> > I definitely agree and understand about immediate=3Dtrue, and guess
what, i
> >> > found it very useful to disable validation as instructed on page 92
of
> >> the
> >> > PDF file.
> >> >
> >> > clarification of my use/understanding:
> >> >
> >> > i am 'not' using immediate=3Dtrue, when i user is to select a row on
> >> > datatable, and then click commandbutton/link/menuitem, which does a
POST
> >> of
> >> > the selected row on the datatable, and bean uses the selected row to
> >> > prepare the UI for the next view that is 'rendered' via
> >> > ui:include=3D#{bean.page}. see below and keep reading, please.
> >> >
> >> >     <p:menuitem value=3D"Add" icon=3D"ui-icon ui-icon-circle-plus"
> >> >
> >> > actionListener=3D"#{pf_pointOfContactController.prepareCreate()}"
> >> >
 update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"/>
> >> >     <p:menuitem value=3D"Edit" icon=3D"ui-icon ui-icon-pencil"
> >> >
> >> > actionListener=3D"#{pf_pointOfContactController.prepareEdit()}"
> >> >
 update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"/>
> >> >     <p:menuitem value=3D"View" icon=3D"ui-icon-folder-open"
> >> >
> >> > actionListener=3D"#{pf_pointOfContactController.prepareView()}"
> >> >
 update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"/>
> >> >     <p:separator/>
> >> >     <p:menuitem value=3D"Copy to Ordered By" icon=3D"ui-icon
ui-icon-newwin"
> >> >
> >> > actionListener=3D"#{pf_pointOfContactController.copySelectedRows()}"
> >> >
 update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"/>
> >> >     <p:menuitem value=3D"Delete" icon=3D"ui-icon ui-icon-trash"
> >> >
> >> >
> >>
actionListener=3D"#{pf_pointOfContactController.confirmDeleteSelectedRows()=
}"
> >> >
 update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"/>
> >> >
> >> > but, for a readonly page that has commandbutton/links to render a ne=
w
> >> view,
> >> > based on the current @Entity that is held in the JSF controller/bean
> >> class,
> >> > i use immediate=3Dtrue without issue and I think it fits/meets the
> >> > occasion/requirement, because there is no need to do validation
phase or
> >> > update model values. see below. :)
> >> >
> >> >     <p:commandButton value=3D"Browse" icon=3D"ui-icon-search"
> >> immediate=3D"true"
> >> > update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"
> >> >
> >> >  actionListener=3D"#{pf_pointOfContactController.prepareList()}"/>
> >> >     <p:commandButton value=3D"Delete" icon=3D"ui-icon ui-icon-trash"
> >> > immediate=3D"true"
update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"
> >> >
> >> >  actionListener=3D"#{pf_pointOfContactController.confirmDelete()}"/>
> >> >     <p:commandButton value=3D"Edit" icon=3D"ui-icon ui-icon-pencil"
> >> > immediate=3D"true"
update=3D"#{pf_pointOfContactController.getAjaxUpdate()}"
> >> >
> >> >  actionListener=3D"#{pf_pointOfContactController.prepareEdit()}"/>
> >> >
> >>
> >>
> >>
> >> --
> >> -------------------------------------------------------------------
> >> *SCJA. Jos=E9 Luis Cetina*
> >> -------------------------------------------------------------------
> >>
> >
> >

--001a11c379ec413d9004e92e5158--