Hi,
I have question around entityManager.flush().
Is it ok to call multiple times? Or will there be any performance issue.
My case is, I have a timer service which executes periodically where I
create a database entity using a dao object using entityManager.persist(),
after that I also call
Hi there Radhakrishna,
On 19/05/2014 08:15, Radhakrishna Kalyan wrote:
Hi,
I have question around entityManager.flush().
Is it ok to call multiple times? Or will there be any performance issue.
Every time you hit the the database you will take a performance hit back
- How much is impossible
Hi Nina,
Are you sure the attribute it written correctly as 'factory-name', looks
like you are using just 'factory'. Maybe a line break slipped in there or
the dash '-' was not correct?
Andy.
-
--
Andy Gumbrecht
http://www.tomitribe.com
agumbre...@tomitribe.com
Hello I am developing an Arquillian extension and I need a way to know in
which port has been deployed an application. When running as client, there
is no problem because I can get the HTTPContext and get all the
information, but when running within container, this information is not
available.
Interesting question and answer.
Per my 2+ year experience with Java EE 6, in my app, i used NetBeans to
develop my JPA session facade (@EJB JPA DAO) classes, including abstract
class. In the abstract class, in the create and edit methods, I did add
flush(), so after every create and edit JPA
I think System.getProperty(tomee.http) would work?
Best for you is to put this port from client side (HTTPContext) in
yourextension.properties in the war then get it from TCCL.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn:
Hmm, this sounds wrong, Arquillian starts the container before creating
the archive. Is it a cache archive appender? Maybe use an archive processor
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github:
Well I think that arquillian creates the httpcontext when he knows which
http context is going ti be deployed (war file) and in auxiliaryappender
you are creating that war file so i think that for this reason there is no
httpcontext. Maybe protocolmetadata will work but not sure
El dilluns, 19
