Hey guys,
I found the solution.
I had import the wrong Session-class.
So long,
Sebastian
> Hey Team,
>
> I have some problems with the example of JNDI Resources "JavaMail
> Sessions".
>
> I get the error: The constructor MimeMessage(Session) is undefined
>
> A extract from the HOW-TO page:
Hey Team,
I have some problems with the example of JNDI Resources "JavaMail
Sessions".
I get the error: The constructor MimeMessage(Session) is undefined
A extract from the HOW-TO page:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
Session se
I'm out then. I'm fine with the way tomcat operates and don't feel
anything in the way context xml files are associated with webapps is
ambiguous. It's really simple:
1. If you just want to deploy a webapp and don't need to define any
resources like db pools, just drop the webapp in the weba
2008/9/3 David Smith <[EMAIL PROTECTED]>:
> There's an implicit association based on the context path. myWebApp.xml in
> conf/Catalina/localhost is implicitly associated with the webapp myWebApp in
> the webapps directory, whether it be as a .war or expanded folder.
Yes, I agree that the docs rea
> From: Paul Pepper [mailto:[EMAIL PROTECTED]
> Subject: Re: Problem with JNDI environment entry resources
>
> Besides, I don't see any other documented way of associating
> each application with its associated element within
> server.xml.
Because you're not
There's an implicit association based on the context path. myWebApp.xml
in conf/Catalina/localhost is implicitly associated with the webapp
myWebApp in the webapps directory, whether it be as a .war or expanded
folder.
Illegal may be a strong word -- it implies that tomcat will flat out
reje
> I'll have to check the docs again. However, docBase is only legal when the
> webapp is stored outside of the
> appBase directory. Otherwise, you risk ending up with double deployment.
I don't see docBase described that way in the docs - at this moment
I'm referring to
http://tomcat.apache.or
contained within this transmission.
> Date: Wed, 3 Sep 2008 14:42:24 +0100
> From: [EMAIL PROTECTED]
> To: users@tomcat.apache.org
> Subject: Re: Problem with JNDI environment entry resources
>
> Martin,
>
> Thanks for the suggestion, though I think there may have
> From: Paul Pepper [mailto:[EMAIL PROTECTED]
> Subject: Re: Problem with JNDI environment entry resources
>
> Tomcat 6 docs states that docBase is a valid attribute
> in this situation.
I'll have to check the docs again. However, docBase is only legal when the
webapp is s
his transmission is of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>
>
>> Date: Wed, 3 Sep 2008 01:01:40 +0100
>> From:
From: Paul Pepper [mailto:[EMAIL PROTECTED]
>> Subject: Problem with JNDI environment entry resources
>>
>> Can anyone suggest what I might have missed?
>
> What happens if you follow the (strongly) recommended practice of not putting
> elements in server.xml? If you don&#x
necessarily endorse content contained within this transmission.
> Date: Wed, 3 Sep 2008 01:01:40 +0100
> From: [EMAIL PROTECTED]
> To: users@tomcat.apache.org
> Subject: Problem with JNDI environment entry resources
>
> Tomcat 6.0.18
> java version "1.6.0_06" (sun-jav
> From: Paul Pepper [mailto:[EMAIL PROTECTED]
> Subject: Problem with JNDI environment entry resources
>
> Can anyone suggest what I might have missed?
What happens if you follow the (strongly) recommended practice of not putting
elements in server.xml? If you don't want to
Tomcat 6.0.18
java version "1.6.0_06" (sun-java6-jdk on Ubuntu 8.04 i386)
I'm attempting to create environment entry resources, of type
java.lang.String, within conf/server.xml and access them from web
applications using JNDI. I've created a bare-bones test web app,
jndistring, with the following
Re: Problem with JNDI using a changed context root path
> >
> > Remember to move the corresponding context file as well, so move
> > conf/Catalina/localhost/mywebapp.xml to
> > conf/Catalina/localhost/ROOT.xml.
>
> The above .xml file is not always created; regardless
> From: Felix Schumacher [mailto:[EMAIL PROTECTED]
> Subject: Re: Problem with JNDI using a changed context root path
>
> Remember to move the corresponding context file as well, so move
> conf/Catalina/localhost/mywebapp.xml to
> conf/Catalina/localhost/ROOT.xml.
The abov
On Mon, April 21, 2008 10:55 am, Stefan Dirschnabel wrote:
> Hi,
>
> I experience a problem changing the context root path of my Tomcat 5.5.
> I deploy my application using a war file. Because the Application can
> now only be accessed using www.url.de/warfilename I changed the context
> root of my
Hi,
I experience a problem changing the context root path of my Tomcat 5.5.
I deploy my application using a war file. Because the Application can
now only be accessed using www.url.de/warfilename I changed the context
root of my Tomcat. I just want the user to enter www.url.de to access
the applic
Hallo
I solved the problem. It is embarrasing to me but in some cases I didn't
close the connection. So therefore I had this problem.
Thanks.
2006/2/3, Hans Sowa <[EMAIL PROTECTED]>:
>
> Hi
>
> I'm working on a webapplikation using JNDI to lookup for a database
> connection. Actually it works fo
Hi
I'm working on a webapplikation using JNDI to lookup for a database
connection. Actually it works for several times and then it stopps and I
don't get an connection. I analysed it and found out that Method
getConnnection has a problem.
Here is my code:
protected Connection lookupJNDIConnectio
20 matches
Mail list logo
