[JBoss Transactions Development] - Re: TransactionManager and AS' ServiceBindingManager
by Vilmar Silva
Vilmar Silva [http://community.jboss.org/people/vbs001] created the discussion
"Re: TransactionManager and AS' ServiceBindingManager"
To view the discussion, visit: http://community.jboss.org/message/589550#589550
--------------------------------------------------------------
Hi, I would like jboss 5; use the ports file ports-binding.xml to distribute the various instances as I do in jboss 4.2.2.; do it like this:
.. / jboss-5.0.1.GA / bin / ports-binding.xml
. / conf / service-jboss.xml
tag <- <mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:service=ServiceBindingManager">
<attribute name="ServerName"> ports-default </ attribute>
<attribute name="StoreURL"> /jboss-5.0.1.GA/ bin / port-bindings.xml </ attribute>
<attribute name="StoreFactoryClassName"> org.jboss.services.binding.XMLServicesStoreFactory </ attribute>
</ mbean>
ports are passed by the generic file /jboss/server/defautl/generic-port, for example generic-port
port.prefix=8
/bin/ksh -x /jboss-5.0.1.GA/bin/run.sh -c default -b 0.0.0.0 -P /jboss-5.0.1.GA/server/default/generic-port
Error displayed after setting:
12:50:32,249 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/opt/jboss-5.0.1.GA/server/default/conf/jboss-service.xml state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.system:service=ServiceBindingManager
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:118)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:274)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: jboss.system:service=ServiceBindingManager is already installed.
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:716)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at org.jboss.system.ServiceController.doInstall(ServiceController.java:670)
at org.jboss.system.ServiceController.install(ServiceController.java:273)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)
... 23 more
12:50:32,682 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/opt/jboss-5.0.1.GA/server/default/conf/jboss-service.xml" is in error due to the following reason(s): java.lang.IllegalStateException: jboss.system:service=ServiceBindingManager is already installed.
12:50:32,686 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 33s:243ms
^C12:50:51,718 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
12:50:54,817 INFO [ServerImpl] Shutdown complete
Shutdown complete
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/589550#589550]
Start a new discussion in JBoss Transactions Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss AS Development Deployment Framework] - I am looking for a JBOSS Software Engineer III for our Reno Nevada office
by Monique Moultrie
Monique Moultrie [http://community.jboss.org/people/mmoultrie] created the discussion
"I am looking for a JBOSS Software Engineer III for our Reno Nevada office"
To view the discussion, visit: http://community.jboss.org/message/589114#589114
--------------------------------------------------------------
Hello,
My name is Monique Moultrie and I am looking for a JBOSS Software Engineer III for our Reno Nevada office. I have enclosed a brief description for your review. If you or anyone you know is interested please send resume to monique.moultrie(a)sncorp.com (mailto:monique.moultrie@sncorp.com)
Thank you,
Monique Moultrie
Talent Acquisition Specialist III
Sierra Nevada Corporation
monique.moultrie(a)sncorp.com (mailto:monique.moultrie@sncorp.com)
Software Engineer III
Sierra Nevada Corporation's Intelligence, Surveillance, and Reconnaissance - Persistence Surveillance (ISR-PSS) group is looking for a Software Engineer III to join our team in the design, development and deployment of Java Enterprise Edition infrastructure and applications related to managing mission control and video delivery systems. ISR is the fastest growing division within SNC and seeks highly motivated individuals to join our team in Sparks, NV.
Sparks is immediately adjacent to Reno and only 20 minutes drive from scenic Lake Tahoe in the heart of the Sierra. In addition to the night life, this area offers world class skiing, mountain biking, backpacking, hiking, kayaking – all of the outdoor adventures imaginable.
If you are ready to work alongside some of the industry’s top engineers and scientists to shape the future of this field, then now is the time to make SNC part of your future. Look over the available position below and apply as indicated. We look forward to hearing from you.
As a Software Engineer III, you will:
•Work directly with the chief software architect to design, implement, integrate and test.
•Develop suitable parallelization strategies based on the algorithm and underlying hardware.
•Collaborate with other engineers to evaluate interfaces between hardware and software.
•Determine operational performance requirements of the overall system.
•Develop and implement test procedures and documentation.
•Troubleshoot designs operating within an integrated system.
The ideal candidate will be proficient in all aspects of Java Enterprise design and development and have significant experience with programming and tools in one or more of the following domains: video and imagery distribution, signals processing, or mission planning.
Basic Qualifications:
•BS or MS degree in Computer Science or Electrical Engineering and at least 6+ years experience
•Java Enterprise Edition (J2EE5 or J2EE6) including Enterprise Java Beans (EJB3)
•Experience developing and deploying infrastructure using RedHat JBoss
•Web services protocols (SOAP, WSDL, XML)
•Development, testing, and debugging on Linux systems (preferably Redhat)
•Familiar with software tools (jUnit, Subversion, Eclipse)
•Experience in optimizing code for specific hardware characteristics
•Create Software Architecture, Design Documents, and Test Plans
•Occasional travel will be required to various facilities to assist with ground/flight system testing.
JBoss knowledge is a critical requirement for this exciting position since it is the underlying application control software for an ongoing SNC program.
We need a JBoss middleware expert that will help define the application server using the RedHat JBoss middleware for the next version of this ongoing software development effort and provide troubleshooting tools for application control.
U.S. Citizenship is required, since the ability to obtain a U.S. Government security clearance is mandatory.
Preferred Qualifications:
• Experience with Adobe FLEX
• Experience with video distribution and image processing
• Experience with RAID and Network Attached Storage
• Experience with Oracle Databases
*SNC is an EEO employer committed to recruiting a diverse workforce.
Apply online for immediate consideration at http://www.sncorp.com/ or send inquiries to Monique.Moultrie(a)SNCorp.com (mailto:Monique.Moultrie@SNCorp.com)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/589114#589114]
Start a new discussion in JBoss AS Development Deployment Framework at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss Web Development] - HornetQ message count.
by Rishi k
Rishi k [http://community.jboss.org/people/rishi321] created the discussion
"HornetQ message count."
To view the discussion, visit: http://community.jboss.org/message/588957#588957
--------------------------------------------------------------
| |
Hi all,
I am new to HOrnetQ, I need to get message count from HornetQ running on Jboss6Final.But it shows the following error:
ExpiryQueuejava.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:338) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at com.jboss.embedded.TestNG.TestCounters.main(TestCounters.java:51)Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325) at javax.naming.InitialContext.lookup(InitialContext.java:392) at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886) at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) ... 2 more
Here is my code |
public static void main(String[] args){
Context lContext=null;
Connection Hconn=null;
ConnectionFactory Hconnection=null;
HornetQQueue q=null;
ObjectName on;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
ht.put(Context.PROVIDER_URL, "xx.xx.xxx.xx");
ht.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
try{
lContext = new InitialContext(ht);
Hconnection = (ConnectionFactory) lContext.lookup("ConnectionFactory");
q = (HornetQQueue) lContext.lookup("/queue/ExpiryQueue");
//System.out.println(q.getQueueName());
on = ObjectNameBuilder.DEFAULT.getJMSQueueObjectName(q.getQueueName());
JMXServiceURL url = new JMXServiceURL("rmi", "xx.xx.xxx.xx", 1099, "/jndi/jmx");
JMXConnector cntor = JMXConnectorFactory.connect(url, ht);
MBeanServerConnection mbsc = cntor.getMBeanServerConnection();
JMSQueueControl queueControl = (JMSQueueControl)MBeanServerInvocationHandler.newProxyInstance(mbsc, on, JMSQueueControl.class, false);
String counters = queueControl.listMessageCounter();
//System.out.print(counters);
MessageCounterInfo messageCounter = MessageCounterInfo.fromJSON(counters);
System.out.format("%s message(s) in the queue (since last sample: %s)\n",messageCounter.getDepth(),messageCounter.getDepthDelta());
} catch (Exception e) {
e.printStackTrace();
}
}
What seems to be wrong ?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588957#588957]
Start a new discussion in JBoss Web Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
[JBoss AS7 Development] - Hacking on AS7
by David Lloyd
David Lloyd [http://community.jboss.org/people/dmlloyd] modified the document:
"Hacking on AS7"
To view the document, visit: http://community.jboss.org/docs/DOC-15596
--------------------------------------------------------------
h4. 1. Create a github account
http://github.com http://github.com
h4. 2. Fork jboss-as into your account
http://github.com/jbossas/jboss-as http://github.com/jbossas/jboss-as
h4. 3. Clone your newly forked copy onto your local workspace
$ git clone git@github.com:[your user]/jboss-as.git
Initialized empty Git repository in /devel/jboss-as/.git/
remote: Counting objects: 2444, done.
remote: Compressing objects: 100% (705/705), done.
remote: Total 2444 (delta 938), reused 2444 (delta 938)
Receiving objects: 100% (2444/2444), 1.71 MiB | 205 KiB/s, done.
Resolving deltas: 100% (938/938), done.
$ cd jboss-as
h4. 4. Add a remote ref to upstream, for pulling future updates
git remote add upstream git://github.com/jbossas/jboss-as.git
h4. 5. Use maven (via build.sh) (make sure you use maven 3)
$ ./build.sh install
.....
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: BOM ..................... SUCCESS [1.834s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [0.022s]
[INFO] JBoss Application Server: Domain Core ............. SUCCESS [3.051s]
[INFO] JBoss Application Server: Server Manager .......... SUCCESS [0.204s]
[INFO] JBoss Application Server: Server .................. SUCCESS [0.283s]
[INFO] JBoss Application Server: Domain Controller ....... SUCCESS [0.084s]
[INFO] JBoss Application Server: Process Manager ......... SUCCESS [0.314s]
[INFO] JBoss Application Server: Remoting ................ SUCCESS [0.390s]
[INFO] JBoss Application Server: Build ................... SUCCESS [5.696s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
h4. 6. Pulling later updates from upstream
$ git pull --rebase upstream master
>From git://github.com/jbossas/jboss-as
* branch master -> FETCH_HEAD
Updating 3382570..1fa25df
Fast-forward
{parent => bom}/pom.xml | 70 ++++----------
build/pom.xml | 13 +--
domain/pom.xml | 10 ++
.../src/main/resources/examples/host-example.xml | 2 +-
.../resources/examples/jboss-domain-example.xml | 28 +++---
.../main/resources/schema/jboss-domain-common.xsd | 12 +--
.../main/resources/schema/jboss-domain-host.xsd | 2 +-
domain/src/main/resources/schema/jboss-domain.xsd | 17 ++--
pom.xml | 100 ++++++++++++++++++--
process-manager/pom.xml | 3 +-
10 files changed, 156 insertions(+), 101 deletions(-)
rename {parent => bom}/pom.xml (85%)
(--rebase will automatically move your local commits, if you have any, on top of the latest branch you pull from, you can leave it off if you do not). Please note that --rebase is very important if you do have commits. What happens is that when git pull can't fast forward, it does a merge commit, and a merge commit puts the sucked in changes ON TOP of yours whereas a rebase puts them BELOW yours. In other words a merge commit makes the history a graph, and we prefer a cleaner, easier to follow linear history (hence the rebasing). Further once you do a merge commit it will be difficult to rebase the history before that commit (say you want to combine two commits to one later) as described in point 12.
One way to not forget --rebase the rebase option is you may want to create an alias
$ git config --global alias.up "pull --rebase"
and then just use the new alias instead of pull
$ git up upstream master
One last option, which some prefer, is to avoid using pull altogether, and just use fetch + rebase (this is of course more typing)
h4. 7. Pushing pulled updates (or local commits if you aren't using topic branches) to your private github repo (origin)
$ git push
Counting objects: 192, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (44/44), done.
Writing objects: 100% (100/100), 10.67 KiB, done.
Total 100 (delta 47), reused 100 (delta 47)
To git@github.com:[your user]/jboss-as.git
3382570..1fa25df master -> master
You might need to say -f to force the changes. Read the note on 12 though before you do it.
h4. 8. Discuss your planned changes (if you want feedback)
* On the forums - http://community.jboss.org/en/jbossas/dev/jboss_as7_development http://community.jboss.org/en/jbossas/dev/jboss_as7_development
* On IRC - irc://irc.freenode.org/jboss-as7 or https://webchat.freenode.net/?channels=jboss-as7 (http://webchat.freenode.net/?channels=jboss-as7)
h4. 9. Make sure there is a JIRA somewhere for the enhancement/fix
http://jira.jboss.org http://jira.jboss.org
h4. 10. Create a simple topic branch to isolate that work (just a recommendation)
git checkout -b my_cool_feature
h6. Note: See tips section for how to use a nice git prompt for tracking what branch you are in!
h4. 11. Make the changes and commit one or more times (Don't forget to push)
git commit -m 'JBAS-XXXX Frunubucate the Fromungulator'
git commit -m 'JBAS-YYYY Tripple Performance of Fromungulation'
git push my_cool_feature
+Note that git push references the branch you are pushing and defaults to master, *not your working branch*.+
h4. 12. Rebase your branch against the latest master (applies your patches on top of master)
git fetch upstream
git rebase -i upstream/master
# if you have conflicts fix them and rerun rebase
# The -f, forces the push, alters history, see note below
git push -f my_cool_feature
The -i triggers an interactive update which also allows you to combine commits, alter commit messages etc. It's a good idea to make the commit log very nice for external consumption. Note that this alters history, which while great for making a clean patch, is unfriendly to anyone who has forked your branch. Therefore you want to make sure that you either work in a branch that you don't share, or if you do share it, tell them you are about to revise the branch history (and thus, they will then need to rebase on top of your branch once you push it out).
h4. 13. Get your changes merged into upstream
1. Make sure your repo is in sync with other unrelated changes in upstream before requesting your changes be merged into upstream by repeating step 12.
2. Email a pull request to mailto:jbossas-pull-requests@lists.jboss.org jbossas-pull-requests(a)lists.jboss.org (if I haven't subscribed the list, do it https://lists.jboss.org/mailman/listinfo/jbossas-pull-requests here) with a link to your repo, a description of the changes, and who reviewed (if any)
3. After review a maintainer will merge your patch, update/resolve issues by request, and reply when complete
4. Don't forget to switch back to master and pull the updates1. git checkout master
git pull upstream master
h4. Appendix A. Adding a new external dependency
1. Edit pom.xml and add a property of the form "version.groupId.artifactId" which contains the Maven version of the dependency. Add your dependency to the <dependencyManagement> section, and use the property for the version. If your new dependency has any transitive dependencies, be sure to <exclude> them (or if possible, update the project so that all its dependencies are of *provided* scope).
2. Add your dependency to any AS modules that require it, but only with group/artifact.
3. Edit build/pom.xml and add your dependency with only group/artifact.
4. Create a directory in build/src/modules corresponding to the *module's* name (which will differ from the Maven group/artifact name; look at other modules to get a feel for the naming scheme), with a version of "main", like this: "build/src/modules/org/jboss/foo/main".
5. Create a module.xml file inside the "main" directory. Use a module.xml from another similar module as a template.
6. Edit build/build.xml and add a <module-def> element. The name listed in the <module-def> element corresponds to the *module* name. The group/artifact listed in the nested maven-resource element(s) refer to the *Maven* group/artifact name.
7. *Important:* Make sure you did not introduce any transitive dependencies by using "mvn dependency:tree". If you did, be sure to add <exclusion>s for each of them to your dependency as described above.
8. *Important:* Do *not* introduce a dependecy on the "*system*" module. If you need access to JDK classes which are not covered by any other dependency, use the "javax.api" module as a dependency.
Please be sure to preserve the alphabetical ordering of all POMs and the build.xml file.
h4. Appendix B. Adding a new AS submodule
1. Create the directory corresponding to the submodule and add it to the root pom.xml file. The convention is to leave off the "jboss-as-" portion, so "jboss-as-remoting" becomes "remoting".
2. Create a POM for your submodule (use another submodule as a template). Make sure all dependencies you specify do *not* include a version. The group ID should be "org.jboss.as", and the artifact ID should begin with "jboss-as-" and there should be a proper <name> for the new module.
3. Add the new submodule to the top section of the <dependencyManagement> of the top-level pom.xml. The version should be set to "${project.version}". This section is sorted alphabetically by artifact name so please preserve that ordering.
4. Add the new submodule to the modules section element of the top-level pom.xml
5. Add your submodule dependency to any AS modules that require it, but only with group/artifact.
6. Edit build/pom.xml and add the new submodule with only group/artifact.
7. Create a directory in build/src/modules corresponding to the submodule, with a version of "main", like this: "build/src/main/resources/modules/org/jboss/as/new-subsystem/main".
8. Create a module.xml file inside the "main" directory. Use a module.xml from another subsystem as a template.
9. Edit build/build.xml and add a <module-def> element for the subsystem. Use the module name and Maven coordinates from steps 6 and 2 respectively. Use another submodule as a template.
Please be sure to preserve the alphabetical ordering of all POMs and the build.xml file.
h4. Appendix C. Profiling with JProfiler
Performance tuning is an important part of AS7 development. In order to use JProfiler on a standalone AS 7 instance, first you need to add the following to your standalone.conf file:
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=com.jprofiler -agentlib:jprofilerti -Xbootclasspath/a:/path/to/jprofiler/bin/agent.jar"
The "jboss.modules.system.pkgs" property tells JBoss Modules to allow the "com.profiler" classes to be found from any class loader, which is essential to allow the JProfiler agent to run.
It's easiest to then just set up your JProfiler session as "Remote", and start the server and the profiler in any order. That's it!
h4. Tips & Tricks!
h4. Creating a Git status prompt in your terminal
This makes it easy to not forget what branch you are working in and quickly tell if you have changes. The following will adjust the PS1 on unix (or cygwin on Windows). Note that it assumes a compiled version of git, which is also the case for the OSX packages. If you are using the bundled rpm version, change the completion path to "/etc/bash_completion.d/git"
GIT_COMPLETION_PATH="/usr/local/git/contrib/completion/git-completion.bash"
if [ -f "$GIT_COMPLETION_PATH" ]; then
GIT_PS1_SHOWDIRTYSTATE=true
. "$GIT_COMPLETION_PATH"
ADD_PS1='$(__git_ps1)'
fi
if [[ ${EUID} == 0 ]] ; then
PS1="\[\033[01;31m\]\h\[\033[01;34m\] \w\[\033[33m\]$ADD_PS1\[\033[34m\] \$\[\033[00m\] "
else
PS1="\[\033[01;32m\]\u@\h\[\033[01;34m\] \w\[\033[33m\]$ADD_PS1\[\033[34m\] \$\[\033[00m\] "
fi
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15596]
Create a new document in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
15 years
[jBPM Development] - Integrating jBPM transactions with Application transactions
by Sampath Gunda
Sampath Gunda [http://community.jboss.org/people/sgunda] created the discussion
"Integrating jBPM transactions with Application transactions"
To view the discussion, visit: http://community.jboss.org/message/588705#588705
--------------------------------------------------------------
Hi Experts,
1. We have a web application using Hibernate and Spring.We are using plain JDBC trabsactions for transaction handling.
2. We are using jBPM4.4 success fully for wrokflows development. jBPM is having its own Data base and session factory.
3. Now jBPM services are getting executed in their own transactions not as part of our application transactions. We wanted to
integrate jBPM transactions to our application transactions. To do this, As per my knowledge we have two options:
a) Using Distributed Transactions Manager JTA. But, at this time,we can't go for this option due to some problems.
b) Merging jBPM DB tables into our application DB and using single session factory for both jBPM and our application.
How to implement this approcah?. How to instruct the jBPM to use this session factory instead of using its own?
Please provide your gudence in resolving this issue.
Thanks & Regards,
Sampath G
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588705#588705]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years
