Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » ServerTools (WTP) » Web tools, Tomcat and JNDI configuration.
Web tools, Tomcat and JNDI configuration. [message #53457] Tue, 16 November 2004 12:13 Go to next message
Eclipse UserFriend
Originally posted by: michele.l.evinco.it

Hi World!,

I' ve a simple question.
Where i can set JNDI resources in Web tools.
Now, with sysdeo plugin, i configure these resources in the file
name-application.xml in conf/Catalina/localhost.
With webtools, when i start the server, the plug-in reset my file with
the base Context information:

<Context docBase="C:/Progetti/Java/Nus/WebContent" path="/Nus"
reloadable="true">
</Context>

so, i loose all the information about JNDI resources every time i start
up the server.

I've try to write these data in server.xml but when the server start it
create a new configuration file with the base Context information.

The only way that i've found to work with JNDI is :

1. start server.
2. edit the name-application.xml in conf/Catalina/localhost when
the server is up.


Do someone have try to work with JNDI? if yes, there is a simple way to
configure it in the server with web tools?

Thanks
Bye
Re: Web tools, Tomcat and JNDI configuration. [message #54875 is a reply to message #53457] Mon, 29 November 2004 20:48 Go to previous messageGo to next message
Tim deBoer is currently offline Tim deBoerFriend
Messages: 71
Registered: July 2009
Member
Hi Michele,

4 of the Tomcat configuration files are stored inside WTP so that they can
be configured using the server editor. On publish, if you have the "Run
modules directly from the workspace..." turned off, these files are
published out to the Tomcat installation.

To get around this, go to the Server preferences and check the "Create
server resources in the workspace" option. When you create a new Tomcat
server, these files will get created in the workspace instead of metadata,
and you can edit the files directly inside the workspace, and they'll
automatically be published out to Tomcat before running.
Web tools and OC4J [message #65925 is a reply to message #53457] Tue, 18 January 2005 12:53 Go to previous messageGo to next message
Karsten is currently offline KarstenFriend
Messages: 24
Registered: July 2009
Junior Member
Hi all,

I'm quite sure I will get beaten for stupidity after this mail but:

I'm using Eclipse 3.1M4 with WTP version M2 ??? maybe M3 I deleted the
zip file and have not been able to discover the version of WTP... the
pluginlist shows 1.0.0...

To my Question... everything seems to work fine with tomcat... but I
don't want to use catalina... I need an working oc4j version... so I
copied the bea-serverfile to oc4j.server in:
${eclipse.home}/plugins/org.eclipse.jst.server.generic.core_ 1.0.0
after that I edited the file to the values I think should fit for oc4j
(start, shutdown and un-/deploly options) I'm quite sure my server-specs
will work but it doesn't even show up in the "Generic Server Runtime"
list and the "search for new server runtime" doesn't even recognize
oc4j.jar as a runtime...

So my question is:
How can I add a new server runtime by hand?!

Thnx in advance...
Re: Web tools, Tomcat and JNDI configuration. [message #77791 is a reply to message #54875] Sun, 27 February 2005 21:15 Go to previous messageGo to next message
Christian is currently offline ChristianFriend
Messages: 4
Registered: July 2009
Junior Member
Tim deBoer wrote:
> Hi Michele,
>
> 4 of the Tomcat configuration files are stored inside WTP so that they can
> be configured using the server editor. On publish, if you have the "Run
> modules directly from the workspace..." turned off, these files are
> published out to the Tomcat installation.
>
> To get around this, go to the Server preferences and check the "Create
> server resources in the workspace" option. When you create a new Tomcat
> server, these files will get created in the workspace instead of metadata,
> and you can edit the files directly inside the workspace, and they'll
> automatically be published out to Tomcat before running.
>
>
Hi,

i still have this problem,
i have created a new tomcat 5.5 server in the workspace, with the above
mentioned option checked. but eclipse still loads the server.xml file in
the ..\workspace\.metadata\.plugins\org.eclipse.wst.server.core dir.
changing the argument in the server run-configuration to the server.xml
in the workspace is useless to, because eclipse changes this value
automatically back to the metadata\plugins-path when starting the server.
Re: Web tools, Tomcat and JNDI configuration. [message #78083 is a reply to message #77791] Mon, 28 February 2005 14:36 Go to previous message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1354
Registered: July 2009
Senior Member
WTP M3 now includes support for META-INF/context.xml. If present in
your web project, the children of the <context> element in this file
will be included in the <context> written to the server.xml when the
publish operation is performed. These children will not be visible in
the server.xml(s) found under the Servers project, but will be present
in the server.xml from which Tomcat is run. For details, see:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=82812

Cheers,
Larry

Christian wrote:
> Tim deBoer wrote:
>
>> Hi Michele,
>>
>> 4 of the Tomcat configuration files are stored inside WTP so that they
>> can
>> be configured using the server editor. On publish, if you have the "Run
>> modules directly from the workspace..." turned off, these files are
>> published out to the Tomcat installation.
>>
>> To get around this, go to the Server preferences and check the "Create
>> server resources in the workspace" option. When you create a new Tomcat
>> server, these files will get created in the workspace instead of
>> metadata,
>> and you can edit the files directly inside the workspace, and they'll
>> automatically be published out to Tomcat before running.
>>
>>
> Hi,
>
> i still have this problem,
> i have created a new tomcat 5.5 server in the workspace, with the above
> mentioned option checked. but eclipse still loads the server.xml file in
> the ..\workspace\.metadata\.plugins\org.eclipse.wst.server.core dir.
> changing the argument in the server run-configuration to the server.xml
> in the workspace is useless to, because eclipse changes this value
> automatically back to the metadata\plugins-path when starting the server.
Previous Topic:servlet wizard error
Next Topic:Webtools an Mac OS X?
Goto Forum:
  


Current Time: Wed Jun 26 19:24:50 GMT 2024

Powered by FUDForum. Page generated in 0.03973 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top