May 2010 - jboss-user - Jboss List Archives

Re: [jboss-user] [Spring Integration] - JBoss 5.1.0 and Multiple EARs and EJBs using the SpringBeanAutowiringInterceptor issue

by Marius Bogoevici

Marius Bogoevici [http://community.jboss.org/people/marius.bogoevici] replied to the discussion "JBoss 5.1.0 and Multiple EARs and EJBs using the SpringBeanAutowiringInterceptor issue" To view the discussion, visit: http://community.jboss.org/message/544955#544955 -------------------------------------------------------------- Looks odd. Are you sure that the deployments include the beanRefContext.xml file only once (also considering JARs)? What really happens there is that the application context for EJB2 is constructed with both XMLs so I am wondering if both of them are included in the EAR. Can you try to deploy only EJB2 and invoke it remotely (without EAR1 being present) and see what happens? If you're still seeing issues then EAR2 might be at fault. Also, how do you deploy Spring - shared lib or included with each EAR? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544955#544955] Start a new discussion in Spring Integration at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

[JBoss Messaging Development] - why JMS server connection can not recover when the socket, which JMS server uses to delivery messages to client, is broken

by yong deng

yong deng [http://community.jboss.org/people/dengyong] created the discussion "why JMS server connection can not recover when the socket, which JMS server uses to delivery messages to client, is broken" To view the discussion, visit: http://community.jboss.org/message/544953#544953 -------------------------------------------------------------- My environment: JBoss messaging 1.4.0.SP3-CP05 + JBoss remoting 2.2.2.SP10 My case is like below: I have a JMS client which will subscribe messages from a JMS topic. On the JMS connection, I set an ExceptionListener so that I can detect the connection broken. I did following testing and found some situation JMS connection exception listener can not dectect connection broken. By default, JMS bisocket will listen on port 4457. For every JMS connection, I can find two TCP connection connecting to the port 4457. Besides that, I can find the other two TCP connection which I guess server will use to delivery messages to the clients. 1. when I [only] close TCP connection connecting to the port 4457 use some tools, indeed the ExceptionListener can detect the broken connection 2. but when I [only] close the other two TCP connection, I find: 1) JMS server will log an exception on ServerInvokerCallbackHandler. After that, it seems will never recover to delivery messages to the clients agains. On the same handle, the session will still be live in server side, I find this from MBean [jboss.messaging:service=ServerPeer showActiveClientsAsHTML] from JMX console. 2) JMS client then can never get message from server side again and also the JMS ExceptionListener on connection can never detect connection failure Now my questions here is: 1. for my case 2, should not the JMS server try to recovery from broken sockets to delivery messages to the JMS client again? 2. for my case 2, if expected behavior can not be implemented, at least JMS connection ExceptionListener should be able to detect failure and reconnect? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544953#544953] Start a new discussion in JBoss Messaging Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

[Spring Integration] - JBoss 5.1.0 and Multiple EARs

by Kyle Bober

Kyle Bober [http://community.jboss.org/people/kyle.bober] created the discussion "JBoss 5.1.0 and Multiple EARs" To view the discussion, visit: http://community.jboss.org/message/544949#544949 -------------------------------------------------------------- I have two EARs that contain unique WAR and EJB JAR files. Each EAR contains a beanRefContext.xml file that I have wired up to multiple applicationContext files to use Autowiring in my EJB implementation classes. My EARs are configured to be isolated in the JBoss EAR deployer. Each of my EJBs is configured to use the @Interceptors(SpringBeanAutowiringInterceptor.class) EAR 1 --- WAR1 --- EJB1 JAR EAR 2 --- WAR2 --- EJB2 JAR My issues is when I deploy both of these EARs in the same JBoss instance and attempt to have EJB1 call EJB2 via a remote EJB call I receive the following exception: {code}Caused by: java.lang.RuntimeException: org.springframework.beans.factory.access.BootstrapException: Unable to return specified BeanFactory instance: factory key [null], from group with resource name [classpath*:beanRefContext.xml]; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [org.springframework.beans.factory.BeanFactory] is defined: expected single bean but found 2{code} This exception is thrown from EJB1 when it attemps to make a remote ejb call to EJB2. To verify that this is an issue with Spring Integration I removed the @Interceptors(SpringBeanAutowiringInterceptor.class) from EJB2 and returned some dummy data and it worked fine. It seems this issue revolves around the SpringBeanAutowiringInterceptor.class. Any help here resolving this issue would be much appreciated! Here are the beanRefContext.xml files which are include in the root of the EAR files. EAR1 <?xml version="1.0" encoding="UTF-8"?> <beans xmlns=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance" xmlns:jee=" http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee" xmlns:aop=" http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop" xmlns:tx=" http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd http://www.springframework.org/schema/tx/spring-tx-2.5.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd http://www.springframework.org/schema/aop/spring-aop-2.5.xsd"> <bean id="ear1-context" class="org.springframework.context.support.ClassPathXmlApplicationContext"> <constructor-arg> <list> <value>ejb1-applicationContext.xml</value> <value>dao1-applicationContext.xml</value> </list> </constructor-arg> </bean> </beans> EAR2 <?xml version="1.0" encoding="UTF-8"?> <beans xmlns=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance" xmlns:jee=" http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee" xmlns:aop=" http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop" xmlns:tx=" http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd http://www.springframework.org/schema/tx/spring-tx-2.5.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd http://www.springframework.org/schema/aop/spring-aop-2.5.xsd"> <bean id="ear2-context"> <constructor-arg> <list> <value>ejb2-applicationContext.xml</value> <value>dao2-applicationContext.xml</value> </list> </constructor-arg> </bean> </beans> -Kyle -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544949#544949] Start a new discussion in Spring Integration at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

[JBoss Tools] - How to Write Documentation for JBDS and JBoss Tools

by OLga Chikvina

OLga Chikvina [http://community.jboss.org/people/Ochikvina] modified the document: "How to Write Documentation for JBDS and JBoss Tools" To view the document, visit: http://community.jboss.org/docs/DOC-14250 -------------------------------------------------------------- ** #Places_of_main_doc_team_resources Places of main doc team resources ** #Documentation_building_procedure Documentation building procedure ** #Doc_JIRA Doc JIRA ** #JBoss_ToolsJBDS_Demos JBoss Tools/JBDS Demos ** #JBoss_ToolsJBDS_guides_structure JBoss Tools/JBDS guides structure ** #Project_structure_schema Project structure schema ** #Inline_graphics_scale__100 Inline graphics scale - 100% ** #Doc_build_process_speed_up Doc build process speed up ** #Task_reviewing Task reviewing ** #Text_validation Text validation ** #JBDS_team_movies_update JBDS team movies update ** #JBDS_Inline_graphics JBDS Inline graphics ** #Task_resolving_before_a_release Task resolving before a release ** #JIRA_issues JIRA issues ** #Para_and_programlisting Para and programlisting ** #Image_canvas_size Image canvas size ** #Docs_releasing_procedure Docs releasing procedure ** #Using_diffmk_to_add_updatedadded_markers_to_TOC Using diffmk to add updated/added markers to TOC ** #Nightly_docs Nightly docs h2. *Places of main doc team resources* Here is the list resources related to JBDS/Tools docs: 1. SVN - https://svn.jboss.org/repos/jbosstools/trunk https://svn.jboss.org/repos/jbosstools/trunk * doc folder with guide/guides is placed in plugin folder e.g. https://svn.jboss.org/repos/jbosstools/trunk/esb/docs https://svn.jboss.org/repos/jbosstools/trunk/esb/docs * https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies - folder with movies on Tools and JBDS * https://svn.jboss.org/repos/jbosstools/trunk/documentation https://svn.jboss.org/repos/jbosstools/trunk/documentation - folder with doc resources and several guides. — guides folder contains guides — jbds-docs folder is the place to generate JBDS release docs -jbosstool-docbook-xslt - xslt styles -jboss-tools-docs folder is the place to generate JBDS release docs -jboss-tools-docs-architype - architype for new guides creation -jbosstool-jdocbook-style -css styles — qa folder with qa resources (qa owns it) — whatsnew folder with what's new pages (dev team own it) 2. Doc project page contains links to release docs, nightly docs, movies — http://jboss.org/tools/docs.html http://jboss.org/tools/docs.html * NEWS - owned by dev team * reference guides - release guides updated by us * screen casts - movies we have made * FAQ - owned by dev team 3. Doc JIRA for both tools and jbds doc projects is on jbds project JIRA — https://jira.jboss.org/jira/browse/JBDS https://jira.jboss.org/jira/browse/JBDS * open components tab - here is a list of components, doc component are ones with Doc- prefix. h2. *Documentation building procedure* Here is an article on documentation building procedure http://jboss.org/community/wiki/BuildingJBossToolsDocumentaion http://jboss.org/community/wiki/BuildingJBossToolsDocumentaion Read it and try to build the docs with different profiles from here https://svn.jboss.org/repos/jbosstools/trunk/documentation https://svn.jboss.org/repos/jbosstools/trunk/documentation h2. *Doc JIRA* Here is JBDS JIRA - https://jira.jboss.org/jira/browse/jbds https://jira.jboss.org/jira/browse/jbds On the Open Issues tab you can see the components, the docs ones have Doc- prefix. Usually when a new guide is created I asked Max to add a component for it, as it's very convenient to use guides names as components. New doc JIRA issue usually is created basing on developers' taks, to find the tasks that affects docs use filter with "affects documentation" check-box marked. Most of the issues that affects docs can be found in JBoss Tools JIRA - https://jira.jboss.org/jira/browse/JBIDE https://jira.jboss.org/jira/browse/JBIDE. When a doc task is created basing on a dev task, the tasks are linked to each other with "is related to" link. h2. *JBoss Tools/JBDS Demos* * When making a demo, in its setting choose the necessary *jboss preloaders* and our standard palette and save the movie with this settings, before committing it to svn. * When making a demo, first of all *set 0,20 sec.* for all frames and then adjust the time you need for some particular frames. * When it’s necessary to draw *user attention* to some particular element on a frame, use red ellipse (for small elements – tabs, buttons, etc.) or rectangle (for file lists, windows, etc.) * When a demo is done, watch it yourself and make sure that you have *enough time to read* text in hints. * When making a demo, make sure that you chose the *appropriate size for hint boxes*: not lot’s of empty space should be under the text and the box should look like all other ones, undamaged, ‘cause when you try to minimize it, it could change its form unproportionally, try to avoid such an effect, minimize the box till its form (not size) remains the same. * When making movie, make sure your *Wink uses* the elements from here, copy it to you wink folders. https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies/common_... * When creating a new movie please *use the style features* located here - https://svn.jboss.org/repos/jbosstools/documentation/trunk/movies/common_... * When creating demos make sure that you use correct *jboss.org styles*, time capture rate is more or equal 4, and the cursor is moving smoothly on the screen * When making a demo, make sure that all application forms, hints, windows are *not cut* with demo frame. e.g. the hint is cut http://community.jboss.org/servlet/JiveServlet/showImage/102-14255-3-1596... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-14255-3-... h2. *JBoss Tools/JBDS guides structure* While creating a new or updating already existed JBoss Tools/JBDS guide, please keep to the following structure (JBoss Portlet Tools User Guide structure as an example): 1. Introduction 1.1. What is JBoss Portal and Portlet Tools? 1.2. Key Features of JBoss Portlet Tools 1.3. Requirements and Installation 2. JBoss Portlet Tools Tasks 2.1. Creating and Deploying a Java Portlet 2.1.1. Creating a Web Project with JBoss Portlet Capabilities 2.1.2. Adding a Java Portlet to a Web Project 2.1.3. Deploying a Portlet to JBoss Portal 2.2. Creating and Deploying a JSF Portlet 2.2.1. Creating a JSF Project with JSF Portlet Capabilities 2.2.2. Adding a JSF Protlet to the Project and Deploying It to JBoss Portal 2.3. Creating and Deploying a Seam Portlet 2.3.1. Creating a Seam Project with Seam Portlet Capabilities 2.3.2. Adding a Seam Protlet to the Project and Deploying It to JBoss Portal 3. Reference 3.1. JBoss Portlet Descriptors 3.2. Wizards 3.2.1. Java Portlet Wizard 3.2.2. JSF/Seam Portlet Wizard 3.3. JBoss Portlet Preferences 4. Summary 4.1. Other Relevant Resources on the Topic * * *Comments:* * The "Key Features of [plugin name]" section should contain the table included key features (wizards, editors, tasks, etc.) of the plugin you're describing with short descriptions and references to the appropriate guide section. * The "Requirements and Installation" section should provide minimal requirements on the environment the plugin needs and installation procedure (or reference to it). * All procedural operations must be put into the "[plugin name] Tasks" chapter. Each section of the chapter is a tutorial on a particular topic. * The referential data should be stored in the "Reference" chapter. * Remember to summarize the results and provide the links to other relevent resources in the "Summary" chapter. h2. *Project structure schema* In case you need to show some project structure in the documentation you should use the "tree" utility that builds in terminal the project structure that you can copy/paste to your docs. Quite likely that the "tree" utility is not installed on your local machine, the sudo apt-get install tree command will install this utility. You need to create the project structure schema in Linux since the tree command in Windows draws a tree that is not as nice as the one in Linux, besides Linux is our primary OS. However if you still need to draw a tree in Windows please use the tree /a /f command. This is what the project structure should be like. |-- pom.xml `-- src |-- main | |-- java | | `-- org | | `-- docs | | `-- richfaces | | `-- Bean.java | |-- resources | `-- webapp | |-- WEB-INF | | |-- faces-config.xml | | `-- web.xml | |-- index.jsp | `-- pages | |-- index.jsp | `-- index.xhtml `-- test `-- java `-- org `-- docs `-- richfaces `-- BeanTest.java h2. *Inline graphics scale - 100%* When inserting an inline graphics element please leave it unscaled. If you scale a tiny inline element, the image will be broken and hardly readable. h2. *Doc build process speed up* Command line option for only creating part of the outputs to speed up roundtrip. See the issue for details https://jira.jboss.org/jira/browse/MPJDOCBOOK-7 https://jira.jboss.org/jira/browse/MPJDOCBOOK-7 h2. *Task reviewing* When writing some article or component description or complicated section/chapter and need some review of it, let me know plz, and I’ll try to find a reviewer for your task. h2. *Text validation* E.g. letter “p” inside two opening tags (<section>p <title>… ) makes the document invalid and failes the build on this place. Do not forget to validate xmls each time you make changes. h2. **JBDS team movies update** When updating the guides according to some dev issue, remember about our movies collection, it also should be updated. h2. *JBDS Inline graphics* Documenting UI, from time to time you talk about icons, mouse arrows that change depending on the user behavior etc. In these cases you can insert an image of the element into the documentation right into the text. DocBook allows you to embed inline graphics using: <inlinemediaobject> <imageobject> <imagedata fileref="images/image1.png"/> </imageobject> </inlinemediaobject> h2. *Task resolving before a release* https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... When you’re resolving a task, make sure that the person who will be closing the task, has enough time for its verification. E.g. if you resolve the task in a release day it means that QA or a person who needs to verify the task, has no time for it, and also you won’t have time to fix the task if it’s reopened. h2. *JIRA issues* *JIRA issues format.* All your tasks in JIRA should have versions and components defined. *JIRA issues resolution.* When closing an issue, plz write some resolution as the last comment about what exactly was done. *"Fix version" of a jira issue.* When closing or resolving a jira issue, make sure “fix version” is the correct one, it must correspond to the next release version, which could be found on project jira page on Version tab. h2. *Para and programlisting* Don’t insert programlisting into para tags, it causes damaged code on a page. h2. *Image canvas size* When print-screening an image, please make sure that canvas size (uninformative white space around) of it is not to large, if yes, trim it. h2. *Docs* releasing procedure The first step you have to do is to generate new master_output.xml files for all the guides that are included to the bundle. h2. *Using diffmk to add updated/added markers to TOC* This procedure is required because it is necessary to compare documentation of the previous release version with the current one and add update/added marker to TOC, we use DiffMk version 3.0.a1. tool. We added two script files in the bin folder of the DiffMk distribution: * run.sh * run_mkdiff.sh. The first is responsible for comparing 2 files and producing a third file with *diff* markers. The second one we use to indicate the files to compare and the output files, the format is the following: ./run.sh [+the path to the file+] [+the path to the file modified+] [+the path to the output file+] To identify the changes between two different revisions of the same guide, use the following line: ./run.sh /path/to/the/old/revision/guide/master.xml /path/to/the/current/revision/guide/master.xml /path/to/the/produced/by/diffmk/master_output.xml Next, run the run_mkdiff.sh Actually, the DiffMk is not an ideal tool for comparing. It has a lot of lacks. Here are some of such lacks we run into: * It removes the HTML entities when outputs the file, for instance & in the links; * Sometimes it mixes the structure of the document, for instance, put the <chapter> into the <chapter>; * Sometimes it deletes the tags such as <imageobject>. Thus, in order the docs with diff markers could be built, the next step is validating and checking the master_output.xml files carefully. The next step you have to do is to build documentation bundle with updated/new markers on the TOC and required styles. Here we have to admit that doc bundels for JBDS and JBT releases differ.JBDS documentation has "com"(red styles), JBT docs are built in blue ones.If you need JBDS doc release bundle,please, use "releaseJBDS" profile,othervise "release" profile meets your needs. You can build release guides one by one using mvn clean install -P releaseJBDS or mvn clean install -P release maven command and then collect all the docs together. But the least time-consuming method is to build the whole bundle from jbosstools_trunk\documentation\jboss-tools-docs directory using mvn assembly:assembly -P releaseJBDS or mvn assembly:assembly -P release maven command.It will build all the guides and collect them in en/ folder. In the end the created release bundle should be uploaded to the site. JBDS release documentation should be placed here:http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/ JBT release documentation should be here: http://docs.jboss.org/tools/. h2. *Nightly docs* Nightly docs online: http://download.jboss.org/jbosstools/nightly-docs/ http://download.jboss.org/jbosstools/nightly-docs/ Here is svn for it: https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs Here is Hudson for it: http://hudson.qa.jboss.com/hudson/job/jbosstools-docs-nightly/ http://hudson.qa.jboss.com/hudson/job/jbosstools-docs-nightly/ (to build nightly docs VPN access and admin pass are required) When a new guide is created it should be added to nightly docs build * add it to pom.xml: https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... * add it to all-guides.xml: https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... * add it to the index.html (master.xml) page: https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-do... See that the guide is added and email Denis Golovin asking to add a new guide to the server settings for nightly docs. Build the guides with mvn clean install from https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs https://svn.jboss.org/repos/jbosstools/trunk/documentation/jboss-tools-docs http://community.jboss.org/docs/DOC-14252 Places of main Docteam resources -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-14250] Create a new document in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

14 years, 7 months

1
0
0 / 0

[Beginner's Corner] - jBoss folders in classpath?

by Bruno Melloni

Bruno Melloni [http://community.jboss.org/people/bmelloni] created the discussion "jBoss folders in classpath?" To view the discussion, visit: http://community.jboss.org/message/544943#544943 -------------------------------------------------------------- What are the jBoss' folders that are exposed to apps in the classpath? I thought that server/<enviroment>/conf and server/<enviroment>/lib were among them, but the application is having trouble reading the file when I use specificy it as being at "classpath:<filename>.xml". I am not a jBoss beginner, but this was clearly a beginner question... so I placed it in this forum :) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544943#544943] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

[jBPM Development] - SubProcess signaling issue

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] created the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/544940#544940 -------------------------------------------------------------- Hi guys, I have created jira issue that relates to potential problem/misuse of sub processes. Please have a look at it and let me know your opinion. https://jira.jboss.org/browse/JBPM-2874 https://jira.jboss.org/browse/JBPM-2874 Thanks -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544940#544940] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - start a process within another process in jbpm 4.3

by Al Nadein

Al Nadein [http://community.jboss.org/people/matrixpooh] replied to the discussion "start a process within another process in jbpm 4.3" To view the discussion, visit: http://community.jboss.org/message/544938#544938 -------------------------------------------------------------- org.hibernate.exception.ConstraintViolationException: could not insert: [org.jbpm.pvm.internal.model.ExecutionImpl] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2285) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2678) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:79) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:167) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1028) at org.jbpm.pvm.internal.tx.HibernateSessionResource.prepare(HibernateSessionResource.java:56) at org.jbpm.pvm.internal.tx.StandardTransaction.commit(StandardTransaction.java:107) at org.jbpm.pvm.internal.tx.StandardTransaction.complete(StandardTransaction.java:64) at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:61) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:56) at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43) at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceByKey(ExecutionServiceImpl.java:66) at com.gs.crd.requestmanager.workflow.test.OpenProcessWithinProcessTest.testDefault(OpenProcessWithinProcessTest.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 3;REQUESTMANAGER_WF_DEV.JBPM4_EXECUTION at com.ibm.db2.jcc.b.hh.b(hh.java:1369) at com.ibm.db2.jcc.b.hh.c(hh.java:1356) at com.ibm.db2.jcc.c.db.k(db.java:352) at com.ibm.db2.jcc.c.db.a(db.java:60) at com.ibm.db2.jcc.c.t.a(t.java:52) at com.ibm.db2.jcc.c.tb.b(tb.java:202) at com.ibm.db2.jcc.b.ih.ab(ih.java:1898) at com.ibm.db2.jcc.b.ih.d(ih.java:2467) at com.ibm.db2.jcc.b.ih.W(ih.java:525) at com.ibm.db2.jcc.b.ih.executeUpdate(ih.java:508) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:46) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2265) ... 42 more -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544938#544938] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - Subprocess wait state signal handling not working from parent process (jBPM 4.3)

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "Subprocess wait state signal handling not working from parent process (jBPM 4.3)" To view the discussion, visit: http://community.jboss.org/message/544933#544933 -------------------------------------------------------------- Hi, In general, you need to signal sub process execution using its id instead of signaling main process. Unfortunately there is no API way to get hold of sub process instance but you can do this casting to ExecutionImpl: ((ExecutionImpl)processInstance).getSubProcessInstance() Then use this process instance when signaling. You can find working example in attachment. BTW, next time please attach your complete process definition with all custom classes (for custom activity, event listeners, etc) and a test case. Will make it easier and faster for others to look into your case. P.S. Will create issue in jira to provide a way to get hold of sub process instance. HTH Maciej -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544933#544933] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

[JBoss Web Services] - how to update the MessageContext

by suresh inala

suresh inala [http://community.jboss.org/people/inalasuresh] created the discussion "how to update the MessageContext" To view the discussion, visit: http://community.jboss.org/message/544930#544930 -------------------------------------------------------------- Hi Everyone, while sending the request from the consumer with the client-handlers i want to update the messagecontext. for that the below code which i am working on. when iam doing this i am getting the null response. i am getting the soap response from the bytes but those byte are not setting into the StreamSource public boolean handleMessage (MessageContext msgContext) { SOAPMessageContext smc = (SOAPMessageContext) msgContext; SOAPMessage msg = smc.getMessage(); SOAPPart sp = msg.getSOAPPart(); StreamSource source = new StreamSource(new ByteArrayInputStream(getMessageBytes())); sp.setContent(source); return false; } protected byte[] getMessageBytes (MessageContext msgContext) { byte[] result = null; try { ByteArrayOutputStream bos = new ByteArrayOutputStream(); ((SOAPMessageContext)msgContext).getMessage().writeTo(bos); result = bos.toByteArray(); bos.close(); log.trace("setting byte message (length="+result.length+")"); } catch (Exception e) { throw new WebServiceException("Error extracting SOAP request message as bytes", e); } return result; } can any one plese help me out how can i set the bytes into MessageContext/StreamSource Thanks & Regards Suresh -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544930#544930] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 months

1
0
0 / 0

Re: [jboss-user] [JBoss Web Services Development] - JBWS-2210 : CXF Username Token JAAS integration

by Sergey Beryozkin

Sergey Beryozkin [http://community.jboss.org/people/sergeyb] replied to the discussion "JBWS-2210 : CXF Username Token JAAS integration" To view the discussion, visit: http://community.jboss.org/message/544920#544920 -------------------------------------------------------------- I gave it an initial try with trying to move the legacy JNDI code to PicketBox api, given that it is likely I'll need to work with PicketLink too (which sits on top of PocketBox as far as I understand), so the question is how to specify the configuration file : https://community.jboss.org/thread/152423 https://community.jboss.org/thread/152423 thanks, Sergey -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544920#544920] Start a new discussion in JBoss Web Services Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 7 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-user May 2010