David Thielen wrote: > 3) I need to have a method called when the servlet first loads. Is a > listener the best way to do this? > What servlet? > 4) When using IE on an ASP application, there is a way to click on a word > document in the browser, it brings up Word to edit the document, and when > you save the document in Word, it uploads it back to the website. > > a. Is there a way to do this in the J2EE world? > I'm not aware that this has anything to do with J2EE. But let me know if it does, 'cuz we could probably use the same functionality. > b. And if not, what is the best way to provide similar functionality? I > dislike the idea that they save it locally and then need to browse for the > saved document to upload it - most people have no idea where their temporary > folder is. > Hack Word? WebDAV? > 5) Is there a way that the appserver can tell me what to use for logging? I > don't want my portal to use log4j if the rest of the app server is using > something else. > I guess that would depend on your appserver.
The Servlet API has two logging methods that I suppose you could use. http://java.sun.com/j2ee/sdk_1.3/techdocs/api/index.html But... I'd just use Log4J. A lot of components you'll probably be using use it too. Handy. > 6) I will have to create a jpg file that is displayed with some pages. I > want to delete the jpg when it is no longer needed. If the user hits refresh > on their browser, I still need it. Should I delete when the user's session > ends (timeout or logout)? > "Should" implies a level of obligation I'm uncomfortable with in this context. If you don't want it after the user's session has ended, then sure. If you only need it here and there, how high is the cost of the image generation (i.e. is the cost of always creating it to high?) What if you cached it (i.e. don't persist it to disk), retrieve it with a servlet (or action), then just let it go away when nobody uses it again? > 7) What do you think of hibernate? I have used it once and it seems to me > that it moves the work, but does not reduce it. > Compared to what? Does your application demand a full-blown ORM? There are plenty of other options (iBatis, straight JDBC, JDBC w/ Spring, Torque, etc.) Heck, I wrote a large intranet app. using JDBC hidden behind a couple of utility classes that wrapped up exceptions etc., threw the result sets into DynaRowSets (or something like that; don't remember now) and that was more than sufficient. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
