September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-426) enable jpdl schema extension via namespaces

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-426?page=all ] Tom Baeyens updated JBPM-426: ----------------------------- Fix Version/s: jBPM jPDL 3.2.2 (was: jBPM 3.3) > enable jpdl schema extension via namespaces > ------------------------------------------- > > Key: JBPM-426 > URL: http://jira.jboss.com/jira/browse/JBPM-426 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1, jBPM jPDL 3.2 > Reporter: Martin Dirichs > Assigned To: Ronald van Kuijk > Fix For: jBPM jPDL 3.2.2 > > > Customizing jpdl elements in a process definition via application-specific XML-elements is currently only possible outside of any schema validation. XML namespaces are the canonical way to allow for the extension of jpdl so that configuration data of delegation classes may be defined within an application-specific namespace and associated XML schema. In particular, this would be necessary to enable customization of jpdl elements > - action > - assignment > - handler > - controller > - task > Bug #JBPM-332: > http://jira.jboss.com/jira/browse/JBPM-332 > is somewhat related to this issue. However, resolution of JBPM-332 > - only allows for arbitrary elements to appear inside jpdl files (without schema validation) > - and only for customizing assignments (leaving out action, handler, controller and task). > Implementation of this feature request would be done via a more intelligent version of an EntityResolver (defined in org.jbpm.jpdl.xml.SchemaValidationHandle) that can return application specific schemas in addition to the default one for jpdl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-989) test suite fails when no ${custom.db.config} defined

by Aleksandar Kostadinov (JIRA)

test suite fails when no ${custom.db.config} defined ---------------------------------------------------- Key: JBPM-989 URL: http://jira.jboss.com/jira/browse/JBPM-989 Project: JBoss jBPM Issue Type: Bug Reporter: Aleksandar Kostadinov Assigned To: Tom Baeyens When test suite is run without specifying custom database config with the custom.db.config variable it fails with the error below. The test org.jbpm.taskmgmt.exe.TaskVariablesTest fails the build as it doesn't find the /home/hudson/static_build_env/jbpm/dbtests/driver/${custom.db.config} directory. http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmBuildingTheSources does say one need to set this variable only in case he's trying to test against a non-default database. ------ BUILD LOG --------- customize.db.config: test: [mkdir] Created dir: /qa/services/hudson/hudson_workspace/workspace/JBPM.3/jpdl/jar/target/test.results/xml [echo] tweaked tests non persistent tests [junit] Running org.jbpm.taskmgmt.exe.TaskVariablesTest BUILD FAILED /qa/services/hudson/hudson_workspace/workspace/JBPM.3/build/build.xml:42: The following error occurred while executing this line: /qa/services/hudson/hudson_workspace/workspace/JBPM.3/jpdl/jar/build.xml:143: /home/hudson/static_build_env/jbpm/dbtests/driver/${custom.db.config} not found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBPM-158) Add <description> back into jPDL

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-158?page=all ] Tom Baeyens updated JBPM-158: ----------------------------- Fix Version/s: jBPM jPDL 3.2.2 (was: jBPM 3.3) > Add <description> back into jPDL > -------------------------------- > > Key: JBPM-158 > URL: http://jira.jboss.com/jira/browse/JBPM-158 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: All > Reporter: Jim Rigsbee > Assigned To: Tom Baeyens > Priority: Minor > Fix For: jBPM jPDL 3.2.2 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > A description element was supported in 2.0. This does not exist in 3.0 so far. > We need to decide whether it should go in and to what extent. In 2.0 it was available on every major element. I would like to suggest that we support it only on the process-definition itself, as people can use <! xxx ---> style comments anywhere they choose. > Perhaps this needs to be coordinated with tasks surrounding features for versioning, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1311) Renaming a page should be possible in the dashboard and management portlet

by Thomas Heute (JIRA)

Renaming a page should be possible in the dashboard and management portlet -------------------------------------------------------------------------- Key: JBPORTAL-1311 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1311 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha2 Reporter: Thomas Heute Assigned To: Julien Viet Fix For: 2.6.CR1 A user should be able to rename a page of his dashboard. Admins should be able to rename pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1280) Move TinyMCE customization outside the webpage

by Thomas Heute (JIRA)

Move TinyMCE customization outside the webpage ---------------------------------------------- Key: JBPORTAL-1280 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1280 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Heute Fix For: 2.6 Final Ideally we would have TinyMCE configuration outside of the webpage (in the CMS admin portlet descriptor maybe ?). It would help: - customize it - test it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-978) <mail tag text attribute does not allow html content. Secondly no "CC" attribute in the mail tag

by Naseem Khan (JIRA)

<mail tag text attribute does not allow html content. Secondly no "CC" attribute in the mail tag ------------------------------------------------------------------------------------------------ Key: JBPM-978 URL: http://jira.jboss.com/jira/browse/JBPM-978 Project: JBoss jBPM Issue Type: Bug Components: BPEL Affects Versions: jBPM jPDL 3.2 Environment: Operating System: Windows 2000 professional Java 1.5, jboss server: jboss-4.0.4 JBPM runtime: jbpm-jpdl-3.2.GA Reporter: Naseem Khan Assigned To: Tom Baeyens In jbpm email support, html formatting is not working. <event type="node-leave"> <mail name="M_MailAction" actors="user(bert)" to="#{Mail}" template="jbpm.mail.templates.xml" subject="Approval Mail to Admin" text="Travel Approval Form:<b>EmployeeId:</b>#{EmployeeId}"/> </event> Now in the text attribute, html tag is not working. At the time of process deployment following exception occurred: org.jbpm.jpdl.JpdlException: [[FATAL] line 28: The value of attribute "text" associated with an element type "mail" must not contain the '<' character., [ERROR] couldn't parse process definition] org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:173) org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:51) org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81) org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(Unknown Source) org.jbpm.webapp.servlet.ProcessUploadServlet.doDeployArchive(Unknown Source) org.jbpm.webapp.servlet.ProcessUploadServlet.handleRequest(Unknown Source) org.jbpm.webapp.servlet.ProcessUploadServlet.service(Unknown Source) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) Secondly there is no cc attribute in the mail tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-793) refresh the bare bones tutorial

by Tom Baeyens (JIRA)

refresh the bare bones tutorial ------------------------------- Key: JBPM-793 URL: http://jira.jboss.com/jira/browse/JBPM-793 Project: JBoss jBPM Issue Type: Feature Request Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 Here's a good example of how it should look like: http://www.springframework.org/docs/MVC-step-by-step/Spring-MVC-step-by-s... No graphical designer, start from the bare jbpm download, jdk 1.4.2 and ant. Work out a minimal example. The main target audience is developers that want to see what jbpm does and how it works. Tooling should be excluded to prevent unnecessary noise for this use case. The getting started that is currently on the wiki will be kept in coexistence. That shows jbpm step by step WITH the tooling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1160) Update DSL docs to include new features

by Michael Neale (JIRA)

Update DSL docs to include new features --------------------------------------- Key: JBRULES-1160 URL: http://jira.jboss.com/jira/browse/JBRULES-1160 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0.1 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1162) Minor corrections in IDE documentation

by Michael Neale (JIRA)

Minor corrections in IDE documentation -------------------------------------- Key: JBRULES-1162 URL: http://jira.jboss.com/jira/browse/JBRULES-1162 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0.1 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1161) Export/import to include version history (optionally)

by Michael Neale (JIRA)

Export/import to include version history (optionally) ----------------------------------------------------- Key: JBRULES-1161 URL: http://jira.jboss.com/jira/browse/JBRULES-1161 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Michael Neale Assigned To: Michael Neale Priority: Minor Fix For: FUTURE Not really sure how to do this. JCR2.0 spec may help somewhat. this would involve restoring multiple workspaces (I am guessing) after the main one is restored (so all the verison history is there). NOt sure how to do this in a general way. The main use case for this is migrating between say jackrabbit, and alfresco. Backup and restore is another. Another option is that there is a backup/restore tool being developed for jackrabbit (was part of a google summer of code) so maybe that can be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 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-jira September 2007