aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes jndi best practices Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "jndi best practices" Watch "jndi best practices" New topic
Author

jndi best practices

vijay shanker
Ranch Hand

Joined: Oct 26, 2007
Posts: 88
Hi friends,

I am in an issue with my web application. here is some description about that issue --> where should is put my JNDI properties file.

currently i have put that file in a working directory made for that tamcat in eclipse.

My problem is my development team is extended and every time i make some changes in the jndi file, i am forced to change and provide a copy of that file to all the developers.

i want to investigate where else can i save this file so, the change process will be stream lined.

i use SNV to share my project between team, and working directory is not shared.


Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Put it under source control and write a build script (also under source control) your team mates can use to deploy it.


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
vijay shanker
Ranch Hand

Joined: Oct 26, 2007
Posts: 88
hi paul,

this is what i am planing to do for this. But we currently not using any build tool. can you please suggest some good tool for our problem with source code support.

i tries to study and implement both ant and maven, but they are to complicated for me.

as they what modularity in the project. I also understand the need for modularity and it should have been there form start. But I did not go with because, when i started all this project.

How should i proceed to create a good web project.
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30764
    
156

vijay shanker wrote:i tries to study and implement both ant and maven, but they are to complicated for me.

They are the standard solutions and it would be wise to learn one. Ant and Maven can get extremely complicated, but the basics shouldn't be. As far as I know, Maven is easier if your projects are organized "the Maven way" otherwise Ant is. Since it sounds like you aren't following Maven's approach, I think you will find Ant easier to setup on your project.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
vijay shanker
Ranch Hand

Joined: Oct 26, 2007
Posts: 88
Thanks Jeanne Boyarsky,

In between i have created my whole project as a maven project. all dependency are added to a POM. I am also able to run this project in eclipse embbeded server.

Now i got some issues with tomcat-maven-plugin
as my project requires javax. activation jar and so is container.

So i need to find out a solution that will help me out to satisfy both the dependencies


 
It is sorta covered in the JavaRanch Style Guide.
 
subject: jndi best practices