Bryan,
Thanks for your excellent reply, very helpful.
I will implement the "Embedded Server" method described in the referenced
documentation.
I have a few additional questions if I may:
1) Where does the Web Server application reside?
I assume that I'll instance the Derby Network Server and I'll spawn the end
user default Internet Browser process with my Report Generator HTML. I know
what a Web Server does but I have never set one up or written any JSP /
Servlet code. Tomcat, I think is the best Web server for this
implementation. Is Tomcat and my JSP / Servlet code linked to the Derby
Network Server somehow?
2) My current Java stand alone application uses Java 1.5. A lot of the
documentation you pointed me to references Java 1.6. Is there a benefit for
me to upgrade to Java 1.6 before implementing this "Embedded Server" design?
3) I am using the Java 1.5 SE development system. The way I read todays
documents, I think I only need to go to the Java EE software development
system if I will be using Enterprise Java Bean in the JSP / Servlet code. Is
that correct?
Bryan Pendleton wrote:
>
>> With the Derby Database presently being embedded, I believe that access
>> to
>> the Derby HDD file from the Browser process will be denied.
>
> You can start the Network Server in a background thread in your embedded
> application, and your embedded application can access the database
> directly
> while simultaneously accepting and processing requests from network
> clients
> (for example, your JSPs in your web server). This mode of operation is
> usually called the "embedded server". You can find some documentation
> here:
> http://db.apache.org/derby/docs/10.5/adminguide/cadminov17524.html
>
> There's a nice diagram of how this works here:
> http://db.apache.org/derby/papers/DerbyTut/ns_intro.html#Embedded+Server
>
-----
Regards,
Jim...
--
View this message in context:
http://old.nabble.com/Derby-Network-Server-usage--tp27117797p27134902.html
Sent from the Apache Derby Developers mailing list archive at Nabble.com.
