My understanding of programming restrictions is that reading or writing to a file is not portable across EJB2 compliant servers. This makes it very difficult to use XML configuation files either of your own for complex business logic (where env-entries are not suffuciently complex) or for the use of something like jakarta commons-validator framework where you would have to write
InputStream in = getClass().getResourceAsStream("validator.xml");
to get the validation rules.
Is this programming restriction definitive and does anyone have any thoughts on it.
The use of I/O within the business logic of the Enterprise Java Bean
is not advisable
Say for example if you want to form a jar file on the fly and publish the information to a file and store it in a file system...then it is better to go for Servlets.
But in certain cases...were you are developing components for a major system, where it is deployed in multiple location.Definetly we have to maintain...different configuration...like Report Server, Security Certs... and many other things.In that case we can use a separate XML and use parser to parse the information.
SCJP SCWCD SCBCD <br /> <br />what u do in life echos in eternity!