RE: struts + IBatis + EJB
Yes. In my application we are using this combination. It rocks!! -Original Message- From: Kelly Goedert [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 11:27 AM To: Struts Users Mailing List Subject: struts + IBatis + EJB Hello, has anyone ever tryed (or did) put this 3 pieces (struts, IBatis and EJB) to work together? Kelly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: struts + IBatis + EJB
Ay quick newbie sample tutorial on iBATIS. Truly, hearing for first time! -Original Message- From: Dalmia, Swati [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 12:38 PM To: Struts Users Mailing List Subject: RE: struts + IBatis + EJB Yes. In my application we are using this combination. It rocks!! -Original Message- From: Kelly Goedert [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 11:27 AM To: Struts Users Mailing List Subject: struts + IBatis + EJB Hello, has anyone ever tryed (or did) put this 3 pieces (struts, IBatis and EJB) to work together? Kelly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts to EJB interface strategies
Last year I was on a team that developed a complex ecommerce for T-Mobile that used Struts 1.0.1 and EJB 1.1. We had the Action classes interfaced with DAOs, which in turn went through a session façade (a single session EJB) which in turn called some 40 different entity beans that, depending on the function, either maintained state from the database or from a cache. It's difficult to give you examples, but I can send you the source (it's copyrighted, mind you). Mark -Original Message- From: yan [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2003 8:49 AM To: [EMAIL PROTECTED] Subject: Struts to EJB interface strategies Hi, Firstly, can anyone recommend a good resource that deals with how you integrate a Web Tier implemented using Struts with the EJB Tier. And also a resource that has an excellent example of how the Struts framework interacts with J2EE. I am looking for more than the basic examples you normally find as they do not help given the complexity of the application I am working on. Secondly, what strategies does one use when deciding on how to implement the ActionClass to Session Bean Inteface? I am thinking along these lines: Create a 'Client Helper Interface' that defines all the business methods that your application will require. This Helper class will form the interface between the ActionClasses and the Session Beans. The ActionClass creates a 'Client Helper Interface' object and calls the relevant methods within this interface. The Client Interface then creates a Session Bean that implements the Client Interface. The Session Bean creates the Entity Bean that opens the database connection and returns the relevant data back to the Session Bean. The Session Bean returns the required information back to the Client Helper Interface. The Client Helper Interface returns to the ActionClass Should you have a separate Helper Interface for each Session Bean? many thanks yan KickStartESolutions - Intelligent Web Services [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts to EJB interface strategies
Buy the Oreilly book on Struts. There are some very good design principles incorporated into this book using especially some of the J2EE design patterns. Keith - Original Message - From: yan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 19, 2003 7:49 AM Subject: Struts to EJB interface strategies Hi, Firstly, can anyone recommend a good resource that deals with how you integrate a Web Tier implemented using Struts with the EJB Tier. And also a resource that has an excellent example of how the Struts framework interacts with J2EE. I am looking for more than the basic examples you normally find as they do not help given the complexity of the application I am working on. Secondly, what strategies does one use when deciding on how to implement the ActionClass to Session Bean Inteface? I am thinking along these lines: Create a 'Client Helper Interface' that defines all the business methods that your application will require. This Helper class will form the interface between the ActionClasses and the Session Beans. The ActionClass creates a 'Client Helper Interface' object and calls the relevant methods within this interface. The Client Interface then creates a Session Bean that implements the Client Interface. The Session Bean creates the Entity Bean that opens the database connection and returns the relevant data back to the Session Bean. The Session Bean returns the required information back to the Client Helper Interface. The Client Helper Interface returns to the ActionClass Should you have a separate Helper Interface for each Session Bean? many thanks yan KickStartESolutions - Intelligent Web Services [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts w/EJB
Martin Naskovski wrote: Hello all. Is there an app that demonstrates the use of Struts EJB as a persistence layer? I checked out Struts-Resume from Matt Raible, but it uses Hibernate... Is there anything available w/EJB's? Thanks. http://xpetstore.sf.net/ There are two implementations of Xpetstore, one that uses EJB and one that just uses servlets. Check out the EJB one, it works great with JBoss. Note, I personally don't think that using EJB is fundamentally different from any other persistence layer, at least not in reference to Struts, so you should be able to look at just about any sample code and figure out some best practices. It all boils down to the fact that you have Struts Actions, which receive HTTP requests from the client, and which then delegate the work to other objects. Whether those objects are session beans that perform some task by calling EJB or Hibernate objects, or whether you're going the simple route (what I'm doing b/c my needs are so trivial) and just having your Struts Actions directly manipulate Data Access Objects which use JDBC business delegates, it's not really much different. The only big difference I've seen is that some people believe you should abstract your model into a layer just beyond Struts Actions so that you can switch from Struts to another framework if necessary. But the other line of reasoning is that this is a lot of extra work if you have no plans to leave Struts. My 2 cents. Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts w/EJB
Maybe EJB should be used with JSF (and blue prints http://java.sun.com/blueprints/code/index.html) instead of Struts. Struts is more like this http://ibatis.com/jpetstore/jpetstore.html. .V Erik Price wrote: Martin Naskovski wrote: Hello all. Is there an app that demonstrates the use of Struts EJB as a persistence layer? I checked out Struts-Resume from Matt Raible, but it uses Hibernate... Is there anything available w/EJB's? Thanks. http://xpetstore.sf.net/ There are two implementations of Xpetstore, one that uses EJB and one that just uses servlets. Check out the EJB one, it works great with JBoss. Note, I personally don't think that using EJB is fundamentally different from any other persistence layer, at least not in reference to Struts, so you should be able to look at just about any sample code and figure out some best practices. It all boils down to the fact that you have Struts Actions, which receive HTTP requests from the client, and which then delegate the work to other objects. Whether those objects are session beans that perform some task by calling EJB or Hibernate objects, or whether you're going the simple route (what I'm doing b/c my needs are so trivial) and just having your Struts Actions directly manipulate Data Access Objects which use JDBC business delegates, it's not really much different. The only big difference I've seen is that some people believe you should abstract your model into a layer just beyond Struts Actions so that you can switch from Struts to another framework if necessary. But the other line of reasoning is that this is a lot of extra work if you have no plans to leave Struts. My 2 cents. Erik -- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA Advanced a href =baseBeans.comStruts Training/a, mentoring and project recovery in North East. Open Source a href =baseBeans.comPortal Content Management/a basicPortal software. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts w/EJB
Download modelj from sourceforge and try it. Supply the path to your j2ee.jar and build the sample app in 2 minutes. Modelj will create a struts/ejb application for you from one single config file. Using JBoss, all you have to do is setup a default data source and deploy your sample.ear. http://sourceforge.net/projects/modelj -- James Mitchell Software Developer/Struts Evangelist http://www.struts-atlanta.org 678-910-8017 AIM:jmitchtx - Original Message - From: Martin Naskovski [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Thursday, July 31, 2003 7:01 PM Subject: Struts w/EJB Hello all. Is there an app that demonstrates the use of Struts EJB as a persistence layer? I checked out Struts-Resume from Matt Raible, but it uses Hibernate... Is there anything available w/EJB's? Thanks. Martin -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts w/EJB
hi, Struts doesnt enforce or set any rules or guidelines for using ejbs. With in your action classes you should use Business Delegate to hide the client's dependency on any persistance layer ejb or DAO. Cheers Ashwani Kalra http://www.geocities.com/ashwani_kalra/ -Original Message- From: Martin Naskovski [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2003 4:31 AM To: Struts Users Mailing List Subject: Struts w/EJB Hello all. Is there an app that demonstrates the use of Struts EJB as a persistence layer? I checked out Struts-Resume from Matt Raible, but it uses Hibernate... Is there anything available w/EJB's? Thanks. Martin -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorised to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Struts w/EJB
try looking xpetstore. xpetsotre.sourceforge.net. see if it helps Shashank -Original Message- From: Kalra, Ashwani [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2003 10:24 AM To: 'Struts Users Mailing List' Subject: RE: Struts w/EJB hi, Struts doesnt enforce or set any rules or guidelines for using ejbs. With in your action classes you should use Business Delegate to hide the client's dependency on any persistance layer ejb or DAO. Cheers Ashwani Kalra http://www.geocities.com/ashwani_kalra/ -Original Message- From: Martin Naskovski [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2003 4:31 AM To: Struts Users Mailing List Subject: Struts w/EJB Hello all. Is there an app that demonstrates the use of Struts EJB as a persistence layer? I checked out Struts-Resume from Matt Raible, but it uses Hibernate... Is there anything available w/EJB's? Thanks. Martin -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorised to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: STRUTS with EJB
http://xpestore.sourceforge.net -Original Message- From: Laurent MARQUEZ [mailto:[EMAIL PROTECTED] Sent: 28 July 2003 10:33 To: [EMAIL PROTECTED] Subject: STRUTS with EJB Hi, I'm new in using of Struts. I would like to integrate STRUTS with EJB. I would like to have a complete example of struts with EJB. I interface STRUTS to EJB with the business delegate pattern but after i don't know how to write class Action, ActionForm, ActionForward... and configure my struts-config.xml Thanks, Laurent. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts + jndi + ejb (on iAS)
Since you're attempting to access the EJB (actually the JNDI registry in
general) from OUTSIDE THE EJB CONTAINER (i.e. from Tomcat), you need to
specify a naming provider as a system property in the JAVA_ARGS of your
java command line. For example:
Not sure what the actual java command used to launch Tomcat is, but it's something
like this:
set NAMING_PROVIDER=172.168.12.23
set JAVA_ARGS=-Djava.naming.provider.url=%NAMING_PROVIDER%
java %JAVA_ARGS% {other stuff to launch tomcat}
This needs to be set somewhere in the cmd file you use to launch Tomcat.
Alternatively, you can also create the initial context by passing it a
HashMap containing all parameters you need to specify the JNDI provider.
This is done in the code when you're creating the InitialContext. Here's
sample code that generates an initial context for an EJB client attempting
to access an ejb in a weblogic container:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, t3://localhost:7001);
Context ctx = new InitialContext(env);
Some of the details here are missing, but it should get you on the right track.
Regarding the NoClassDefFoundError - gosh this could be anything. Are you
sure that your the ejb classes are visible to Tomcat? Resolving your jndi
issue may allow you to pull the classes using traditional rmi
functionality.
Best of luck. Send more info if you make progress.
Kevin
Kevin
Stan Burnitt [EMAIL PROTECTED] on 05/04/2002 07:49:11 PM
Please respond to Struts Users Mailing List
[EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:(bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject: struts + jndi + ejb (on iAS)
Hello,
I'm a struts-newbie, but have worked with WebObjects/Model2 for many years.
So I hope I'm not asking a dumb question here ;-)
I've got a simple struts action, and a simple ejb. They work fine until
I try to access the bean on iAS, from Tomcat.
I want to access the bean via a jndi.properties file:
java.naming.factory.initial=javax.naming.InitialContext
#java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
-- this works when I run in JDeveloper
java.naming.provider.url=ormi://brasil/clientes-bean
java.naming.security.principal=*
java.naming.security.credentials=*
I put ejb.jar in $CATALINA_HOME/common/lib
I cannot get a connection to the iAS - bean server.
Tomcat is failing to load EJBHome. The tomcat locahost shows this
exception:
2002-05-04 22:24:18 oreilly: Error creating Action instance for path
'/login',
class name 'com.oreilly.actions.LoginAction'
java.lang.NoClassDefFoundError: javax/ejb/EJBHome
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:493)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
at
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLo
ader.java:1631)
at
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.jav
a:926)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav
a:1360)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav
a:1243)
...
...
1) What naming factory do I use, since the oracle naming factory is not
available on Tomcat?
2) I think this is part of my problem, what else?
Can anybody clue me in?
Thanks
Stan
---
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
As for whether EJBs is going to be required in the near future for you to get a job, who's to say? Sadly, companies are very biased towards people who don't have specific product experience in many cases. Don't take this the wrong way but EJB's are not all that difficult. I have read a book on them and tried some things with the reference implementation. No big deal. So you have a home and a remote interface. So you have session beans (our struts Java beans are basically the same thing), entity beans (We wrote a bunch of db-bind classes to be used within our struts application to perform this) and message beans (I used JMS in cases to simulate message beans). Ok... So why do so many companies discredit individuals who lack a specific product experience even if they have decent OO skills? :-) A friend of ours who has done EJB for a year says EJB's are very easy. What's difficult is understanding how they all work together. But that's OO and not EJB. I guess since this is an Employer's market (at least in the Phoenix and Denver area), they can put tight strict requirements around. Heck, we'd love it if our employer would buy an App Server but they won't so we're using Struts since it's free. But we've found out that it's very powerful and very easy to work with. thanks for your insight... Theron -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
I obviously missed part of this discussion -- a negative side effect of trying to do my job while keeping up with this list. And I don't have a lot of time to respond to this fully. However, I find it necessary to disagree with the contention that JavaBeans are Session Beans, DAO classes are Entity Beans, and JMS is Message Beans. What I think you've missed by this over-simplification is the intended role of the EJB container in providing services and capabilities that you would otherwise be developing yourself: transactions, security, resource connectivity (e.g. Naming, Mail, Database), distribution, failover, caching, scaling, and declaritive configuration. Could you write these? Sure. Would use use available specifications and implementations of JDBC, JTA, JTS, JNDI, JavaMail, etc. You bet. But that is exactly what the specification is about -- ensuring a choice of robust compliant container implementations which can be used to host your application components. And while EJBs aren't necessarily the hardest thing to ever come along in application development, I wouldn't so easily dismiss them. There is a _lot_ to know if one is to make effective use of the technology. Perhaps a re-reading of some of the J2EE docs, including the J2EE Tutorial and the Patterns section of the BluePrints, will emphasize the breadth and depth of the technology. That is, if you are interested in learning more. The question ultimately isn't Struts vs. EJB but whether you intend to construct using Struts with EJB or Struts without EJB. Both are possible. Both are valid. Both have pros and cons. Each may be a valid (or invalid) architectural decision depending on the problem and environment. Best regards, Jim Cakalic -Original Message- From: Kousek, Theron [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 11:18 AM To: 'Struts Users Mailing List' Subject: RE: Struts vs EJB, thoughts? As for whether EJBs is going to be required in the near future for you to get a job, who's to say? Sadly, companies are very biased towards people who don't have specific product experience in many cases. Don't take this the wrong way but EJB's are not all that difficult. I have read a book on them and tried some things with the reference implementation. No big deal. So you have a home and a remote interface. So you have session beans (our struts Java beans are basically the same thing), entity beans (We wrote a bunch of db-bind classes to be used within our struts application to perform this) and message beans (I used JMS in cases to simulate message beans). Ok... So why do so many companies discredit individuals who lack a specific product experience even if they have decent OO skills? :-) A friend of ours who has done EJB for a year says EJB's are very easy. What's difficult is understanding how they all work together. But that's OO and not EJB. I guess since this is an Employer's market (at least in the Phoenix and Denver area), they can put tight strict requirements around. Heck, we'd love it if our employer would buy an App Server but they won't so we're using Struts since it's free. But we've found out that it's very powerful and very easy to work with. thanks for your insight... Theron -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
Heck, we'd love it if our employer would buy an App Server but they won't so we're using Struts since it's free. But we've found out that it's very powerful and very easy to work with. Struts is cool, eh? If you want to use a free app server, check out www.jboss.org It's open-source, fast as hell, infinitely configurable, deployment is simplicity itself, and you can download an install zip with Tomcat already fully integrated. You can also configure it use your preferred JSP engine/web server. JBoss's auto-deployer will take an EAR file, deploy the EJB jar file(s) within it in its EJB container, and deploy the war file(s) contained within it to the integrated web server, faster than you can say No way!. It support runtime re-deployment of EJBs and uses a no-compilation .class file generation mechanism to generate the necessary container-specific EJB stub skeleton classes (very fast). You can deploy 'vanilla' EJB jars, or customize them with JBoss-specific deployment descriptors, your choice. Compare THAT with Weblogic, or, horror of horrors, WebSphere. b.t.w, I have tested direct client integration (not web-based) using EJBs with Weblogic, WebSphere, JBoss, and IPlanet, and JBoss wins hands down in all categories, except for clustering, which is where Weblogic shines. Porting from JBoss to another server is also simplicity itself, since you can use generic EJB jars for deployment in JBoss, none of this app server-specific required crap you have to do with the others. cheers, Joe Barefoot plug from JBoss's site: 'JBoss beat out BEA and IBM to sweep the JavaWorld Editors' Choice 2002 Award for Best Java Application Server. JBoss stopped being an application server long time ago -- it is now officially a phenomenon, says ECA judge Humphrey Sheil. Discover for yourself why JBoss gets more monthly downloads than any other app-server.' -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
Joseph, Have you done any testing against HP Application Server? It is also free. I would be interested in any comments that you may have! Robert -Original Message- From: Joseph Barefoot [mailto:[EMAIL PROTECTED]] Sent: Tue, April 16, 2002 11:29 AM To: Struts Users Mailing List Subject: RE: Struts vs EJB, thoughts? Heck, we'd love it if our employer would buy an App Server but they won't so we're using Struts since it's free. But we've found out that it's very powerful and very easy to work with. Struts is cool, eh? If you want to use a free app server, check out www.jboss.org It's open-source, fast as hell, infinitely configurable, deployment is simplicity itself, and you can download an install zip with Tomcat already fully integrated. You can also configure it use your preferred JSP engine/web server. JBoss's auto-deployer will take an EAR file, deploy the EJB jar file(s) within it in its EJB container, and deploy the war file(s) contained within it to the integrated web server, faster than you can say No way!. It support runtime re-deployment of EJBs and uses a no-compilation .class file generation mechanism to generate the necessary container-specific EJB stub skeleton classes (very fast). You can deploy 'vanilla' EJB jars, or customize them with JBoss-specific deployment descriptors, your choice. Compare THAT with Weblogic, or, horror of horrors, WebSphere. b.t.w, I have tested direct client integration (not web-based) using EJBs with Weblogic, WebSphere, JBoss, and IPlanet, and JBoss wins hands down in all categories, except for clustering, which is where Weblogic shines. Porting from JBoss to another server is also simplicity itself, since you can use generic EJB jars for deployment in JBoss, none of this app server-specific required crap you have to do with the others. cheers, Joe Barefoot plug from JBoss's site: 'JBoss beat out BEA and IBM to sweep the JavaWorld Editors' Choice 2002 Award for Best Java Application Server. JBoss stopped being an application server long time ago -- it is now officially a phenomenon, says ECA judge Humphrey Sheil. Discover for yourself why JBoss gets more monthly downloads than any other app-server.' -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts vs EJB, thoughts?
Subject: Re: Struts vs EJB, thoughts? From: Vic Cekvenich [EMAIL PROTECTED] === EJBs, as I have said before sometimes have negative impact on design, productivity and performance. SHURTLEFF,ROBERT (HP-FtCollins,ex1) wrote: Joseph, Have you done any testing against HP Application Server? It is also free. I would be interested in any comments that you may have! Robert -Original Message- From: Joseph Barefoot [mailto:[EMAIL PROTECTED]] Sent: Tue, April 16, 2002 11:29 AM To: Struts Users Mailing List Subject: RE: Struts vs EJB, thoughts? Heck, we'd love it if our employer would buy an App Server but they won't so we're using Struts since it's free. But we've found out that it's very powerful and very easy to work with. Struts is cool, eh? If you want to use a free app server, check out www.jboss.org It's open-source, fast as hell, infinitely configurable, deployment is simplicity itself, and you can download an install zip with Tomcat already fully integrated. You can also configure it use your preferred JSP engine/web server. JBoss's auto-deployer will take an EAR file, deploy the EJB jar file(s) within it in its EJB container, and deploy the war file(s) contained within it to the integrated web server, faster than you can say No way!. It support runtime re-deployment of EJBs and uses a no-compilation .class file generation mechanism to generate the necessary container-specific EJB stub skeleton classes (very fast). You can deploy 'vanilla' EJB jars, or customize them with JBoss-specific deployment descriptors, your choice. Compare THAT with Weblogic, or, horror of horrors, WebSphere. b.t.w, I have tested direct client integration (not web-based) using EJBs with Weblogic, WebSphere, JBoss, and IPlanet, and JBoss wins hands down in all categories, except for clustering, which is where Weblogic shines. Porting from JBoss to another server is also simplicity itself, since you can use generic EJB jars for deployment in JBoss, none of this app server-specific required crap you have to do with the others. cheers, Joe Barefoot plug from JBoss's site: 'JBoss beat out BEA and IBM to sweep the JavaWorld Editors' Choice 2002 Award for Best Java Application Server. JBoss stopped being an application server long time ago -- it is now officially a phenomenon, says ECA judge Humphrey Sheil. Discover for yourself why JBoss gets more monthly downloads than any other app-server.' -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
for the last 4 months and don't mind it. I see it as a poor mans EJB. Poor man's EJB ? :-) No, EJB deals with very different problems. Also, seems like Struts is more useful for smaller companies and EJB is more suitable for large corporations. Is this pretty much a valid statement? We use STRUTS and EJBs. I think that the best approach is to use STRUTS and EJB together. Maris -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts vs EJB, thoughts?
I dont think you can directly compare Struts to EJB since both solve different problems.. but you can use EJB with Struts.. - Original Message - From: Kousek, Theron [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Friday, April 12, 2002 5:03 PM Subject: Struts vs EJB, thoughts? Not that I am looking for a job (I am not), I have been working with struts for the last 4 months and don't mind it. I see it as a poor mans EJB. I have no EJB experience but I don't think transitioning over to EJB after working with struts as a big deal. After all, they both act on server-side beans. Yeah, EJB has entity beans and session beans but you can easily simulate both of those types of beans using JSP/Struts/tomcat. Since there's a gazillion people on the planet now that know how to program in Java, getting an EJB position will be next to impossible (I guess) if you don't have EJB experience. Companies now have so many available Java programmers to pick and choose from and are in a position to require salary cuts for existing Java programmers on staff due to the plethoria of Java developers available to work who would be willing to work for less$ Being a Java programmer is no longer an elite skill. Now it's as common as coding in Cobol once was :-( I have already read about the salaries of Java programmers declining and I expect the trend to continue due to the bad economy and the oversupply of qualified Java programmers in the market place. This is why so many companies can now demand specific product experience with Java (ie, if you don't have 1 year of Bea Weblogic experience, see you later!! Next person please...)... SO back to the Struts vs EJB issue: If one is comfortable with struts, how much more difficult would EJB be to get comfortable with? Also, seems like Struts is more useful for smaller companies and EJB is more suitable for large corporations. Is this pretty much a valid statement? thanks... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
EJB and Struts are not the same thing. Struts is an open source framework for building Web applications that integrates with standard technologies like Java Servlets, JavaBeans, and JavaServer Pages (JSP). Its goal is to do the mundane work of converting HTTP parameter information into more Java-friendly models, as well as provide an MVC architecture for your J2EE application. While you can construct an application using struts and without EJBs, you can also construct an application using both struts and EJBs. (For that matter, you can create a J2EE application without struts and without EJBs, but why would you? :). I would suggest you pick up a printed or online copy of the J2EE Blueprints from Sun. There, it will outline the fundamental principles of the J2EE architecture, the different tiers, where servlets, JSPs, web frameworks, and EJBs fit in, and even some best practices and patterns. From there, you can determine if EJBs fit your applications' needs. As for whether EJBs is going to be required in the near future for you to get a job, who's to say? But, I have found that many companies in the Austin area have to make this decision before they begin their project, so knowing at least how EJBs work and what the decision points are for using or staying away from EJBs is necessary for any good software designer (and a requirement for architects, of course). Just like any distributed component architecture, EJBs require careful planning and can be a painful decision to a project if the early architecture decisions and daily decisions you make in your design are not well thought out. I've seen projects die a horrible death from poor planning and lack of overall architectural planning. When done right, EJBs can make your life must easier, since there are many benefits provided to your application that you gain for free from J2EE that you would have had to build by hand otherwise. HTH, James -Original Message- From: Kousek, Theron [mailto:[EMAIL PROTECTED]] Sent: Friday, April 12, 2002 7:03 PM To: 'Struts Users Mailing List' Subject: Struts vs EJB, thoughts? Not that I am looking for a job (I am not), I have been working with struts for the last 4 months and don't mind it. I see it as a poor mans EJB. I have no EJB experience but I don't think transitioning over to EJB after working with struts as a big deal. After all, they both act on server-side beans. Yeah, EJB has entity beans and session beans but you can easily simulate both of those types of beans using JSP/Struts/tomcat. Since there's a gazillion people on the planet now that know how to program in Java, getting an EJB position will be next to impossible (I guess) if you don't have EJB experience. Companies now have so many available Java programmers to pick and choose from and are in a position to require salary cuts for existing Java programmers on staff due to the plethoria of Java developers available to work who would be willing to work for less$Being a Java programmer is no longer an elite skill. Now it's as common as coding in Cobol once was :-( I have already read about the salaries of Java programmers declining and I expect the trend to continue due to the bad economy and the oversupply of qualified Java programmers in the market place. This is why so many companies can now demand specific product experience with Java (ie, if you don't have 1 year of Bea Weblogic experience, see you later!! Next person please...)... SO back to the Struts vs EJB issue: If one is comfortable with struts, how much more difficult would EJB be to get comfortable with? Also, seems like Struts is more useful for smaller companies and EJB is more suitable for large corporations. Is this pretty much a valid statement? thanks... -- To unsubscribe, e-mail: mailto:struts-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts vs EJB, thoughts?
I prefer apples to oranges because they don't take their name from their colour. FYI, we use Struts with EJBs. EJBs are the M of MVC, Struts is the VC. There is little to no overlap. If you don't need the container support provided for EJBs (remote invocation, pooling, transactions, etc), then you use plain JBs as the M and struts as the VC. (That may be simplifying it somewhat, but you get my drift). Cheers, Brett -Original Message- From: Kousek, Theron [mailto:[EMAIL PROTECTED]] Sent: Saturday, 13 April 2002 10:03 AM To: 'Struts Users Mailing List' Subject: Struts vs EJB, thoughts? Not that I am looking for a job (I am not), I have been working with struts for the last 4 months and don't mind it. I see it as a poor mans EJB. I have no EJB experience but I don't think transitioning over to EJB after working with struts as a big deal. After all, they both act on server-side beans. Yeah, EJB has entity beans and session beans but you can easily simulate both of those types of beans using JSP/Struts/tomcat. Since there's a gazillion people on the planet now that know how to program in Java, getting an EJB position will be next to impossible (I guess) if you don't have EJB experience. Companies now have so many available Java programmers to pick and choose from and are in a position to require salary cuts for existing Java programmers on staff due to the plethoria of Java developers available to work who would be willing to work for less$Being a Java programmer is no longer an elite skill. Now it's as common as coding in Cobol once was :-( I have already read about the salaries of Java programmers declining and I expect the trend to continue due to the bad economy and the oversupply of qualified Java programmers in the market place. This is why so many companies can now demand specific product experience with Java (ie, if you don't have 1 year of Bea Weblogic experience, see you later!! Next person please...)... SO back to the Struts vs EJB issue: If one is comfortable with struts, how much more difficult would EJB be to get comfortable with? Also, seems like Struts is more useful for smaller companies and EJB is more suitable for large corporations. Is this pretty much a valid statement? thanks... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts +ACY- EJB support
Hi I am geeting the idea from a no. of people that that EJB should only be used if u want Scalibility /Distributed or Transaction Managment. But That is against of my knowledge. Apart from the Software Appserver Cost we do get benefits from EJB also 1) Automatic Database pooling 2) easier deveopment +ACY- more flexibility by use of container managed services 3) more plugable component architechure So why would anyone say +ACI-people attempt EJBs to much+ACI- for medium sized projects ? Thanks - Original Message - From: +ACI-Vic Cekvenich+ACI- +ADw-vic+AEA-basebeans.com+AD4- To: +ACI-Struts Users Mailing List+ACI- +ADw-struts-user+AEA-jakarta.apache.org+AD4- Sent: Friday, December 28, 2001 9:18 PM Subject: Re: Struts +ACY- EJB support +AD4- When I did EJB's, my understanding was that Sun would recommend them for +AD4- distributed application. Other's found them very slow. +AD4- This is said on EBB home page +ACI- the EJBTM server-side component model +AD4- simplifies development of middleware components that are transactional, +AD4- scalable, and portable.+ACI- +AD4- So if you do not need midldleware, ie, distributed, consider not using +AD4- EJBs. Middleware makes sense on only about 5+ACU- of applications, so +AD4- perhaps people attempt EJBs to much. If you do need distributed, perhaps +AD4- SOAP is better. EJB API to me is like SWING api, it has it's uses, +AD4- +AD4- Just a JavaBean or a rowset or a combo for model does just fine. +AD4- +AD4- Vic +AD4- +AD4- Jon Ferguson wrote: +AD4- +AD4- +AD4-Am I not correct in suggesting that Action objects are essentially our +AD4- +AD4-opportunity to connect into an EJB model... Therefore struts' major +AD4- +AD4-focus is not on the Model side of things which is where EJB majors (esp. Entity +AD4- +AD4-Beans). The two seem like a cool fit. +AD4- +AD4- +AD4- +AD4-As far as scalability issues... what features make you say struts is generally +AD4- +AD4-targets medium sized projects? Perhaps the single servlet controller? +AD4- +AD4-Or are you drawing a parallel between size and complexity? Eg. lack of workflow +AD4- +AD4-yet (unless its farther on than I thought+ACE-). +AD4- +AD4- +AD4- +AD4-Cheers, +AD4- +AD4-Jon +AD4- +AD4- +AD4- +AD4-Gopalakrishnan Rangaswamy wrote: +AD4- +AD4- +AD4- +AD4APg-Patney, +AD4- +AD4APg- +AD4- +AD4APg-The struts framework is basically meant for medium sized projects, so +AD4- +AD4APg-EJBs are not envisaged as part of it. If the project is big, and likely +AD4- +AD4APg-to face scalability issues then it is better to adapt ejb based design +AD4- +AD4APg-patterns. +AD4- +AD4APg- +AD4- +AD4APg-And nothing stops from calling a ejb in the struts framework. +AD4- +AD4APg- +AD4- +AD4APg-hope this helps. +AD4- +AD4APg- +AD4- +AD4APg--Original Message- +AD4- +AD4APg-From: Patney +AFs-mailto:xpatney+AEA-hotmail.com+AF0- +AD4- +AD4APg-Sent: Friday, December 28, 2001 5:09 PM +AD4- +AD4APg-To: 'Struts Users Mailing List' +AD4- +AD4APg-Subject: Struts +ACY- EJB support +AD4- +AD4APg- +AD4- +AD4APg-Hi All, +AD4- +AD4APg-Can anyone give comment for my observation below : +AD4- +AD4APg- +AD4- +AD4APg-According to the struts documentation , it seams to be focusing a lot on +AD4- +AD4APg-the +AD4- +AD4APg-Servlet / JSP combination and does not seam to be exploiting the EJB +AD4- +AD4APg-features as extensively as it could. +AD4- +AD4APg- +AD4- +AD4APg-Do i need to use Sun Pet Store for best EJB design practises and +AD4- +AD4APg-possible +AD4- +AD4APg-pick up some code (generic classes) from it +AD4- +AD4APg- +AD4- +AD4APg-Thanks in advance +AD4- +AD4APg- +AD4- +AD4APg--- +AD4- +AD4APg-To unsubscribe, e-mail: +AD4- +AD4APgA8-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- +AD4APg-For additional commands, e-mail: +AD4- +AD4APgA8-mailto:struts-user-help+AEA-jakarta.apache.org+AD4- +AD4- +AD4APg- +AD4- +AD4APg--- +AD4- +AD4APg-To unsubscribe, e-mail: +ADw-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- +AD4APg-For additional commands, e-mail: +ADw-mailto:struts-user-help+AEA-jakarta.apache.org+AD4- +AD4- +AD4APg- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4--- +AD4- +AD4-To unsubscribe, e-mail: +ADw-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- +AD4-For additional commands, e-mail: +ADw-mailto:struts-user-help+AEA-jakarta.apache.org+AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- -- +AD4- To unsubscribe, e-mail: +ADw-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- For additional commands, e-mail: +ADw-mailto:struts-user-help+AEA-jakarta.apache.org+AD4- +AD4- +AD4- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts +ACY- EJB support
Couldn't agree with you anymore+ACE- According to my understanding, Struts is basically an MVC framework for web applications.So it's main focus is on the web tier and it doesn't place any restrictions on how you implement the business logic. The model part of the Struts framework, namely the form bean is only the model for the web tier. For the model of business logic, you can either use javabean or rowset or EJB or whatever you like. The beauty of Struts is that you can easily plug all these into the framework with the Action class, which can be regarded as the connector for your business model. The bottom line is scalability is never a problem for Struts. - Original Message - From: +ACI-Jon Ferguson+ACI- +ADw-ferguson+AEA-ieee.org+AD4- To: +ACI-Struts Users Mailing List+ACI- +ADw-struts-user+AEA-jakarta.apache.org+AD4- Sent: Friday, December 28, 2001 9:56 PM Subject: Re: Struts +ACY- EJB support +AD4- Am I not correct in suggesting that Action objects are essentially our +AD4- opportunity to connect into an EJB model... Therefore struts' major +AD4- focus is not on the Model side of things which is where EJB majors (esp. Entity +AD4- Beans). The two seem like a cool fit. +AD4- +AD4- As far as scalability issues... what features make you say struts is generally +AD4- targets medium sized projects? Perhaps the single servlet controller? +AD4- Or are you drawing a parallel between size and complexity? Eg. lack of workflow +AD4- yet (unless its farther on than I thought+ACE-). +AD4- +AD4- Cheers, +AD4- Jon +AD4- +AD4- Gopalakrishnan Rangaswamy wrote: +AD4- +AD4- +AD4- Patney, +AD4- +AD4- +AD4- +AD4- The struts framework is basically meant for medium sized projects, so +AD4- +AD4- EJBs are not envisaged as part of it. If the project is big, and likely +AD4- +AD4- to face scalability issues then it is better to adapt ejb based design +AD4- +AD4- patterns. +AD4- +AD4- +AD4- +AD4- And nothing stops from calling a ejb in the struts framework. +AD4- +AD4- +AD4- +AD4- hope this helps. +AD4- +AD4- +AD4- +AD4- -Original Message- +AD4- +AD4- From: Patney +AFs-mailto:xpatney+AEA-hotmail.com+AF0- +AD4- +AD4- Sent: Friday, December 28, 2001 5:09 PM +AD4- +AD4- To: 'Struts Users Mailing List' +AD4- +AD4- Subject: Struts +ACY- EJB support +AD4- +AD4- +AD4- +AD4- Hi All, +AD4- +AD4- Can anyone give comment for my observation below : +AD4- +AD4- +AD4- +AD4- According to the struts documentation , it seams to be focusing a lot on +AD4- +AD4- the +AD4- +AD4- Servlet / JSP combination and does not seam to be exploiting the EJB +AD4- +AD4- features as extensively as it could. +AD4- +AD4- +AD4- +AD4- Do i need to use Sun Pet Store for best EJB design practises and +AD4- +AD4- possible +AD4- +AD4- pick up some code (generic classes) from it +AD4- +AD4- +AD4- +AD4- Thanks in advance +AD4- +AD4- +AD4- +AD4- -- +AD4- +AD4- To unsubscribe, e-mail: +AD4- +AD4- +ADw-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- +AD4- For additional commands, e-mail: +AD4- +AD4- +ADw-mailto:struts-user-help+AEA-jakarta.apache.org+AD4- +AD4- +AD4- +AD4- +AD4- -- +AD4- +AD4- To unsubscribe, e-mail: ++ADw-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- +AD4- For additional commands, e-mail: ++ADw-mailto:struts-user-help+AEA-jakarta.apache.org+AD4- +AD4- +AD4- +AD4- -- +AD4- To unsubscribe, e-mail: ++ADw-mailto:struts-user-unsubscribe+AEA-jakarta.apache.org+AD4- +AD4- For additional commands, e-mail: ++ADw-mailto:struts-user-help+AEA-jakarta.apache.org+AD4-
RE: STRUTS and EJB
http://developer.java.sun.com/developer/restricted/patterns/BusinessDelegate .html http://developer.java.sun.com/developer/restricted/patterns/ValueObject.html http://developer.java.sun.com/developer/restricted/patterns/SessionFacade.ht ml EJB and Struts! -Original Message- From: craigmcc@localhost [mailto:craigmcc@localhost]On Behalf Of Craig R. McClanahan Sent: None To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB On Thu, 23 Aug 2001, Juha Paananen wrote: I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? Yes, it is ... and it is designed precisely to keep you from doing what you're trying to do :-). More seriously, an ActionForm exists primarily to save the server-side state of an HTML input form, in a fashion that it can be reproduced *exactly* the way the user entered it even if they make mistakes. For that reason, you will typically use String properties in an ActionForm, even for integer and date properties in the underlying EJBs. Further, the properties that exist on an ActionForm should match what is on the HTML form, which is *not* always (or even often, in my experience) exactly the same as the contents of a particular value object from a particular EJB. Think of an ActionForm as part of the view layer (in MVC terms), while a value object is part of the model layer, and it will make a lot more sense. Craig McClanahan
RE: STRUTS and EJB
the samples codes for these patterns can be found at http://www.myhtg.com/product.html --- Barry Glasco [EMAIL PROTECTED] wrote: http://developer.java.sun.com/developer/restricted/patterns/BusinessDelegate .html http://developer.java.sun.com/developer/restricted/patterns/ValueObject.html http://developer.java.sun.com/developer/restricted/patterns/SessionFacade.ht ml EJB and Struts! -Original Message- From: craigmcc@localhost [mailto:craigmcc@localhost]On Behalf Of Craig R. McClanahan Sent: None To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB On Thu, 23 Aug 2001, Juha Paananen wrote: I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? Yes, it is ... and it is designed precisely to keep you from doing what you're trying to do :-). More seriously, an ActionForm exists primarily to save the server-side state of an HTML input form, in a fashion that it can be reproduced *exactly* the way the user entered it even if they make mistakes. For that reason, you will typically use String properties in an ActionForm, even for integer and date properties in the underlying EJBs. Further, the properties that exist on an ActionForm should match what is on the HTML form, which is *not* always (or even often, in my experience) exactly the same as the contents of a particular value object from a particular EJB. Think of an ActionForm as part of the view layer (in MVC terms), while a value object is part of the model layer, and it will make a lot more sense. Craig McClanahan __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
RE: STRUTS and EJB
On Thu, 23 Aug 2001, Juha Paananen wrote: I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? Yes, it is ... and it is designed precisely to keep you from doing what you're trying to do :-). More seriously, an ActionForm exists primarily to save the server-side state of an HTML input form, in a fashion that it can be reproduced *exactly* the way the user entered it even if they make mistakes. For that reason, you will typically use String properties in an ActionForm, even for integer and date properties in the underlying EJBs. Further, the properties that exist on an ActionForm should match what is on the HTML form, which is *not* always (or even often, in my experience) exactly the same as the contents of a particular value object from a particular EJB. Think of an ActionForm as part of the view layer (in MVC terms), while a value object is part of the model layer, and it will make a lot more sense. Craig McClanahan
Re: STRUTS and EJB
Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
Re: STRUTS and EJB
I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
RE: STRUTS and EJB
I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
RE: STRUTS and EJB
Title: RE: STRUTS and EJB Why not make a Value object for passing the information around, and have the form hold an instance of the value object? Derek. -Original Message- From: Juha Paananen [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
RE: STRUTS and EJB
Title: RE: STRUTS and EJB If a value object is used within the ActionForm for holding the form data, how should the html elements be named so that the data elements in the value object is automatically populated. Or should the data elements also reside in the ActionForm as separate fields, for which the setters and getters would go and get the information from the value object ? Anand Narayan -Original Message-From: Derek Longmuir [mailto:[EMAIL PROTECTED]]Sent: Thursday, August 23, 2001 1:46 PMTo: '[EMAIL PROTECTED]'Subject: RE: STRUTS and EJB Why not make a Value object for passing the information around, and have the form hold an instance of the value object? Derek. -Original Message- From: Juha Paananen [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except "extends ActionForm"), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: "Juha Paananen" [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and aftervalidating it in my Action class, store it into the db using a sessionEJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR ___ Juniper Bank "Rated #1 in Customer Confidence" Gomez Inc., Summer 2001 Internet Credit Card Scorecard www.juniper.com ___ This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on.
Re: STRUTS and EJB
Yes, the inheritance is a necessary part of the Struts design. I realize that it seems wasteful at first, but the ActionForm beans have several special needs that may not apply to the other beans in your application. An interface was tried in the earliest instances of the framework, but discarded for several reasons. The biggest one is that we may need to yet add another method, and if the ActionForm was an interface, everything would break ;-( The other reason was that people tried to turn their business beans into ActionForm beans, which is really not a good idea in practice (as seductive as it sounds ;-) For more see http://www.mail-archive.com/struts-user@jakarta.apache.org/msg08070.html and http://www.mail-archive.com/struts-dev@jakarta.apache.org/msg01495.html You should also take a look at the BeanUtils for quick and easy ways to populate beans. I add a toMap() method to all my ActionForm beans, which, with BeanUtils.populate() can be an easy way to populate your business beans. In fact, these are so useful, we moved them to theCommons for 1.1 ;-) -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Juha Paananen wrote: I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design?
RE: STRUTS and EJB
Title: RE: STRUTS and EJB html:text property=valueObjectA.someNumber size=5 maxlength=5 / Where the form has a Value object ValueObjectA, along with a public ValueObjectA getValueObjectA() method. The value object has a String someNumber in it, with a public String getSomeNumber() method. Doesn't one of the sample applications or Ted's examples show this a lot better? Derek. -Original Message- From: Narayan, Anand [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB If a value object is used within the ActionForm for holding the form data, how should the html elements be named so that the data elements in the value object is automatically populated. Or should the data elements also reside in the ActionForm as separate fields, for which the setters and getters would go and get the information from the value object ? Anand Narayan -Original Message- From: Derek Longmuir [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:46 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB Why not make a Value object for passing the information around, and have the form hold an instance of the value object? Derek. -Original Message- From: Juha Paananen [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
Re: STRUTS and EJB
I just updated the Struts-Simple example to demonstrate using nested beans in ActionForms and also with bean:write http://husted.com/about/struts/resources.htm#new Using a nested bean on your ActionForm lets you use the form like a wrapper, so you don't have to define everything twice, if your business beans and ActionForm beans would otherwise be identical. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Derek Longmuir wrote: html:text property=valueObjectA.someNumber size=5 maxlength=5 / Where the form has a Value object ValueObjectA, along with a public ValueObjectA getValueObjectA() method. The value object has a String someNumber in it, with a public String getSomeNumber() method. Doesn't one of the sample applications or Ted's examples show this a lot better? Derek. -Original Message- From: Narayan, Anand [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB If a value object is used within the ActionForm for holding the form data, how should the html elements be named so that the data elements in the value object is automatically populated. Or should the data elements also reside in the ActionForm as separate fields, for which the setters and getters would go and get the information from the value object ? Anand Narayan -Original Message- From: Derek Longmuir [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:46 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB Why not make a Value object for passing the information around, and have the form hold an instance of the value object? Derek. -Original Message- From: Juha Paananen [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
RE: STRUTS and EJB
Thanks very much. This nested property thing seems like a nice solution for the problem! -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 24. elokuuta 2001 0:08 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I just updated the Struts-Simple example to demonstrate using nested beans in ActionForms and also with bean:write http://husted.com/about/struts/resources.htm#new Using a nested bean on your ActionForm lets you use the form like a wrapper, so you don't have to define everything twice, if your business beans and ActionForm beans would otherwise be identical. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Derek Longmuir wrote: html:text property=valueObjectA.someNumber size=5 maxlength=5 / Where the form has a Value object ValueObjectA, along with a public ValueObjectA getValueObjectA() method. The value object has a String someNumber in it, with a public String getSomeNumber() method. Doesn't one of the sample applications or Ted's examples show this a lot better? Derek. -Original Message- From: Narayan, Anand [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB If a value object is used within the ActionForm for holding the form data, how should the html elements be named so that the data elements in the value object is automatically populated. Or should the data elements also reside in the ActionForm as separate fields, for which the setters and getters would go and get the information from the value object ? Anand Narayan -Original Message- From: Derek Longmuir [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:46 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB Why not make a Value object for passing the information around, and have the form hold an instance of the value object? Derek. -Original Message- From: Juha Paananen [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except extends ActionForm), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: Juha Paananen [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and after validating it in my Action class, store it into the db using a session EJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
RE: STRUTS and EJB
Title: RE: STRUTS and EJB But look at the mail send by Ted Husted asking not to use the Value Objects ( Business beans) inside the ActionForm bean Here it is -The other reason was that people tried to turn their business beans into ActionForm beans, which is really not a good idea in practice (as seductive as it sounds ;-) -Original Message-From: Derek Longmuir [mailto:[EMAIL PROTECTED]]Sent: Thursday, August 23, 2001 11:38 PMTo: '[EMAIL PROTECTED]'Subject: RE: STRUTS and EJB html:text property="valueObjectA.someNumber" size="5" maxlength="5" / Where the form has a Value object ValueObjectA, along with a "public ValueObjectA getValueObjectA()" method. The value object has a String someNumber in it, with a "public String getSomeNumber()" method. Doesn't one of the sample applications or Ted's examples show this a lot better? Derek. -Original Message- From: Narayan, Anand [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB If a value object is used within the ActionForm for holding the form data, how should the html elements be named so that the data elements in the value object is automatically populated. Or should the data elements also reside in the ActionForm as separate fields, for which the setters and getters would go and get the information from the value object ? Anand Narayan -Original Message- From: Derek Longmuir [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:46 PM To: '[EMAIL PROTECTED]' Subject: RE: STRUTS and EJB Why not make a Value object for passing the information around, and have the form hold an instance of the value object? Derek. -Original Message- From: Juha Paananen [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 1:47 PM To: [EMAIL PROTECTED] Subject: RE: STRUTS and EJB I also agree on that stuff that has references to STRUTS should not be transmitted to the EJB level. The problem here is simply that I would not want to make another, exactly similar (except "extends ActionForm"), class for transporting the information to the EJB. Of course, I can do that, but I don't like the idea. My question is, is this inheritance of ActionForm really necessary in Struts design? -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED]] Sent: 23. elokuuta 2001 20:29 To: [EMAIL PROTECTED] Subject: Re: STRUTS and EJB I agree with Gregor. The ActionForm beans are best left as ActionForm beans, and used only as an extension of the html:form tags. Once the data is validated, it should be transferred to persistent stoarge, or to another bean that is not bound to the HTTP layer (and could be re-used in other environments). This bean can then use the right data-type for the job, and perform other business tasks that have nothing to do with gathering input from HTTP. On the way back, a good way to repopulate an ActionForm bean, or other string-based helper, is to have your data access objects return a Map, and then use it with the standard BeanUtils.populate() method. Struts does the same thing with the HTTP request, which is basically a Map. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel +1 716 737-3463 -- http://www.husted.com/about/struts/ Gregor Rayman wrote: "Juha Paananen" [EMAIL PROTECTED] wrote: I want to fill in a form JavaBean using a struts form, and aftervalidating it in my Action class, store it into the db using a sessionEJB component. The proble here is that I have to extend ActionForm class to make the bean work with Struts. You can use containment instead of inheritance. You should avoid using Struts ActionForm on the business logic level. -- gR
Antwort: Re: STRUTS and EJB
I think UDDI and WSDL are just things on top of ejb's. They are for the outside world to access business oriented services to other applications or to people who want to access your apps with a different frontend. If you have apps that access something via soap, where is the apps which implements the soap interface at the inner side. ejb's serve this. Dirk Bitte antworten an [EMAIL PROTECTED] An:[EMAIL PROTECTED], Mark Simms [EMAIL PROTECTED] cc: Thema:Re: STRUTS and EJB Personally, I feel WSDL and UDDI complements EJB quite well. You can't implement business logic in WSDL; WSDL is just an interface definition using XML. EJB can't interface to another which is not RMI-based; WSDL and UDDI solves this problem. --- Mark Simms [EMAIL PROTECTED] wrote: Not to beat a dead horse, but isn't the new SOAP and XML initiatives along with UDDI and WSDL specifications going to make EJBs look a bit less attractive for certain transactional applications ?? BTW: that bye-bye struts article had little substance; it was an apparent attempt on the author's part to push his own MVC architecture. Also, anyone know why JavaReport allowed him to publish that trash ? __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ =?iso-8859-2?Q?$RFC822.eml?=
Re: STRUTS and EJB
Not to beat a dead horse, but isn't the new SOAP and XML initiatives along with UDDI and WSDL specifications going to make EJBs look a bit less attractive for certain transactional applications ?? BTW: that bye-bye struts article had little substance; it was an apparent attempt on the author's part to push his own MVC architecture. Also, anyone know why JavaReport allowed him to publish that trash ? - Original Message - From: Ritter, Steve [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, June 18, 2001 5:48 PM Subject: RE: java report article says bye-bye struts Bill, although I think this thread needs to die, I really wanted to hopefully relieve some of your confusion. EJB and Struts are COMPLETELY complementary technologies and I don't see how they compete with eachother at all. Struts is a web-application framework based on MVC, EJB is really a server side component architecture. If you are faced with the task of delivering web-based access to an EJB backend, then Struts is a perfect fit. Note, its not the only choice -- but IMHO it is one of the best choices from a framework standpoint. In general, your Struts Action classes (the contoller) will acquire references to EJB objects (session/entity beans) and use them to implement business logic. When using Struts in conjunction with EJB, Struts is really just concerned with the presentation logic and not so much with the business logic. That should be handled by your EJB's. In my development I routinely code pure-java (application) client to test out my EJB backend. Once that works building the Web presentation stuff with JSP's and Action classes is pretty straight-forward. I hope this is helpful, feel free to send me some email directly if you have more questions. --Steve -Original Message- From: Bill G [mailto:[EMAIL PROTECTED]] Sent: Monday, June 18, 2001 2:04 PM To: [EMAIL PROTECTED] Subject: RE: java report article says bye-bye struts Hi Craig, Although excellent in dealing with Web-based applications, Struts is not ready to take on EJB. This is a concern of mine as well but as a newbie to this technology, I am wondering how to adopt the Struts framework knowing that I will move to EJB's. Is it worth starting with Struts with the idea of moving to EJB's or what? Any info on this matter is seriously appreciated! Thanks BG... -Original Message- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Monday, June 18, 2001 11:14 AM To: '[EMAIL PROTECTED]' Subject: RE: java report article says bye-bye struts On Mon, 18 Jun 2001, Ritter, Steve wrote: Hi Hal, yeah I read the same article and couldn't help but laugh. Prashant really made some outlandish comments and hopefully those comments will diminish any negative impact his article might have on Struts (or, the adoption of Struts I should say). Craig, if you read this thread it might not be a bad idea to send a quick email to the editor's of Java Report and let them know about some of the mis-leading statements. Sounds like their review board needs a little re-org. Looks like I'll have to go buy a copy -- I don't pay a lot of attention to trade magazines in print, because production cycles make them so far out of date. Judging from the many thank-you's I've received for the 1.0 final release, I wouldn't worry to much about negative impact on Struts adoption. :-) --Steve Craig -Original Message- From: Deadman, Hal [mailto:[EMAIL PROTECTED]] Sent: Monday, June 18, 2001 7:52 AM To: 'Struts List' Subject: java report article says bye-bye struts Clearly there are too many java magazines and they will publish anything. In the July issue of Java Report there is an article titled Writing a Reusable Implementation of the MVC Design Pattern by Prashant Sarode from Brience. It's interesting because it has a section title of Bye-Bye Struts. The section starts out as follows: While the Struts framework is a powerful idea, it is not yet a product. Although excellent in dealing with Web-based applications, Struts is not ready to take on EJB. There are other gems in the article but I won't reproduce them all here. The premise of the article is that the author went looking for an MVC framework. He found the Blueprint document and liked that but it was too complicated. He then found Struts but apparently it didn't meet his need for a reusable implementation of the MVC pattern. Prashant must be a hard man to please. I think he wants one framework that can be used for both web applications and desktop applications. Personally I would rather share the model components and let my MVC framworks be a little less abstract and more useful to the task at hand. I
Re: STRUTS and EJB
Personally, I feel WSDL and UDDI complements EJB quite well. You can't implement business logic in WSDL; WSDL is just an interface definition using XML. EJB can't interface to another which is not RMI-based; WSDL and UDDI solves this problem. --- Mark Simms [EMAIL PROTECTED] wrote: Not to beat a dead horse, but isn't the new SOAP and XML initiatives along with UDDI and WSDL specifications going to make EJBs look a bit less attractive for certain transactional applications ?? BTW: that bye-bye struts article had little substance; it was an apparent attempt on the author's part to push his own MVC architecture. Also, anyone know why JavaReport allowed him to publish that trash ? __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
