RE: I cannot use ejbmaker
Hi, I found out about the same bug and entered a new bug report in bugzilla yesterday, its number is #106. Hope they fix it soon. Bye, Martijn -- _ Martijn van Berkum GX creative online development _ mailto:[EMAIL PROTECTED] _ http://www.gx.nl/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Frank Eggink Sent: woensdag 11 oktober 2000 18:58 To: Orion-Interest Subject: RE: I cannot use ejbmaker Neither have I. On Wednesday, October 11, 2000 6:06 PM, Sean Han [SMTP:[EMAIL PROTECTED]] wrote: Hi, everyone: When using ejbmaker, I found I cannot restore it from a saved .skeleton file. No matter what I entered for the bean, I always get an empty package when I reopen it. Can anyone tell me what's wrong? regards, Sean
Deploying a ear file, not a war file
Hi, Is it possible to create a .ear file which contains the ejb-jar file, but not the web-jar file. Orion should then retrieve it's web related files from a subdirectory. This way I can deploy the ejb's using a jar file, but test them using .jsp files, which I don't need to deploy when changing just a little code. The only way to do this I could think of right now is using two seperate deployments, one with the .ear file and one for the webroot dir. Thanks, Martijn -- _ Martijn van Berkum GX creative online development _ mailto:[EMAIL PROTECTED] _ http://www.gx.nl/
RE: EJB vs Servlets
Hello, This is a very interesting discussion. Here at GX we built our own application server on top of servlets, no JSP, no EJB's. This application server is focused on content management systems. While we are stil happy using it for almost all our clients, I still intent to go to building sites using the J2EE technology and methods. The main reason I want this is not because of technical reasons, but because almost all application server vendors are going the J2EE way. For example, take a look at Vignette, which is going to rebuilt their Storyserver on top of J2ee, of Allaire, which is going to rebuilt its Cold Fusion engine on top of JRun. Also, BEA, IBM and others are all creating J2EE compliant Application Servers. I know this is more a long-term, management overview, probably not intented for a single project, but all these players are going to create reusable components using EJB. So we have to have experience using J2EE, and especially the EJB part, even when it's as immature as it is today, in order to take advantage of them. Martijn -- _ Martijn van Berkum GX creative online development _ mailto:[EMAIL PROTECTED] _ http://www.gx.nl/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of bradley mclain Sent: dinsdag 10 oktober 2000 14:57 To: Orion-Interest Subject: RE: EJB vs Servlets hello all, since it came up, this is an issue that i and our other programmer have been wrestling with for a while, because like everyone else we feel the pressure to use the cool new stuff..and we wonder if the transactional and distributed advantages will help us out. here is my problem. call me dense, but i just don't see or mapping being as flexible as i need it to be. in all the books the examples tell you that you map your object to the table that holds its data. sounds fine in theory, but we have some very complex objects, and we have a complex relational model, the reason for which is to store our data efficiently, not only for this application, but also for others. so we have objects that need to get their data from different tables, even different databases. these objects contain collections, single entities, indexes into other objects, etc., all of which must be persisted in the db. we have solved the problem by writing our own dblayer, employing reflection and stashing all our queries (as well as caching them and the connections) in a static lookup object. this gives us a level of control over the data that i cannot see us getting from any OR tool, no matter how smart (and remember, the smarter something is, the slower). as to transactional support, we use jts or the db transaction services. no problems.. as to servlets, we use exactly one per application, mereley to take the requests and to control everything--everything else is plain old java classes. it is blazingly fast. i cannot believe that looking up objects through jndi is going to be as quick as looking up my classes in a hashmap. if i want distribution, i simply break my app into multiple apps, run them on separate machines, and use the same object model--thats one benefit of oo, right? i hope someone has the time to refute me completely, because, like kevin, i really do want to understand what ejb will give me that i cannot live without. my greatest concern, as i mentioned above, is OR mapping. i have been a dba and a programmer, and i find it really difficult to believe that some tool is going to produce more efficient and more flexible access to my data than i can, given that i currently have full control from table to view to sp to accessor methods on objects.. bradley mclain --usmoving.com --- "Duffey, Kevin" [EMAIL PROTECTED] wrote: Hi Mike (and all), Actually, while Struts is pretty kewl, there are some things that I wish were modified that won't be for reasons of the general population interest instead of my own. Because of this, while I will continue to use Struts at work, my own projects will use my own solution, similar to Struts but not near as robust in some ways, but a bit better on performance. The one thing I really dislike, but I agree with based on what Craig has told me, is that every single form submission causes the auto-population feature to get called (reflection). I only want it to be called if an update occurs. If the user hits cancel to go back, or what not..I don't much care what they just entered. Only when doing searches or updates/entry on forms should it be called. For that reason I am doing my own reflection population routine that does use nested objects. But overall Struts kicks ass in what it offers for a free package. Did I compare Struts to EJB? I didn't mean to in terms of performance.
RE: EJB vs Servlets
Hello, This is a very interesting discussion. Here at GX we built our own application server on top of servlets, no JSP, no EJB's. This application server is focused on content management systems. While we are stil happy using it for almost all our clients, I still intent to go to building sites using the J2EE technology and methods. The main reason I want this is not because of technical reasons, but because almost all application server vendors are going the J2EE way. For example, take a look at Vignette, which is going to rebuilt their Storyserver on top of J2ee, of Allaire, which is going to rebuilt its Cold Fusion engine on top of JRun. Also, BEA, IBM and others are all creating J2EE compliant Application Servers. I know this is more a long-term, management overview, probably not intented for a single project, but all these players are going to create reusable components using EJB. So we have to have experience using J2EE, and especially the EJB part, even when it's as immature as it is today, in order to take advantage of them. Martijn -- _ Martijn van Berkum GX creative online development _ mailto:[EMAIL PROTECTED] _ http://www.gx.nl/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of bradley mclain Sent: dinsdag 10 oktober 2000 14:57 To: Orion-Interest Subject: RE: EJB vs Servlets hello all, since it came up, this is an issue that i and our other programmer have been wrestling with for a while, because like everyone else we feel the pressure to use the cool new stuff..and we wonder if the transactional and distributed advantages will help us out. here is my problem. call me dense, but i just don't see or mapping being as flexible as i need it to be. in all the books the examples tell you that you map your object to the table that holds its data. sounds fine in theory, but we have some very complex objects, and we have a complex relational model, the reason for which is to store our data efficiently, not only for this application, but also for others. so we have objects that need to get their data from different tables, even different databases. these objects contain collections, single entities, indexes into other objects, etc., all of which must be persisted in the db. we have solved the problem by writing our own dblayer, employing reflection and stashing all our queries (as well as caching them and the connections) in a static lookup object. this gives us a level of control over the data that i cannot see us getting from any OR tool, no matter how smart (and remember, the smarter something is, the slower). as to transactional support, we use jts or the db transaction services. no problems.. as to servlets, we use exactly one per application, mereley to take the requests and to control everything--everything else is plain old java classes. it is blazingly fast. i cannot believe that looking up objects through jndi is going to be as quick as looking up my classes in a hashmap. if i want distribution, i simply break my app into multiple apps, run them on separate machines, and use the same object model--thats one benefit of oo, right? i hope someone has the time to refute me completely, because, like kevin, i really do want to understand what ejb will give me that i cannot live without. my greatest concern, as i mentioned above, is OR mapping. i have been a dba and a programmer, and i find it really difficult to believe that some tool is going to produce more efficient and more flexible access to my data than i can, given that i currently have full control from table to view to sp to accessor methods on objects.. bradley mclain --usmoving.com --- "Duffey, Kevin" [EMAIL PROTECTED] wrote: Hi Mike (and all), Actually, while Struts is pretty kewl, there are some things that I wish were modified that won't be for reasons of the general population interest instead of my own. Because of this, while I will continue to use Struts at work, my own projects will use my own solution, similar to Struts but not near as robust in some ways, but a bit better on performance. The one thing I really dislike, but I agree with based on what Craig has told me, is that every single form submission causes the auto-population feature to get called (reflection). I only want it to be called if an update occurs. If the user hits cancel to go back, or what not..I don't much care what they just entered. Only when doing searches or updates/entry on forms should it be called. For that reason I am doing my own reflection population routine that does use nested objects. But overall Struts kicks ass in what it offers for a free package. Did I compare Struts to EJB? I didn't mean to in terms of performance.
mapping database to cmp beans
Hi, At the moment we designed and created a database with around 19 tables. Now we want to map cmp beans to this database. Afaik I have to do this manually, creating all the beans by hand(or by ejbmaker, but it doesnt look at the database, and cannot read in the saved configuration from a previous session :( ). This means creating 3 * 19 .java files.. Is there any way to do this more easily, tools using metadata from the database for example? Thanks, Martijn -- _ Martijn van Berkum GX creative online development _ mailto:[EMAIL PROTECTED] _ http://www.gx.nl/
