Hi
We are adding TomEEMyFacesContainerInitializer manually. But it will not
get fire to the root app since we are deploying the root app before
registering the SCI.
So I manually added the TomEEMyFacesContainerInitializer SCI through the
META-INF/services/javax.servlet.ServletContainerInitilizer
Hi,
Check deployed el api bundles and protrcted domain of the one in Ast*
classes
Thanks for the help Romain. Yeah it caused due to some class resource
loading issues that we manually added from our side. That fix the issue.
Thanks a lot for the help :)
Best Regards
/Thusitha
2015-06-09 19:45
One thing about PasswordCipher, because you are planning to rework :) My
security team (which sometimes are a bit crazy) noticed me that this
interface deals with passwords as Strings. This can be a security problem
since Strings are immutable and not destroyed (they are pooled), so it can
be a
thank you
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/TomEE-1-7-2-JavaMail-Resource-tp4675216p4675236.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Hi I would like to share this experience with CDI and PasswordCipher:
If I do next code:
public class SecurePasswordCipher implements PasswordCipher {
@Inject
MasterPasswordProvider masterPasswordProvider;
}
And no MasterPasswordProvider implementation is provided, I get next
Go for it :) - not sure what's involved off the top of my head, but am
happy to help dig into the code.
Jon
On Wed, Jun 10, 2015 at 7:42 AM, Alex Soto asot...@gmail.com wrote:
Ok no problem at all because I will implement the logic I need as a JDK
service, but I think that will be great to
That's a good point!
Pre-side note/history: on a pure PasswordCipher aspect it was not an issue
until recently (j8 something) cause constant pool was not used/usable for
all strings.
On a pure technical aspect and our API: most of modern API use a String
(datasources, JavaEE API like
yeah, fully agree.
The few points which make PasswordCipher different are:
- they are prototype (short live instances)
- they are not bound to any application by default (so no cdi)
That said it shouldnt be hard to get a PasswordCipher which is actually a
cdi bridge one (ie we dont add cdi by
well before playing with config the idea is to know what happened, is the
network quality the cause for instance?
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn
Thank you for help!
BRM
2015-06-10 20:21 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
2015-06-10 11:17 GMT-07:00 Matej gma...@gmail.com:
Hi.
Maybe what i forgot to tell is that when looking at the database we see
many connections like that:
IDLE IN TRANSACTION, mayn (ALL)
Hi Matej
looks like a database issue for me (stateless pool is waiting for the
stateless trying to get the db connection to be released), hasnt the DB
connection be lost or something like that?
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
On Wed, Jun 10, 2015 at 1:18 PM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
Hi Matej
looks like a database issue for me (stateless pool is waiting for the
stateless trying to get the db connection to be released), hasnt the DB
connection be lost or something like that?
what is the
2015-06-10 10:59 GMT-07:00 Matej gma...@gmail.com:
Hi Romain.
We lookef for DB locks, but it's only SELECT and INSERT statements, which
should not cause locking on postgresql. And we also looked for locks using
postgresql debuging, analytics. So we suspected the network and the JDBC
driver,
Hi Romain.
We lookef for DB locks, but it's only SELECT and INSERT statements, which
should not cause locking on postgresql. And we also looked for locks using
postgresql debuging, analytics. So we suspected the network and the JDBC
driver, we did some TCP stack tuning, but also no major change.
2015-06-10 11:17 GMT-07:00 Matej gma...@gmail.com:
Hi.
Maybe what i forgot to tell is that when looking at the database we see
many connections like that:
IDLE IN TRANSACTION, mayn (ALL) transaction that are long running, waiting
for commit statemet which somehow doesn't happen.
And the
Yeah like a class you instantiate yourself or not cdi managed (like jpa
entities). Scanned but not managed.
Le 10 juin 2015 05:05, Alex Soto asot...@gmail.com a écrit :
Hi I would like to share this experience with CDI and PasswordCipher:
If I do next code:
public class SecurePasswordCipher
Hi
it shouldnt leak if you use 2 different EntityManagerFactories.
Can you share a project with tomee-maven-plugin sets up to reproduce it on
a public repository?
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github
Hi Romain,
thanks for the quick response! I'll need to set up a minimal sample
application that I can share - will get one underway.
Looks like it may be related to runtime enhancement - I tried running
manually enhancing the classes for both applications via PCEnhancer and the
error didn't
Hi,
we are encountering an OpenJPA problem when running two different versions
of the same web application under one instance of TomEE (version 1.7.2). The
problem only occurs when persistent fields have been added to a JPA entity
class in one version of the application but not in the other. When
https://issues.apache.org/jira/browse/TOMEE-1603
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau | Blog
http://rmannibucau.wordpress.com | Github https://github.com/rmannibucau |
LinkedIn https://www.linkedin.com/in/rmannibucau | Tomitriber
http://www.tomitribe.com
2015-06-11
20 matches
Mail list logo
