On Mon, 12 Aug 2002 15:50:16 -0700, you wrote: >You might think about configuring the demo to use JBoss internal Hypersonic database, >which would negate the requirement that the demo communicate with your machine. Then >it >becomes a problem of populating the database with data. If its a lot of data, then >perhaps your original idea is better.
At the moment I cannot say how big the demo dataset will be. The primary reason why I want to leave the application's EJBs on a central server is protection of valuable source code and class files. I intentionally mention class files, because even a not-decompiled EJB jar file is valuable. The customer could download JBoss, deploy EJB jar and then he would (theoretically) have everything he needs to setup the system on his machine. Since we now use CMP beans, the needed database tables would be created automatically at the first deployment of the EJB jar. If they lie on a central server, then he only sees the interfaces, but has no access to class files of the EJB implementations (please correct me if I'm wrong). He has the swing-app, but he has not the required EJBs. Best regards Dimitri Pissarenko > >Dimitri Pissarenko wrote: > >> Hello! >> >> I've looked at the Netboot demo on the JBoss web-site. Being quite >> impressed by its functionality, I'm considering to use this feature in >> the following way. >> >> I'm currently working on an application which is based on EJB and is >> being developed for several research institutions located in different >> cities in Europe. >> >> In my opinion, it would be highly advantageous to make an evaluation >> version, which should be available to these future customers with as >> least effort as possible (so that they can try out the application and >> we can get feedback about the application quality early). The main >> effort associated with the installation of our application consists of >> setting up the JBoss server and the mySQL DBMS. >> >> In order to relieve the potential customers from these efforts, I've >> thought of distributing the evaluation version in the following way: >> >> 1) Customer downloads the client application (this is a rather small >> swing-based GUI) >> 2) Customer downloads the JBoss Bootstrap Environment >> 3) By means of the JBoss bootstrap environment, the customer installs >> the JBoss server configuration A on his machine. >> 4) The JBoss server (configuration A) communicates with JBoss server >> configuration B, which is located on our web-server and is connected >> to the database. >> >> See also the diagram in the attachment. >> >> JBoss configuration A has a service deployed in it, which forwards all >> requests to the central server (JBoss configuration B). Configuration >> A has no other services in it. Configuration A is installed on the >> customer's machine by means of netboot. >> >> JBoss configuration B contains all the EJBs of our application. >> >> The advantage of this solution is that the potential customer can try >> out the features of our system, as it would be installed on his own >> machine without the disadvantages (the need to setup JBoss and mySQL). >> >> Is this solution possible? >> >> Does it make sense (from a technical point of view) ? >> >> Thanks in advance >> >> Dimitri Pissarenko >> >> ------------------------------------------------------------------------ >> Name: 2002_08_12_netboot.zip >> 2002_08_12_netboot.zip Type: Zip Compressed Data >(application/x-zip-compressed) >> Encoding: base64 ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code1 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
