I'm trying to get you to tell us what exactly your problem is. where are you stuck? what don't you know/understand how to do?
Further, i'm trying to help you break down your problem into small, more manageable problems. you started by saying "I don't know how to do this project". after some back and forth, it turns out you do know how to do some of it, but it is still not clear (at least to me) where you are stuck. Each time I ask "Did you do this", you reply with "yes, i know how to do that, and now I'm stuck".
You apparently know how to create a DTD. you apparently know how to create xml. Do you know how to compile a java program? Do you know if you have a JDK? do you know how to run a program once it is compiled?
you need to tell us SPECIFICALLY where you need help.
There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors
posted 9 years ago
I know compiling java and runing java program.
classpath,java-home and path is set in my system.
now the question is which is package I should use , and what is the easy way.
We don't know... do you have a domain registered? Then use that. If not, use something that describes what you are doing.
Actually reply was given for Mr. Fred Rosenberger's reply.
Sorry, I didn't understand that you and Fred was having a private conversation on an open channel.
gyan kumar wrote:
fred rosenberger wrote:are you asking about what your package statement should be and how to set up your directories?
yes Mr. Fred Rosenberger.
Will javax.xml package helpful?
Yes, in javax.xml you find classes that is helpful when working with XML in Java.
However, if you are asking in what package to put YOUR developed files, javax.xml is not the package to use, since that is used by Oracle in the Java API. You may put your files and classes in any package that you like. The commonly used standard is to have a registered domain that you control as base and then add a project or product specific sub-package to it. Under that, there are some patterns that you could use, like have all the specifications (interface and abstract classes) in one package and implementations in another.