found back how to get the error with the default settings
- this error is in apache-tomee/logs/localhost*.log but not in the console
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
Is there another configuration file that controls tomee
ManagedConnectionFactories? I'm just using ra.xml but am starting to think
their could be another that configures container specific pool
implementations. For example, weblogic has a weblogic-ra.xml file that you
can use to configure pool
Really and why? I usually don't refer there but I will confirm. I've seen
other system out println in console.
On Nov 26, 2012 3:22 AM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
found back how to get the error with the default settings
- this error is in apache-tomee/logs/localhost*.log
not sure i got your question
yes by default the error is in localhost*.log because the logger in cause
is not defined so it delegates to parent loggers
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog:
I can't see in the documentation how to configure a custom JCA resource. Can
you provide an example? I don't know which resource type i should use. I
tried the actual class name but got an error.
My test case code...
@BeforeClass
public static void beforeClass() throws
Is there a TomEE Example on the TomEE Examples page that shows how to
use/define the logger (I assume that's JULI). I saw the WTP and JULI
example, but I don't know if that is applicable to me or not.
On Mon, Nov 26, 2012 at 8:36 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
not sure i
As per your response in your email below, how can I get HttpSessionListener
system.out.println messages to show in the console?
I just logged into my app, undeployed the web app from TomEE, and the
following is in the console. When I use Glassfish, my session listener
system.out.println msgs show
it is shown by default
what is swallowed are the exception and i explained you how to activate them
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn:
Okay, you mentioned the following:
for wtp you need to add 2 properties but i guess that's the doc you saw
(that's done by default using tomcat scripts to startup it)
I had to google 'wtp', and I see that is eclipse. I'm not an eclipse user,
I use NetBeans. If you want NetBeans/Glassfish
we fixed issued we had with netbeans some versions ago,
but i think users were using maven as base project
not sure about other cases
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
I think you're right, because right off the bat, when I first started using
TomEE, NetBeans (v7.2) shows me localhost log and catalina log in separate
(NetBeans) output console/panes.
This is all working well for me, too. so, maybe there is no need to update
this TomEE document, and you can
Hmmm, I guess you are referring to conf/logging.properties.
On Mon, Nov 26, 2012 at 10:27 AM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
it is shown by default
what is swallowed are the exception and i explained you how to activate
them
*Romain Manni-Bucau*
*Twitter: @rmannibucau
On Nov 26, 2012, at 8:36 AM, Howard W. Smith, Jr. smithh032...@gmail.com
wrote:
I think you're right, because right off the bat, when I first started using
TomEE, NetBeans (v7.2) shows me localhost log and catalina log in separate
(NetBeans) output console/panes.
This is all working well
Wow, David, that page is not loading in my Google Chrome browser for
whatever reason. I'm willing to contribute to such pages and share
information from a 'user' perspective as I am a user of TomEE. :)
I would like to and plan to contribute to such pages (applicable to my use
of TomEE) as time
Hmmm, was just able to access that page, but the page is only authorized to
be edited by 'committers'. :(
On Mon, Nov 26, 2012 at 11:38 PM, Howard W. Smith, Jr.
smithh032...@gmail.com wrote:
Wow, David, that page is not loading in my Google Chrome browser for
whatever reason. I'm willing to
Okay, I see this warning even on startup of container. see below.
Evidently, nothing to be concerned about, but for some reason, TomEE WARNS
developer about this.
*1st occurrence*
INFO: using context file
C:\Users\Public\NetBeansProjects\mcms\build\web\META-INF\context.xml
Nov 27, 2012 1:20:58 AM
16 matches
Mail list logo
