Alright, the question might be broad. We've been looking at Jboss and a few other similar app. servers.
好吧,问题可能很广泛。我们一直在关注Jboss和其他一些类似的应用程序。服务器。
From the feature list it would be perfect for replacing our soon to be outdated homegrown reporting application on the server side. But at this point, for 2 developers, just grasping all the setup, configuration, administration, tuning,testing not to mention the APIs and programming itself just seems way too much, too big, too complex.
从功能列表中,它将非常适合在服务器端替换我们即将过时的本土报表应用程序。但在这一点上,对于2位开发人员来说,只需掌握所有的设置,配置,管理,调优,测试,更不用说API和编程本身似乎太过分,太大,太复杂。
What path does people take to become familiar and productive with such application servers ?
人们用这种应用服务器熟悉和高效的路径是什么?
4 个解决方案
#1
Start with a simple one, and only use a more complex one if you really need the features.
从一个简单的开始,如果你真的需要这些功能,只使用更复杂的一个。
For example, Do you really need the full JBoss stack? Would Tomcat not be sufficient? It's much less of a handful.
例如,你真的需要完整的JBoss堆栈吗? Tomcat不够吗?它少了一把。
#2
I would approach this the same way I approach anything new.
我会像处理任何新事物一样处理这个问题。
Start with the documentation - read the introduction and basic setup/configuration documents. Then move on to tutorials and maybe some simple apps that I find interesting. In your case, maybe port a few features over to the new system. As time goes on, you should get better with the tools at hand.
从文档开始 - 阅读介绍和基本设置/配置文档。然后转到教程,也许还有一些我感兴趣的简单应用程序。在您的情况下,可能将一些功能移植到新系统。随着时间的推移,你应该用手头的工具做得更好。
#3
From my experience using one is the best way to learn what you like/dislike about it. Once you have a project set up for one application server it should not be too much work to migrate it to another. I am currently working on an application that we develop & test daily using a simple Tomcat v6 server, but which runs in production on both Websphere Application Server and JBoss.
根据我使用one的经验,这是了解你喜欢/不喜欢它的最佳方式。为一个应用程序服务器设置项目后,将其迁移到另一个应用程序服务器应该不会太多。我目前正在开发一个应用程序,我们每天使用一个简单的Tomcat v6服务器开发和测试,但它在生产环境中运行在Websphere Application Server和JBoss上。
As a side note for your development, I strongly recommend looking into integrating your Eclipse development environment with your chosen application server through server adapters - it will greatly speed up development tasks and simplify the debugging process.
作为开发的附注,我强烈建议您考虑通过服务器适配器将Eclipse开发环境与您选择的应用程序服务器集成 - 这将大大加快开发任务并简化调试过程。
#4
I'd say that the minimum features for using Java EE are:
我要说使用Java EE的最低功能是:
- Servlets and JSPs, written using JSTL (no scriptlets)
- JDBC
- JNDI for pooling database connections (optional but recommended)
- Basic authentication for security
使用JSTL编写的Servlet和JSP(无scriptlet)
用于汇集数据库连接的JNDI(可选但建议)
安全性的基本认证
You can accomplish a great deal knowing just those. If you want to minimize the learning curve, I'd recommend starting with those and staying away from EJBs, JMS, Struts, JSF, etc.
知道这些就可以完成很多事情。如果你想最小化学习曲线,我建议从那些开始,远离EJB,JMS,Struts,JSF等。
Another benefit is that this subset of features is common to both servlet/JSP engines, like Tomcat, Jetty, Resin, etc. and full-blown Java EE app servers like WebLogic, JBOSS, WebSphere, etc. An app that runs on one should be portable to any of the others, as long as you stay away from app engine-specific extensions.
另一个好处是这个功能子集对于servlet / JSP引擎都是通用的,如Tomcat,Jetty,Resin等,以及完整的Java EE应用服务器,如WebLogic,JBOSS,WebSphere等。运行在一个应用程序上的应用程序应该是只要您远离特定于应用程序引擎的扩展程序,就可以移植到任何其他程序。
You should realize that there's a trade-off here. You'll have to develop pieces that might be easier if you leverage the app server more. But hopefully you'll start with some simpler problems and work your way up once you're comfortable with the basics.
你应该意识到这里有一个权衡。如果您更多地利用应用服务器,则必须开发可能更容易的部分。但是,希望你从一些更简单的问题开始,一旦你对基础知识感到满意就会一路走来。
There's another approach: Hire an experienced guide to help you with training and mentoring for the first project. A six-month gig with a reputable consulting firm might get you started.
还有另一种方法:聘请经验丰富的导游帮助您完成第一个项目的培训和指导。与信誉良好的咨询公司进行为期六个月的演出可能会让您开始。
Last of all, I'd recommend Spring. It would also have a learning curve, but it's a good alternative to Java EE EJB development.
最后,我推荐Spring。它也有一个学习曲线,但它是Java EE EJB开发的一个很好的替代品。
#1
Start with a simple one, and only use a more complex one if you really need the features.
从一个简单的开始,如果你真的需要这些功能,只使用更复杂的一个。
For example, Do you really need the full JBoss stack? Would Tomcat not be sufficient? It's much less of a handful.
例如,你真的需要完整的JBoss堆栈吗? Tomcat不够吗?它少了一把。
#2
I would approach this the same way I approach anything new.
我会像处理任何新事物一样处理这个问题。
Start with the documentation - read the introduction and basic setup/configuration documents. Then move on to tutorials and maybe some simple apps that I find interesting. In your case, maybe port a few features over to the new system. As time goes on, you should get better with the tools at hand.
从文档开始 - 阅读介绍和基本设置/配置文档。然后转到教程,也许还有一些我感兴趣的简单应用程序。在您的情况下,可能将一些功能移植到新系统。随着时间的推移,你应该用手头的工具做得更好。
#3
From my experience using one is the best way to learn what you like/dislike about it. Once you have a project set up for one application server it should not be too much work to migrate it to another. I am currently working on an application that we develop & test daily using a simple Tomcat v6 server, but which runs in production on both Websphere Application Server and JBoss.
根据我使用one的经验,这是了解你喜欢/不喜欢它的最佳方式。为一个应用程序服务器设置项目后,将其迁移到另一个应用程序服务器应该不会太多。我目前正在开发一个应用程序,我们每天使用一个简单的Tomcat v6服务器开发和测试,但它在生产环境中运行在Websphere Application Server和JBoss上。
As a side note for your development, I strongly recommend looking into integrating your Eclipse development environment with your chosen application server through server adapters - it will greatly speed up development tasks and simplify the debugging process.
作为开发的附注,我强烈建议您考虑通过服务器适配器将Eclipse开发环境与您选择的应用程序服务器集成 - 这将大大加快开发任务并简化调试过程。
#4
I'd say that the minimum features for using Java EE are:
我要说使用Java EE的最低功能是:
- Servlets and JSPs, written using JSTL (no scriptlets)
- JDBC
- JNDI for pooling database connections (optional but recommended)
- Basic authentication for security
使用JSTL编写的Servlet和JSP(无scriptlet)
用于汇集数据库连接的JNDI(可选但建议)
安全性的基本认证
You can accomplish a great deal knowing just those. If you want to minimize the learning curve, I'd recommend starting with those and staying away from EJBs, JMS, Struts, JSF, etc.
知道这些就可以完成很多事情。如果你想最小化学习曲线,我建议从那些开始,远离EJB,JMS,Struts,JSF等。
Another benefit is that this subset of features is common to both servlet/JSP engines, like Tomcat, Jetty, Resin, etc. and full-blown Java EE app servers like WebLogic, JBOSS, WebSphere, etc. An app that runs on one should be portable to any of the others, as long as you stay away from app engine-specific extensions.
另一个好处是这个功能子集对于servlet / JSP引擎都是通用的,如Tomcat,Jetty,Resin等,以及完整的Java EE应用服务器,如WebLogic,JBOSS,WebSphere等。运行在一个应用程序上的应用程序应该是只要您远离特定于应用程序引擎的扩展程序,就可以移植到任何其他程序。
You should realize that there's a trade-off here. You'll have to develop pieces that might be easier if you leverage the app server more. But hopefully you'll start with some simpler problems and work your way up once you're comfortable with the basics.
你应该意识到这里有一个权衡。如果您更多地利用应用服务器,则必须开发可能更容易的部分。但是,希望你从一些更简单的问题开始,一旦你对基础知识感到满意就会一路走来。
There's another approach: Hire an experienced guide to help you with training and mentoring for the first project. A six-month gig with a reputable consulting firm might get you started.
还有另一种方法:聘请经验丰富的导游帮助您完成第一个项目的培训和指导。与信誉良好的咨询公司进行为期六个月的演出可能会让您开始。
Last of all, I'd recommend Spring. It would also have a learning curve, but it's a good alternative to Java EE EJB development.
最后,我推荐Spring。它也有一个学习曲线,但它是Java EE EJB开发的一个很好的替代品。