HOW-TO : Mail session and authentication password

2004-06-17 Thread Q\. Werty
How can I declare a JavaMail Session in server.xml with
AUTHENTICATION informations?
It's OK for some properties (mail.smtp.port|from|user|auth)
but never found a way to indicate PASSWORD.


Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,34€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: HOW-TO : Mail session and authentication password

2004-06-17 Thread Q\. Werty
OK, thanks for you response. I've not understood how you
specify/pass your SMTPAuthenticator from JNDI resources.

What i want, is to be able to specify my SMTP password FROM
SERVER.XML and not from application (like JDBC resources). Is
your SMTPAuthenticator build by the application (and therefore
password is provided by the application) or build par the
contenair (and password is mentionned)?


 Hi.

 I extended an javax.mail.Authenticator to set username and
password for SMTP
 authentication:

   private static class SMTPAuthenticator extends Authenticator
   {
   String username, password;
   SMTPAuthenticator( String username, String password )
   {
   this.username = username;
   this.password = password;
   }
   public PasswordAuthentication getPasswordAuthentication()
   {
   return new PasswordAuthentication( username,
 password );
   }
   }


 You then set mail.smtp.auth property to true

 When constructing the MimeMessage, use a javax.mail.Session
object created
 using a Properties instance (with your properties set) and
the instance of
 the Authenticator (as above) that has the username and
password set.

 Hope that helps

 Carl


 -Original Message-
 From: Q. Werty [mailto:[EMAIL PROTECTED]
 Sent: 17 June 2004 05:02 PM
 To: tomcat-user
 Subject: HOW-TO : Mail session and authentication password


 How can I declare a JavaMail Session in server.xml with
AUTHENTICATION
 informations? It's OK for some properties
(mail.smtp.port|from|user|auth)
 but never found a way to indicate PASSWORD.


 Accédez au courrier électronique de La Poste :
www.laposte.net ;
 3615 LAPOSTENET (0,34€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)





-
 To unsubscribe, e-mail:
[EMAIL PROTECTED]
 For additional commands, e-mail:
[EMAIL PROTECTED]


-
 To unsubscribe, e-mail:
[EMAIL PROTECTED]
 For additional commands, e-mail:
[EMAIL PROTECTED]
 
 

Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,34€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re:Reloading an application non-interactively

2003-01-14 Thread Q. Werty
I agree ...


 On 13 Jan 2003 at 17:35, Q. Werty wrote:
 
  Try this :
  http://admin:password@localhost/manager/reload?path=/myapp
  
  Be aware : username and password can be catched on the 
wire and
  in log files ...
 
 It doesn't make a difference, whether the name and password 
are 
 put into the URL or into the dialog box. The browser 
translates 
 it into a proper HTTP authentication header. At least that's 
 what I tested. And it makes sense that way.
 
 The only difference: third persons could get to know the 
name 
 and password watching over the shoulder  
 O O
  |
 ---
 
 Andreas
 
 
  
  
   All, I would like to reload an application non-
  interactively.  I do not
   want to use Ant to do this because it will not be 
installed 
  on my target
   system. Instead I'd rather use a URL.   That is, I would 
  like to be able
   to enter the username and password as parameters to the 
URL, 
  not in the
   login dialog.
   
   It should look something like:
 
   http://localhost/manager/reload?path=/myapp;?
  username=admin?password=
   passwd
   
   Does anyone know how to do this?  Or is there another 
way to 
  reload
   something non-interactively (and not using Ant)?
   
   Thanks.
   Mary
   
 
 
 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
 
 

Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




JK2, JkUriSet and virtual hosting

2003-01-13 Thread Q. Werty
Hi,

I'am facing a problem with JK2 and virtual hosting.
Configuration : Tomcat 4.1.18/Apache 2.0.43/JK2 2.0.2/Windows 
2000 SP3.

As said in previous messages and in some documentation, it's 
possible to configure URI mapping with JK2 in Apache 
httpd.conf file (as with mod_jk). There exist JkUriSet to do 
this.
This directive work well, except when use with virtual host 
and same context. It seems that JkUriSet directive doesn't  
include hostname in internal configuration.
Does anyone has encountered same problem or does anyone knows 
how to resolve it?

Thanks in advance for any response.

 Following a longer explanation of the problem ===

Let's say I've got a /samples context in www.srv1.com and 
www.srv2.com host (correctly defined in Tomcat and Apache).
I defined two workers for JK2 (local_1 and local_2). I put the 
following directive in httpd.conf : 

VirtualHost *
ServerName www.srv1.com
#... others directives for this host

Location /samples
JkUriSet worker ajp13:local_1
/Location
/VirtualHost


VirtualHost *
ServerName www.srv2.com
#... others directives for this host

Location /samples
JkUriSet worker ajp13:local_2
/Location
/VirtualHost

= Results : all /samples URL are forwared to local_2, even 
requests to www.srv1.com.

Some remarks :
1. this configuration, all in workers2.properties with 
[uri:...] and without JkUriSet work very well.
2. when requesting /JkStatus, it appear that only the JkUriSet 
directive by context is used, and WITHOUT hostname


Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re:Reloading an application non-interactively

2003-01-13 Thread Q. Werty
Try this :
http://admin:password@localhost/manager/reload?path=/myapp

Be aware : username and password can be catched on the wire 
and in log files ...


 All, I would like to reload an application non-
interactively.  I do not
 want to use Ant to do this because it will not be installed 
on my target
 system. Instead I'd rather use a URL.   That is, I would 
like to be able
 to enter the username and password as parameters to the URL, 
not in the
 login dialog.
 
 It should look something like:
   
 http://localhost/manager/reload?path=/myapp;?
username=admin?password=
 passwd
 
 Does anyone know how to do this?  Or is there another way to 
reload
 something non-interactively (and not using Ant)?
 
 Thanks.
 Mary
 
 
 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
 
 

Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




mod_jk2 and shm explanations

2002-12-17 Thread Q. Werty
I'm experiencing Tomcat-4.1.17/mod_jk2/Apache-2.0.43/Windows-
2000.
After some difficulties, the whole configuration seems to be OK 
but I haven't understood all what I've done ...!
Particulary, in workers2.properties, [shm] component is still 
obscur to me and documentation il very poor on this subject.

So, does anyone can explain me :
- what is exactly the fonction of this module
- what kind of data is written in shm file?
- which file size should I configure (actually 100 but 
don't know why ...)?

Thanks in advance for any response.

Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Admin webapp bug with datasource?

2002-12-17 Thread Q. Werty
I'am facing with a problem in admin application.

I added manually a datasource in server.xml with a custom 
factory (some extensions to DBCP).
Then I went to admin application, and when I asked for this 
datasource with custom factory, admin application responded 
with a error (driverClassName missing, which is right, because 
my custom factory configure elsewhere the driver ...)

I think it would be good if admin application accept custom 
factory in datasource (and obviously in this cas doesn't enable 
more configuration in this datasource other than factory class 
name).

Is is a bug?

Accédez au courrier électronique de La Poste : www.laposte.net ; 
3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Context management and virtual host

2002-08-26 Thread Q. Werty

I'am looking for a way to manage all contexts installed on my
server.
I've got numerous virtual hosts and I'like NOT to install
manager context in all virtual hosts. How can I do?
- Is it possible to install a cross-host context in Tomcat?
- I saw the administration interface in Tomcat 4.1 beta. It's a
very great work, this interface enable to see/add/remove all
contexts accross all virtual hosts. I thought it was what I was
looking for but apparently there's nothing to start/stop/reload
context. Is it planned for final version?

Thanks in advance for any response

Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Context management and virtual host

2002-08-26 Thread Q. Werty

I agree there's no problem with installing the manager
application in each virtual host. I just don't want to do this
because I don't want to publish this context to anyone, even
with credentials.
I would be ready to this on our production server if I could
restrict manager context access to some IP adresses (127.0.0.1
for exemple).
== Is it possible? (if not, what about thinking of this in
future release?)



 There is no current support for a manager webapp that works
cross-host.
 The people I know using multiple virtual hosts haven't had
any problems
 with the notion of installing manager in each host (usually
with a unique
 username/password if you allow the virtual host users to
manage their own
 webapps).

 Admin webapp support for contexts is primarily for tweaking
existing
 config properties.  I view manager as the standard mechanism
for dynamic
 starting and stopping of webapps, in addition to deploying,
undeploying,
 and reloading.  Although the user interface of manager is
quite limited,
 it is expressly designed to be used by tools -- such as the
Ant custom
 tasks included in Tomcat 4.1, and the version of deploytool
shipped with
 the JWSDP http://java.sun.com/webservices/.

 People building plugins for IDEs should really be integrating
support for
 manager commands instead of trying to embed Tomcat inside
their
 environments.  They'd find it a lot easier.

 Craig


 On Mon, 26 Aug 2002, Q. Werty wrote:

  Date: Mon, 26 Aug 2002 16:42:32 +0200
  From: Q. Werty [EMAIL PROTECTED]
  Reply-To: Tomcat Users List [EMAIL PROTECTED]
  To: [utf-8] tomcat-user [EMAIL PROTECTED]
  Subject: Context management and virtual host
 
  I'am looking for a way to manage all contexts installed on
my
  server.
  I've got numerous virtual hosts and I'like NOT to install
  manager context in all virtual hosts. How can I do?
  - Is it possible to install a cross-host context in
Tomcat?
  - I saw the administration interface in Tomcat 4.1 beta.
It's a
  very great work, this interface enable to see/add/remove all
  contexts accross all virtual hosts. I thought it was what I
was
  looking for but apparently there's nothing to
start/stop/reload
  context. Is it planned for final version?
 
  Thanks in advance for any response
 
  Accédez au courrier électronique de La Poste :
www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68
13 50 (0,34€/mn)
 
 
 
 
  --
  To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
  For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
 
 


 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]



Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: Context management and virtual host

2002-08-26 Thread Q. Werty

OK, I haven't saw this. Thanks a lot

 Use the Remote Address Valve

 Context path=/manager 
   Valve
className=org.apache.catalina.valves.RemoteAddrValve
 allow=127.0.0.1 /
 /Context

 More info is here -
 http://jakarta.apache.org/tomcat/tomcat-4.0-
doc/config/valve.html

 - Andrew

  -Original Message-
  From: Q. Werty [mailto:[EMAIL PROTECTED]]
  Sent: Monday, August 26, 2002 11:48 AM
  To: tomcat-user
  Subject: Re: Context management and virtual host
 
 
  I agree there's no problem with installing the manager
  application in each virtual host. I just don't want to do
this
  because I don't want to publish this context to anyone,
even
  with credentials.
  I would be ready to this on our production server if I
could
  restrict manager context access to some IP adresses
(127.0.0.1
  for exemple).
  == Is it possible? (if not, what about thinking of this in
  future release?)
 
 
 
   There is no current support for a manager webapp that
works
  cross-host.
   The people I know using multiple virtual hosts haven't had
  any problems
   with the notion of installing manager in each host
(usually
  with a unique
   username/password if you allow the virtual host users to
  manage their own
   webapps).
  
   Admin webapp support for contexts is primarily for
tweaking
  existing
   config properties.  I view manager as the standard
mechanism
  for dynamic
   starting and stopping of webapps, in addition to
deploying,
  undeploying,
   and reloading.  Although the user interface of manager
is
  quite limited,
   it is expressly designed to be used by tools -- such as
the
  Ant custom
   tasks included in Tomcat 4.1, and the version of
deploytool
  shipped with
   the JWSDP http://java.sun.com/webservices/.
  
   People building plugins for IDEs should really be
integrating
  support for
   manager commands instead of trying to embed Tomcat inside
  their
   environments.  They'd find it a lot easier.
  
   Craig
  
  
   On Mon, 26 Aug 2002, Q. Werty wrote:
  
Date: Mon, 26 Aug 2002 16:42:32 +0200
From: Q. Werty [EMAIL PROTECTED]
Reply-To: Tomcat Users List tomcat-
[EMAIL PROTECTED]
To: [utf-8] tomcat-user tomcat-
[EMAIL PROTECTED]
Subject: Context management and virtual host
   
I'am looking for a way to manage all contexts installed
on
  my
server.
I've got numerous virtual hosts and I'like NOT to
install manager
context in all virtual hosts. How can I do?
- Is it possible to install a cross-host context in
  Tomcat?
- I saw the administration interface in Tomcat 4.1 beta.
  It's a
very great work, this interface enable to
see/add/remove all
contexts accross all virtual hosts. I thought it was
what I
  was
looking for but apparently there's nothing to
  start/stop/reload
context. Is it planned for final version?
   
Thanks in advance for any response
   
Accédez au courrier électronique de La Poste :
  www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92
68
  13 50 (0,34€/mn)
   
   
   
   
--
To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
   
   
  
  
   --
   To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
   For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
  
  
 
  Accédez au courrier électronique de La Poste :
  www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn)  ; tél : 08
92
  68 13 50 (0,34€/mn)
 
 
 
 
  --
  To unsubscribe, e-mail:
  mailto:tomcat-user- [EMAIL PROTECTED]
  For
  additional commands,
  e-mail: mailto:[EMAIL PROTECTED]
 


 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]



Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Context management and virtual host

2002-08-26 Thread Q. Werty

OK, thanks a lot too.



 On Mon, 26 Aug 2002, Q. Werty wrote:

  Date: Mon, 26 Aug 2002 17:48:10 +0200
  From: Q. Werty [EMAIL PROTECTED]
  Reply-To: Tomcat Users List [EMAIL PROTECTED]
  To: [utf-8] tomcat-user [EMAIL PROTECTED]
  Subject: Re: Context management and virtual host
 
  I agree there's no problem with installing the manager
  application in each virtual host. I just don't want to do
this
  because I don't want to publish this context to anyone, even
  with credentials.
  I would be ready to this on our production server if I could
  restrict manager context access to some IP adresses
(127.0.0.1
  for exemple).
  == Is it possible? (if not, what about thinking of this in
  future release?)
 

 Check out the Request Filters section on:

   http://jakarta.apache.org/tomcat/tomcat-4.1-
doc/config/context.html

 Craig


 
 
   There is no current support for a manager webapp that
works
  cross-host.
   The people I know using multiple virtual hosts haven't had
  any problems
   with the notion of installing manager in each host
(usually
  with a unique
   username/password if you allow the virtual host users to
  manage their own
   webapps).
  
   Admin webapp support for contexts is primarily for
tweaking
  existing
   config properties.  I view manager as the standard
mechanism
  for dynamic
   starting and stopping of webapps, in addition to
deploying,
  undeploying,
   and reloading.  Although the user interface of manager
is
  quite limited,
   it is expressly designed to be used by tools -- such as
the
  Ant custom
   tasks included in Tomcat 4.1, and the version of
deploytool
  shipped with
   the JWSDP http://java.sun.com/webservices/.
  
   People building plugins for IDEs should really be
integrating
  support for
   manager commands instead of trying to embed Tomcat inside
  their
   environments.  They'd find it a lot easier.
  
   Craig
  
  
   On Mon, 26 Aug 2002, Q. Werty wrote:
  
Date: Mon, 26 Aug 2002 16:42:32 +0200
From: Q. Werty [EMAIL PROTECTED]
Reply-To: Tomcat Users List tomcat-
[EMAIL PROTECTED]
To: [utf-8] tomcat-user tomcat-
[EMAIL PROTECTED]
Subject: Context management and virtual host
   
I'am looking for a way to manage all contexts installed
on
  my
server.
I've got numerous virtual hosts and I'like NOT to
install
manager context in all virtual hosts. How can I do?
- Is it possible to install a cross-host context in
  Tomcat?
- I saw the administration interface in Tomcat 4.1 beta.
  It's a
very great work, this interface enable to
see/add/remove all
contexts accross all virtual hosts. I thought it was
what I
  was
looking for but apparently there's nothing to
  start/stop/reload
context. Is it planned for final version?
   
Thanks in advance for any response
   
Accédez au courrier électronique de La Poste :
  www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92
68
  13 50 (0,34€/mn)
   
   
   
   
--
To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
   
   
  
  
   --
   To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
   For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
  
  
 
  Accédez au courrier électronique de La Poste :
www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68
13 50 (0,34€/mn)
 
 
 
 
  --
  To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
  For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
 
 


 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]



Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]