July 2009 - jboss-dev-forums - Jboss List Archives

[Design of JCA on JBoss] - Re: Implementation of the ConnectionManager Service

by jesper.pedersen

A couple of other points - as I took a quick look. 5) Remove any deprecated functionality 6) Don't port the management layer (rewrite is needed) 7) Don't port the statistics layer (rewrite is needed) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247280#4247280 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247280

15 years, 5 months

1
0
0 / 0

[Design of Embedded JBoss] - Re: Is Embedded testsuite-full-dependency ready to use?

by ALRubinger

testsuite-full-dep is a work in progress, but should be in working form now (ie. I can run it). It's lacking some documentation though (that's next on my list after I chase down a heap error in Sun JDK x86_64). I'm not sure if these will fix your problems, but let's give it a spin. 1) Build AS Branch_5_x using build/build.sh. This creates the distribution. 2) Run "mvn clean install" on Branch_5_x/pom.xml. This puts the modules' SNAPSHOTs into your local M2 repo. 3) Set JAVA_HOME to Sun JDK 1.6 i586 4) Run "mvn clean install" on projects/embedded/trunk 5) Set JBOSS_HOME to the AS 5.x build you'd previously created 6) Run "mvn clean install" on projects/embedded/trunk/testsuite-full-dep S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247277#4247277 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247277

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: .classpath and .project to .svnignore

by kukeltje

I know how the setup is and It's not that it does not work, it's that because of using the maven plugin for eclipse (which works great), on importing the projects, the classpath and project file sometimes need regenerating. This results them being different than the ones checked in. So when syncing, I need to exclude them. Not a big deal, but I thought since using maven they are not needed since they can be easily generated. If others do need them, please leave it as it is, I'll work around it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247222#4247222 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247222

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM console repository moved

by heiko.braun＠jboss.com

The console has it's own JIRA space now: https://jira.jboss.org/jira/browse/BPMC View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247217#4247217 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247217

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - jBPM console repository moved

by heiko.braun＠jboss.com

The GWT Console sources have been moved to: https://svn.jboss.org/repos/soag/bpm-console/trunk View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247216#4247216 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247216

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: .classpath and .project to .svnignore

by tom.baeyens＠jboss.com

the idea is that the .classpath and .project should be the same for everyone. that is why they are checked in. instructions of how to set up eclipse with the maven plugin so that the classpaths are set up properly are explained in the wiki http://www.jboss.org/community/docs/DOC-13458 let us know if any of these assumptions is not correct or doesn't work for you. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247211#4247211 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247211

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Re-using the REST facade

by heiko.braun＠jboss.com

anonymous wrote : | All of the facades in server-core org.jboss.bpm.console.server need a public setter for ProcessEnginePlugin. | | A maven task goal needs to be added to the pom file that will create a jar file for server-core. | | Add a constructor to all the classes descending from JBPMIntegration that accepts a process engine. | That's nonsense. The integration layer does lookup the process engine from JNDI. Simply bind it to JNDI from your spring context and you are done. The same applies to running in tomcat and other containers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247168#4247168 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247168

15 years, 5 months

1
0
0 / 0

[Design of Embedded JBoss] - Is Embedded testsuite-full-dependency ready to use?

by jaikiran

I was just looking at running the testsuite-full-dependency against AS branch 5_x in Embedded. But looks like its testcases are having compile issues because of dependencies not being speicified in the pom: | [INFO] [compiler:testCompile] | [INFO] Compiling 10 source files to /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/target/test-classes | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD FAILURE | [INFO] ------------------------------------------------------------------------ | [INFO] Compilation failure | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/ejb3/entity/Jbossian.java:[26,24] package javax.persistence does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/ejb3/entity/Jbossian.java:[27,24] package javax.persistence does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/ejb3/entity/Jbossian.java:[28,24] package javax.persistence does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/ejb3/entity/Jbossian.java:[29,24] package javax.persistence does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/ejb3/entity/Jbossian.java:[40,1] cannot find symbol | symbol: class Entity | @Entity | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[26,20] package javax.servlet does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[27,20] package javax.servlet does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[28,25] package javax.servlet.http does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[29,25] package javax.servlet.http does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[30,25] package javax.servlet.http does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[32,24] package org.jboss.logging does not exist | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[42,42] cannot find symbol | symbol: class HttpServlet | public class JspForwardingServlet extends HttpServlet | | /NotBackedUp/jpai/business/jboss/wc/jbossas/projects/embedded/trunk/testsuite-full-dep/src/test/java/org/jboss/embedded/testsuite/fulldep/servlet/JspForwardingServlet.java:[52,24] cannot find symbol | symbol : class Logger | location: class org.jboss.embedded.testsuite.fulldep.servlet.JspForwardingServlet | .... // many more | The pom.xml of this component does not explicitly add these dependencies. Is this work in progress component? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247148#4247148 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247148

15 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Quartz MDB integration and classloader issues

by jaikiran

"ALRubinger" wrote : | | Nope. :) | | Interceptors are aspects; they encapsulate logic that runs across the core concerns of other components. So to dump them all in the same project would be counterproductive; we'd eventually build up a tangled mess of dependencies equivalent to the old "aspects" module of the AS. | I see what you mean. "ALRubinger" wrote : | So each interceptor should get its own component with release cycle. Then they can be plugged in at will. | As for this specific interceptor i don't see a reason why it needs to be in a new component. Infact the only reason this logic is going into an interceptor is to avoid repeated code all over the place, like what you say here: "ALRubinger" wrote : | Also, IMO we overuse interceptors. Oftentimes we leverage them just to break code out into some other space, | Given that this specific interceptor is going to put the right classloader on the thread, for use by components invoked by the container(s), i guess the core would be a right place for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247142#4247142 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247142

15 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Re-using the REST facade

by rmoskal

I do see how the cleanest way to do is is to replace the jbpm jboss service with one that publishes processEngine that is embedded in my spring context. This does tie me to JBoss which is not so bad. I also see a hack, which really doesn't seem so bad either. It basically involves short-circuiting your workflow engine neutral abstractions. It might even be worth it to incorporate these changes into the main code. Let me know what you think: I will simply create a jar file of everything in this module gwt-console/server/server-core to avoid mucking with the code. I'll make a subclass for all the rest facades that simply add a setter for the ProcessEnginePlugin. This way I can inject that directly from the spring context. It would be nice to add that to the actual classes. Then the only other thing that needs to be addressed are the classes in integration/console/src/main/java/org/jbpm/integration/console: TaskManagementImpl, ProcessEnginePluginImpl.java, etc.. The all extend from JBPMIntegration which gets the process engine from jndi: ProcessEngine)ctx.lookup("java:/ProcessEngine"); All I need to do then is to subclass each of these and replace the constructor with one that gets the process engine from the spring context. The nice thing is that these classes are all packaged as part of jbpm-console-integration.jar. Both the Facades and the JBPMIntegration integration classes will live on the spring framework. I'm not sute about the plugin stuff, but this will get me a free rpc layer for my app. I'll burn that bridge when I come to it. Now as far as I can tell, to simplify this integration all thats' needed is: All of the facades in server-core org.jboss.bpm.console.server need a public setter for ProcessEnginePlugin. A maven task goal needs to be added to the pom file that will create a jar file for server-core. Add a constructor to all the classes descending from JBPMIntegration that accepts a process engine. You know the code well, if you have time let me know if I've missed anything. If you think it is a reasonable idea, I'd be happy to help make the changes. Thanks and regards, Robert View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247122#4247122 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247122

15 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2009