October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1035) Integrate JSUnit with existing testing framework.

by Roy Russo (JIRA)

Integrate JSUnit with existing testing framework. ------------------------------------------------- Key: JBPORTAL-1035 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1035 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 -- 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, 3 months

1
1
0 / 0

WebHosting al mejor precio de Chile!!

by WebHosting Profesional.

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1072) Clustering configurations does not startup with mysql

by Rajesh Rajasekaran (JIRA)

Clustering configurations does not startup with mysql ----------------------------------------------------- Key: JBPORTAL-1072 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1072 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Clustering nodes ports-01 and ports-02 as explained in the reference guide http://docs.jboss.com/jbportal/v2.4/reference-guide/en/html/clustering.html does not startup with myql. The following errors are encountered with with mysql. 18:06:30,796 INFO [RenderKitFactoryImpl] RenderKit with renderKitId 'HTML_BASIC' was replaced. 18:06:30,796 INFO [MyFacesGenericPortlet] PortletContext 'C:\portal-release\jboss-4.0.4.GA\server\ports-01\.\deploy\jboss-portal-ha.sar\portal-core.war\' initialized. 18:06:30,937 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 01004 18:06:30,937 ERROR [JDBCExceptionReporter] Data truncation: Data too long for column 'MODIFIABLE' at row 1 18:06:30,937 ERROR [PortletAppDeployment] Error when creating instances org.hibernate.exception.GenericJDBCException: could not insert: [org.jboss.portal.core.impl.model.instance.InstanceImpl] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:40) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2044) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2481) at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:47) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:290) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:131) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:87) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38) at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:620) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:594) -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1070) Convert Dashboard navigation to portlet

by Roy Russo (JIRA)

Convert Dashboard navigation to portlet --------------------------------------- Key: JBPORTAL-1070 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1070 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-391) <end-conversation /> ends task

by Peter Muir (JIRA)

<end-conversation /> ends task ------------------------------ Key: JBSEAM-391 URL: http://jira.jboss.com/jira/browse/JBSEAM-391 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 1.0.1 Environment: Tested against 1.0.1 but looks unaltered in CVS Reporter: Peter Muir The reference manual says 'Optionally, we can specify a transition name. In this case, Seam will signal the end of the current task in the overarching business process.' (4.2.5) Whether or not you specify a transition on <end-conversation /> if a task instance is active then it will be ended. This is because in Page.java the execute method has if ( transition == null ) { task.end(); } else { task.end(transition); } How about adding endTask="true|false" (default true) to end-conversation and altering Page.java accordingly? This functionality would be useful if you want to 'cancel' out of a pageflow and returrn to the task at a later date. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-597) Tracker task for JBSHOTOKU-101 (blogs dont show up in our Labs project blog area)

by Ovidiu Feodorov (JIRA)

Tracker task for JBSHOTOKU-101 (blogs dont show up in our Labs project blog area) --------------------------------------------------------------------------------- Key: JBMESSAGING-597 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-597 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Trivial Fix For: 1.2.0.Alpha2 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1069) Allow for dynamic regions to read rendercontext

by Roy Russo (JIRA)

Allow for dynamic regions to read rendercontext ----------------------------------------------- Key: JBPORTAL-1069 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1069 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 Will allo dynamic regions to be request/ctx sensitive. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1068) Improve integration with Alfresco

by Alex Pinkin (JIRA)

Improve integration with Alfresco --------------------------------- Key: JBPORTAL-1068 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1068 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Reporter: Alex Pinkin Fix For: 3.0 Final - consider splitting off our CMS implementation into a separate project - work with Alfresco to design better integration (see http://issues.alfresco.com/browse/AWC-593) This may not need to be tied with a particular release of JBoss Portal. This is more of a PortletSwap thingy. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-12) Can't use . in username when using BaseCertLoginModule

by Anil Saldhana (JIRA)

Can't use . in username when using BaseCertLoginModule ------------------------------------------------------ Key: SECURITY-12 URL: http://jira.jboss.com/jira/browse/SECURITY-12 Project: JBoss Security Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 1.x Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 JBAS-3742 ======================================================================================== I have trying to use mod_jk + SSL + jboss and I have found that I can't have a '.' in the username. I am trying with the following user: +++ EMAILADDRESS=support(a)jboss.com, CN=support, OU=Jboss, O=Redhat, L=Neuchatel, ST=Neuchatel, C=CH +++ Find attached a patch thanks for committing it. (The patch is for jbossas-4.0.x). Cheers Jean-Frederic ================================================================== -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBTM-75) Update transactional JDBC driver to support JDBC 3 methods.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-75?page=comments#action_12344773 ] Mark Little commented on JBTM-75: --------------------------------- Yes, 4.2.2 is 1.4 only, so we should keep this for the 4.4 release as you say. > Update transactional JDBC driver to support JDBC 3 methods. > ----------------------------------------------------------- > > Key: JBTM-75 > URL: http://jira.jboss.com/jira/browse/JBTM-75 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.2 > Reporter: Mark Little > Assigned To: Jonathan Halliday > Priority: Minor > Fix For: 4.2.2 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > -- 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006