September 2007 - jboss-jira - Jboss List Archives

[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

16 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

16 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

16 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

16 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

16 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

16 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1109) Exported BRMS repositories lose version history

by Shahad Ahmed (JIRA)

Exported BRMS repositories lose version history ----------------------------------------------- Key: JBRULES-1109 URL: http://jira.jboss.com/jira/browse/JBRULES-1109 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.0.GA Environment: Windows XP SP2, SUN JRE 1.5_09 Reporter: Shahad Ahmed Assigned To: Mark Proctor I've come across an issue with exporting and importing a BRMS repository backup, which I'm not sure is a feature or a bug. I have a package that contains a bunch of rules I've developed. I've modified and saved rules, so that most of the rules have a fairly long history when you select the Version History in the rule view. If I export the repository in the Admin/Manage Backups section and then import the repository into a clean BRMS installation, all the version history of the rules seems to be lost. The rules still have the correct version attribute (e.g. version: 8 etc), but when you click on the View History link it just says No History. If you actually export and then re-import the rules into the same BRMS installation, then the History is maintained - however, I suspect that is purely by chance as the underlying repository is not being cleaned up by the import option? Here's how to replicate the problem for a clean BRMS install: 1. Create a new category called test. 2. In the defaultPackage create a new technical rule called test as shown below: when eval(true) then System.out.println("Hello"); 3. Save the test rule 4. Modify test rule e.g. by changing "Hello" to "Hello World" and Save the rule agin to get a version 2 of the rule. 5. Click on the View History option to verify that the rule has a single historical version 1 in the repository. 6. From Admin/Manage Backups save the repository. 7. In a new clean BRMS install import the previously exported repository (I guess if you do not want to reinstall the BRMS you can shutdown the original and remove the repository directory, the repository.xml and derby.log files, and then restart to get an empty repository). 8. Open the test rule created previously. It should show up with version 2. Click on the View History option and it says No History. The conclusion is that the back feaure does not back up the full repository i.e. history is lost. -- 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

16 years, 8 months

4
6
0 / 0

[JBoss JIRA] Resolved: (JBREM-129) remove oswego-concurrent lib

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-129?page=all ] Ron Sigal resolved JBREM-129. ----------------------------- Resolution: Won't Fix Assignee: (was: Tom Elrod) The premise of this issue, that oswego-concurrent jar is only being used by test code, is no longer true: org.jboss.remoting.Client uses org.jboss.util.id.GUID (from the common-core project) for its sessionId, and GUID uses org.jboss.util.id.UID, which uses an EDU.oswego.cs.dl.util.concurrent.SynchronizedLong. > remove oswego-concurrent lib > ---------------------------- > > Key: JBREM-129 > URL: http://jira.jboss.com/jira/browse/JBREM-129 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Optional > Fix For: 2.4.0.CR1 (Pinto) > > > The oswego-concurrent jar is only being used by test code. If change this code to not use concurrent then can remove jar from remoting project (and distribution). -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-433) point to multipoint invocation api

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-433?page=all ] Ron Sigal updated JBREM-433: ---------------------------- Fix Version/s: 3.0.0.Alpha1 (Otter) (was: 2.4.0.Beta1 (Pinto)) Affects Version/s: 2.2.2.GA (was: 2.0.0.Beta1) There's not point in working on this issue until Remoting 3.0. > point to multipoint invocation api > ---------------------------------- > > Key: JBREM-433 > URL: http://jira.jboss.com/jira/browse/JBREM-433 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.2.2.GA > Reporter: Tom Elrod > Assigned To: David Lloyd > Fix For: 3.0.0.Alpha1 (Otter) > > > Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time. The responses for each target server would be aggregated into one response as return to the client call. Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for this. -- 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

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