August 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by jaikiran

"ALRubinger" wrote : Jaikiran: | | Brian's been working on extending the Proxy component for use in a clustered environment, so let's be sure to get his approval on the timing before any commits. The current patch > JIRA > green light > commit approach we've been doing has been working well. :) | | S, | ALR Yes, that's how i plan to do this and other tasks - No commits without review/approval :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172125#4172125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172125

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Behavior difference in intra-AS EJB calls

by bstansberry＠jboss.com

"wolfc" wrote : A bean that has been looked up remotely, but that also exists locally should not be invoked locally. (Where local and remote are nodes which are not bound in the same cluster.) The behavior you describe is what existed for clustered beans looked up from a remote node: same cluster, go local, different cluster, go remote. I can reproduce that behavior with no problem w/ proxy-clustered. What's changed is the behavior of non-clustered beans -- before they went remote, now they go local. I found the threads related to EJBTHREE-773, and it's clear from those that the intent of Bill D's work was that the calls would go remote: http://www.jboss.com/?module=bb&op=viewtopic&t=104924 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101220 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172110#4172110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172110

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Behavior difference in intra-AS EJB calls

by wolfc

A bean that has been looked up remotely, but that also exists locally should not be invoked locally. (Where local and remote are nodes which are not bound in the same cluster.) https://jira.jboss.org/jira/browse/EJBTHREE-773 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172101#4172101 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172101

17 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Improvements

by ALRubinger

I'm looking into what it'll take to restrict a Maven deployment to snapshots that are available remotely, and with static version numbers. "epbernard" wrote : I think the right level for a CI / Snapshot use is to define the targeted branch (say 3.3 for Hibernate Core) at the Jboss AS level. From here, the snapshot build of JBoss AS should get the latest published snapshot for that release (ideally it should get it from SVN, I don't see why we should have to manually push a snapshot out). Interesting, presently we have no mapping between SCM location and libs. So the logic could become: 1) I depend on http://anonsvn.jboss.org/whatever/ 2) If SNAPSHOT location, checkout and build from source. If a release, use a cached lib available in repository.jboss.org A brief look into Maven sources reveals that this kind of thing strikes at the heart of a largely unpluggable/unmodular dependency resolution core, so this isn't as trivial as extending/enhancing a plugin. For instance, the Maven Dependency Plugin is really a hook, it doesn't actually perform any resolution as the name implies. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172085#4172085 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172085

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Classloading problem in proxy factories

by ALRubinger

This whole TCL thing was put in place because of some failures that became present in web injection. I'll remove it locally, look for affected areas, and see if there's a better way to solve the issue. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172084#4172084 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172084

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by ALRubinger

Jaikiran: Brian's been working on extending the Proxy component for use in a clustered environment, so let's be sure to get his approval on the timing before any commits. The current patch > JIRA > green light > commit approach we've been doing has been working well. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172083#4172083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172083

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Behavior difference in intra-AS EJB calls

by ALRubinger

Some more clarification (and also for the record so I can remember): Proxy Factories are created on the server and registered with MC (and, if remote, with Dispatcher). Remote JNDI lookups create a PojiProxy to the Dispatcher to get at the Proxy Factory, calling upon it to return the Proxy. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172079#4172079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172079

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Behavior difference in intra-AS EJB calls

by bstansberry＠jboss.com

Just to clarify; my initial post was inaccurate. Issue is with the proxy to the proxy factory that is created client-side via ProxyObjectFactory.createProxyFactoryProxy(). That results in a proxy that uses an IsLocalProxyFactoryInterceptor that is instantiated client-side. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172078#4172078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172078

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Behavior difference in intra-AS EJB calls

by bstansberry＠jboss.com

The old behavior could be restored easily enough by adding a StringRefAddr with some sort of vmid/long to the Reference. Then the ObjectFactory uses a constructor method on IsLocalProxyFactoryInterceptor that gets passed the vmid. Or a factory method on IsLocalProxyFactoryInterceptor that returns a 'singleton', either IsLocalProxyFactoryInterceptor.local or IsLocalProxyFactoryInterceptor.remote. If you guys think that's a valid thing to do, I can do it pretty quick; an existing clustering test already tests this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172072#4172072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172072

17 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Improvements

by pgier

"epbernard" wrote : well I was more thinking about an extreme version of that. A extreme CI. | You take all snapshots of all projects all the time. So you see shit coming and you see when you break 95% of the app server. I just wanted to note that this is how maven is set up normally. It will by default check daily for updates of snapshot dependencies. And how the AS build was working until Dimitrius started locking down versions to do a release. One of the problems is that in order to do a beta or RC release of the app server the versions of the components have to be locked down otherwise you have a build that is not reproducible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172059#4172059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172059

17 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2008