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

[Design the new POJO MicroContainer] - JBoss Reliance Project

by adrian＠jboss.org

I've created a project for reliance JIRA http://jira.jboss.com/jira/browse/JBREL SVN [url][https://svn.jboss.org/repos/jbossas/projects/reliance//url] The reason for moving these out of the microcontainer is that I don't want a circular dependency from reliance -> deployers - > microcontainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135410#4135410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135410

18 years, 1 month

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - StatefulHandleImpl in 4.x

by Frito

When migrating a huge application from JBoss 3.2.7 to JBoss 4.0 (and then to JBoss 4.2), I found some strange behaviour which I filed as a bug (http://jira.jboss.org/jira/browse/JBAS-5302) and some implementation details which I wanted to discuss here (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=123553), probably the wrong forum... many views, no comment ;-) Reading the sources and the EJB spec lead me to these questions: 1.) Why has the 3.2.7 compatibility not been implemented, using the invokerProxyBinding instead of doing a fresh lookup? The StatefulHandleImpl stores the "old" values when the property "org.jboss.ejb.sfsb.handle.V327" is set, but it doesn't use them. I tried to port the 3.2.7 implementation to the getEJBObject method, evaluating the property, and it worked for me in a non clustered environment (JBoss 4.0.7). 2.) JBoss implementations (as the StatefulHandleImpl) sometimes rely on "new InitialContext()". We sometimes come up, that a thread on a client didn't ever do a lookup by himself using new InitialContext(properties) and the system properties are not set at all. Must the client programmer provide informations, that a "new InitialContext()" works consistent, or must the implementation not rely on the use of getting a new initial context without "seeing" the right properties? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135403#4135403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135403

18 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - jBPM With Seam

by divakar.satyanarayan

Hi, We are exploring options of using jBPM with Seam for a workflow process. We had certain queries around the approach that we are planning to take. 1. We plan to retrieve tasklist and assign task to the user using jBPM API's and not through Seam annotations as we found out that annotations dont provide the kind of flexibility that we need. We are not sure how would the application behave in following scenario a. User kicks of a workflow process. Process is in progress. b. Lets assume that we have some production issue and we fix the bug and redeploy the Seam Application. NOw since jPDL file is part of Seam application, jPDL would also get deployed and a new version is assigned to this. What would happen to processes that were in progress? How would task retrieval work since you dont have access to process id that was instantiated? c. Lets assume that I modify the workflow and redeploy the process definition. How would the tasks that were pending behave when we have new process defined? Are there any documentation available that we can look through for these scenarios? Divakar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135401#4135401 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135401

18 years, 1 month

1
0
0 / 0

[Design of OSGi Integration] - Re: new OSGi project

by alesj

In order not to confuse people now, what's the best way to 'deprecate' this project: - http://anonsvn.jboss.org/repos/jbossas/projects/osgi/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135398#4135398 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135398

18 years, 1 month

1
0
0 / 0

[Design of OSGi Integration] - new OSGi project

by adrian＠jboss.org

I've moved the OSGi code to here from the microcontainer: https://svn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135396#4135396 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135396

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JarEntry as VFS root does not return empty vfspath

by alesj

"scott.stark(a)jboss.org" wrote : but I suspect we need to redo how we handle jars to not rely on JarFile. | Scott, what are some of the things you've already looked at, for this issue? If we just ironed these details from those projects... How does this relate with the urlconn-work branch? Or what's that status of that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135394#4135394 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135394

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBoss Managed as an external project

by adrian＠jboss.org

"mark.spritzler" wrote : Adrian, sorry for the stupid question, | | But are the old maven managed and metatype artifact names now combined into jboss-man-aggregator? | | We had | | | | <dependency> | | <groupId>org.jboss.man</groupId> | | <artifactId>jboss-managed</artifactId> | | <version>${microcontainer.version}</version> | | <scope>provided</scope> | | </dependency> | | | | <dependency> | | <groupId>org.jboss.man</groupId> | | <artifactId>jboss-metatype</artifactId> | | <version>${microcontainer.version}</version> | | <scope>provided</scope> | | </dependency> | | | | in our pom for dependencies, and I am updating it. | | Thanks | | Mark You just need to depend on org.jboss.man:jboss-managed the metatype dependency will be automatic as a transitive dependency. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135393#4135393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135393

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Splitting the rest of MC

by alesj

Perhaps putting a Category here: - http://jira.jboss.com/jira/secure/BrowseProjects.jspa To get all the newly created JIRAs under same category/group - MC or something ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135389#4135389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135389

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Splitting the rest of MC

by alesj

"adrian(a)jboss.org" wrote : Give me chance to finish it then I'll explain it in due course. | OK, I'll restrain myself for a bit more. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135383#4135383 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135383

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - JBoss Deployers Project

by adrian＠jboss.org

There's a new JBoss Deployers Project JIRA http://jira.jboss.com/jira/browse/JBDEPLOY SVN https://svn.jboss.org/repos/jbossas/projects/jboss-deployers/ MAVEN http://repository.jboss.com/maven2/org/jboss/deployers Again the maven repository is empty partly because it needs an MC Beta11 release and partly because there's 4 outstanding tasks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135380#4135380 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135380

18 years, 1 month

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 March 2008