January 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2151) WYSIWYG not working in preview with files with no content.

by Viliam Rockai (JIRA)

WYSIWYG not working in preview with files with no content. ---------------------------------------------------------- Key: JBPORTAL-2151 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2151 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Environment: fedora 9, laptop t61, java version "1.5.0_16", firefox 3.0.1 Reporter: Viliam Rockai Assignee: Sohil Shah Priority: Minor after a creation of file with no content (nothing typed into WYSIWYG Editor) i can click on the "preview" button. it seems that clicking this button has different functionality when the file has content, or is blank. on a blank file "preview" gives us ONLY the list of files in directory (which i guess is not correct functionality) but if the file has any text written in it, the preview opens the "WYSIWYG Editor" where it is able to see the content of file and change it AND the list of files in directory . user who didn't fill the content of their files are now unable to do it with preview button. is it correct? step: login as admin click on the admin link click on cms tab select action -> create file choose any filename, description, title and language, but don't type anything into the WYSIWYG editor click "create" click on the "preview" link as a resultyou cannot see the WYSIWYG editor and you cannot add content this way. same steps with typing some content into the WYSIWYG ends with showing up the WYSIWYG editor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2266) CMS JBPM Workflow affected by the JBPM Value Serialization Bug

by Sohil Shah (JIRA)

CMS JBPM Workflow affected by the JBPM Value Serialization Bug -------------------------------------------------------------- Key: JBPORTAL-2266 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2266 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Sohil Shah Assignee: Sohil Shah Fix For: 2.7.1 Final When CMS Workflow is turned on, the public Collection<Content> getPendingQueue(String filePath) throws WorkflowException method of ApprovePublishImpl does not get a proper instance back from the JBPM Process. It gets a ByteArray back instead of the actual Object which in this case of type "Content". I checked and made sure the Object is Serializable Link to similar issue: https://jira.jboss.org/jira/browse/JBPM-1914 For some reason, this same piece of code unaltered works fine with the 2.7.0 Final that was shipped. So far, its a Ghost in the machine until I know more ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1452) Use OrderedExecutor on Paging

by Clebert Suconic (JIRA)

Use OrderedExecutor on Paging ----------------------------- Key: JBMESSAGING-1452 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1452 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: 2.0.0 Beta -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
2
0 / 0

[JBoss JIRA] Resolved: (JBAS-2953) cyclic dependency on ejb3 module

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2953?page=com.atlassian.jira.plug... ] Alessio Soldano resolved JBAS-2953. ----------------------------------- Resolution: Out of Date I assume this is out of date, if not reopen. > cyclic dependency on ejb3 module > -------------------------------- > > Key: JBAS-2953 > URL: https://jira.jboss.org/jira/browse/JBAS-2953 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Services > Reporter: Bill Burke > Assignee: Alessio Soldano > > there is now a cyclic dependency in ejb3 module as I need the @WebService annotation. can you break out the ws interfaces into a separate module like j2ee does and ejb3x does? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2953) cyclic dependency on ejb3 module

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2953?page=com.atlassian.jira.plug... ] Alessio Soldano reassigned JBAS-2953: ------------------------------------- Assignee: Alessio Soldano > cyclic dependency on ejb3 module > -------------------------------- > > Key: JBAS-2953 > URL: https://jira.jboss.org/jira/browse/JBAS-2953 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Services > Reporter: Bill Burke > Assignee: Alessio Soldano > > there is now a cyclic dependency in ejb3 module as I need the @WebService annotation. can you break out the ws interfaces into a separate module like j2ee does and ejb3x does? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6287) org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCase fails when run with JDK 6

by Shelly McGowan (JIRA)

org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCase fails when run with JDK 6 ------------------------------------------------------------------------------------- Key: JBAS-6287 URL: https://jira.jboss.org/jira/browse/JBAS-6287 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: JBossAS-5.0.1.CR1 This test case failure is the same as JBAS-5482. The workaround was added to org.jboss.test.JBossIIOPTestCase.java (JBTEST-5) but this test class extends org.jboss.test.JBossTestCase.java. public class HelloTimingStressTestCase extends JBossTestCase -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
2
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-375) Grouping of messages

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-375?page=com.atlassian.jir... ] Tim Fox reopened JBMESSAGING-375: --------------------------------- Re-opening since grouping of messages in a cluster is not implemented (see earlier comments) > Grouping of messages > -------------------- > > Key: JBMESSAGING-375 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assignee: Andy Taylor > Fix For: 2.0.0 Beta > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by a group id so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of group id. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2271) IAE when rendering a simple resource

by Chris Laprun (JIRA)

IAE when rendering a simple resource ------------------------------------ Key: JBPORTAL-2271 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2271 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.0 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.7.1 Final java.lang.IllegalArgumentException: Must pass a non null resource id at org.jboss.portal.common.util.ParameterValidation.throwIllegalArgExceptionIfNull(ParameterValidation.java:68) at org.jboss.portal.core.portlet.PortletRequestDecoder.decode(PortletRequestDecoder.java:189) at org.jboss.portal.core.model.portal.PortalObjectCommandFactory.doMapping(PortalObjectCommandFactory.java:89) at org.jboss.portal.core.controller.command.mapper.CommandFactoryDelegate.doMapping(CommandFactoryDelegate.java:87) at org.jboss.portal.core.controller.command.mapper.DelegatingCommandFactoryService.doMapping(DelegatingCommandFactoryService.java:142) at org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:69) at org.jboss.portal.core.controller.Controller.handle(Controller.java:252) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-35) Resource adapter deployer

by Jesper Pedersen (JIRA)

Resource adapter deployer ------------------------- Key: JBJCA-35 URL: https://jira.jboss.org/jira/browse/JBJCA-35 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0 Alpha1 We need a resource adapter deployer chain that can deploy .rar archives and JCA 1.6 annotated classes. The chain will look at * ra.xml * jboss-ra.xml * JCA 1.6 annotated classes Sub-tasks should be created for each deployment stage (org.jboss.deployers.spi.deployer.DeploymentStage). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1665) EJB bean classes are not getting woven by AOP

by Carlo de Wolf (JIRA)

EJB bean classes are not getting woven by AOP --------------------------------------------- Key: EJBTHREE-1665 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1665 Project: EJB 3.0 Issue Type: Bug Affects Versions: 1.0.0 Reporter: Carlo de Wolf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

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 January 2009