Menu
▾
▴
jboss-dev-forums
|
From: <ad...@jb...> - 2005-05-03 14:39:03
|
So I guess the next stage in this track is to add AOP/Hibernate/EJB3 and make it into a real distribution. We should also identify the configuration kludges and trim where unnecessary things have leaked into the dependencies. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876274#3876274 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876274 |
|
From: <bil...@jb...> - 2005-05-03 14:53:45
|
how do you want to procede? Will you refactor TM/JCA/JNDI and put the POJO classes and such into the respective code bases? Also, we probably need a factory bean for the datasources. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876277#3876277 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876277 |
|
From: <ad...@jb...> - 2005-05-03 15:03:28
|
It should be discussed individually with the project leads. The API I have used for JCA is marked as "FOR TEST ONLY" but I think we need a more POJO/DI oriented api which the MBeans can be adapted to (rather than the other way around). I quite like the idea of using integration factories rather the JBoss code/classes directly. That way, it is easy to switch the implementation to for example use Tomcat's DataSource/JNDI/etc. Remember we also need to be able to do this across JBoss versions as well, so we must be careful that the API used is stable and intended for public use. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876284#3876284 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876284 |
|
From: <bil...@jb...> - 2005-05-03 16:10:06
|
"ad...@jb..." wrote : It should be discussed individually with the project leads. Well, between you and I we have most of it covered. Scott handles JNDI/Security. So, its us three. Remoting, Tom, would also have to be included. Minimally, we need * JNDI * TM * EJB3 * JCA Let me know if you have time for anything. I know the above code bases enough to proceed on my own if you have better things to do. I'll focus on EJB3 first since you seem to have all the base components I need to test a refactoring. So, again, how do you want to proceed? Who does what? anonymous wrote : | Remember we also need to be able to do this across JBoss versions as well, | so we must be careful that the API used is stable and intended for public use. Well, let's get a useful iteration before committing to any stable API. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876295#3876295 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876295 |
|
From: <ad...@jb...> - 2005-05-03 16:19:13
|
For JCA there already is this open task: http://jira.jboss.com/jira/browse/JBAS-1425 which is basically replacing what -ds.xml does with a javabean For JTA the pojo config problem is largely due to most of the config being package protected since it is assumed to be configured from the TransactionManagerService MBean. And the XIDFactory validates its own config in startService() which we don't support yet in the MC: http://jira.jboss.com/jira/browse/JBMICROCONT-23 I'd prefer it if these changes were discussed on the forum threads associated with those tasks so that everything is kept together for later reference. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876299#3876299 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876299 |
|
From: <ad...@jb...> - 2005-05-03 16:22:54
|
"bil...@jb..." wrote : | So, again, how do you want to proceed? Who does what? | Steve Ebersole was volunteering to help in a thread earlier this week: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63283 I have discussed the JCA issue with him before in relation to the hibernate deployer. I'd also guess he would be the best to get hibernate working? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876300#3876300 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876300 |
|
From: <ad...@jb...> - 2005-05-03 16:28:14
|
It might also be interesting to get someone from the JBoss/IDE project involved? i.e. bootstrap your own EJB3 inside eclipse for testing purposes. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876301#3876301 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876301 |
|
From: <bil...@jb...> - 2005-05-03 16:28:59
|
Hibernate is not a problem since EJB3 handles interaction with Hibernate. What I need is JCA/TM/JNDI. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876302#3876302 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876302 |
|
From: <ad...@jb...> - 2005-05-03 16:42:01
|
"bil...@jb..." wrote : Hibernate is not a problem since EJB3 handles interaction with Hibernate. What I need is JCA/TM/JNDI. Which is what the prototype does. So the next stage is to make it into a real standalone downloadable and identify kludges/improvements/haircuts with a roadmap on JIRA. I can do this, but I'd rather get on with my current roadmap/objectives 1) Finalize the XML 2) Ensure we have the integration with AOP working 3) Fixing some of the TODOs (like the lifecycle annotation) with tests These are basic foundations, it is not a wise idea to build things on sand ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876305#3876305 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876305 |
|
From: <bil...@jb...> - 2005-05-03 18:03:41
|
"ad...@jb..." wrote : "bil...@jb..." wrote : Hibernate is not a problem since EJB3 handles interaction with Hibernate. What I need is JCA/TM/JNDI. | | Which is what the prototype does. So the next stage is to make it into a real | standalone downloadable and identify kludges/improvements/haircuts with a roadmap | on JIRA. | | I can do this, but I'd rather get on with my current roadmap/objectives | 1) Finalize the XML | 2) Ensure we have the integration with AOP working | 3) Fixing some of the TODOs (like the lifecycle annotation) with tests | | These are basic foundations, it is not a wise idea to build things on sand ;-) Cool, ok, i'll work on this...start from where you've begun View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876317#3876317 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876317 |
|
From: <ste...@jb...> - 2005-05-04 14:40:02
|
So should I start on the JCA-bean stuff? Is that what makes the most sense priority-wise? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876424#3876424 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876424 |
|
From: <bil...@jb...> - 2005-05-04 14:57:05
|
sure. I'm working on TM/JNDI right now. Will move to JCA if you don't get to it this week. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876427#3876427 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876427 |
|
From: <ste...@jb...> - 2005-05-04 18:02:17
|
Bill emailed and said he is going to work on the JCA stuff. So I think I'll work on some Hibernate3 shit. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876476#3876476 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876476 |
|
From: <ad...@jb...> - 2005-05-04 19:42:35
|
JIRA Task: http://jira.jboss.com/jira/browse/EJBTHREE-144 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876494#3876494 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876494 |
|
From: <ad...@jb...> - 2005-05-04 19:53:10
|
We should probably also look at providing trimmed binaries for POJO/embeddable. e.g. There is no need to include org.jboss.resource.adapter.jdbc.remote or the jca deployer or the inbound jca processing, etc. In this case, JBoss/JCA could provide a jbosscx-core.jar (or whatever naming convention we want to use). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876496#3876496 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876496 |
|
From: <ad...@jb...> - 2005-05-04 22:25:38
|
I don't think JMS/timers/remoting and even security belong on this list for the first demo release. Unless you are talking about simple mock objects? We are trying to create an embeddable EJB3 container for use in something like a junit test. We are not trying to reproduce what will become JBoss5 under the auspices of an EJB3 demo. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876515#3876515 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876515 |
|
From: <bil...@jb...> - 2005-05-04 22:52:58
|
JCA is so tiny compared to everything else it doesn't really matter. Demoes are a waste of time. If this is just a demo, I'm stopping right now... BTW, TM, JNDI, EJB3 is 11.4 megabytes of jars so far. WHen I get JCA complete, we'll see how much else. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876524#3876524 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876524 |
|
From: <ad...@jb...> - 2005-05-04 23:10:23
|
Refactoring JBossMQ/JBossSX/etc. to be pojo based is going to take too much time for an initial release and it isn't something that is going to happen in JBoss4 anyway. It is wasted effort, especially, when there is a much easier mechanism provided by the AOP/MC JMX processing that allows the old JMX and the new MC to work together and a more "lazy" timescale for POJOizing the other services. The effort is about DEMOnstrating the ability to use EJB3 in a POJO environment, e.g. unit tests/Tomcat/etc. It is NOT an alternative to the full POJO environment solution which will come with JBoss5 or a replacement for the core solution which is JBossAS. It is however a step/bridge on the way that will show the direction and allow early adoption. Call it JBoss-4.2.x if you like. Anyway, that is just my opinion/focus. Hence the reason why I didn't want to spend time on this task. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876529#3876529 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876529 |
|
From: <ad...@jb...> - 2005-05-05 00:45:53
|
Just to clear in case you think I'm being arbitrary... If you examine the use case for EJB3 standalone and these services it fails the 5%/95% rule for the first release. Security junit: you aren't going to run your tests against the corporate ldap server tomcat: you'd use their native realm abstraction swing: it would only be useful if you are also operating in client/server mode and want single sign-on JMS If you want *co-located* jms and EJB3 you can use JBossAS/EJB3, otherwise you just need the jndi config for the remote jms. Remoting All you need is to marshall the invocation to simulate call-by-value and that is only so you can test remote access properly in junit. You aren't going to expose standalone EJB3 sessions remotely from Tomcat or Swing. etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876541#3876541 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876541 |
|
From: <tom...@jb...> - 2005-05-06 17:12:52
|
Is XMLKernelDeployer just a place holder? See that it is already deprecated in favor of BeanXMLDeployer. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876819#3876819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876819 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X