October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1078) CMSPortlet default content update

by Roy Russo (JIRA)

CMSPortlet default content update --------------------------------- Key: JBPORTAL-1078 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1078 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS 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

19 years, 7 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-832) CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-832?page=comments#action_12345152 ] Roy Russo commented on JBPORTAL-832: ------------------------------------ Will add an encoding type when saving files. > CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged > -------------------------------------------------------------------------------------------------------------------- > > Key: JBPORTAL-832 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-832 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal CMS > Environment: jboss4.0.3sp1 > Reporter: Mike Khlu > Assigned To: Roy Russo > Attachments: ??????? ? ???-??? ???????.PNG, issue-screenshot.GIF, jbossportali18nbug.GIF, russian-in-1251.txt, russian-in-utf8.html > > > When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged. > I think that I have to encode the request in UTF-8 ??? > --------------------------------------------- > create file.html in Ru (in cms admin) with this text > abc??? > then look at the last record of JBP_CMS_VERSION_BINVAL > (six bytes in BINVAL_DATA field): > 61 62 63 e0 e1 e2 > it is cp1251 encoding !!!! > why this text non unicoded ??? > then when i retrive it i have - 'abc???' > I think that problem isn't in ContentTypeInterceptor because it succefully > sets UTF8, because localized resources seems right (in russian). > may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ??? > ----------------------------------------------------------- > but when I upload file on UTF-8 with russian characters - all correct. > I think that cms saves the content in one byte encoding (cp1250 or same). -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1012) Integrate drag&drop with the back-end (persistence of the window position)

by Alex Pinkin (JIRA)

Integrate drag&drop with the back-end (persistence of the window position) -------------------------------------------------------------------------- Key: JBPORTAL-1012 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1012 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alex Pinkin Fix For: 2.6.Alpha1 Saving/loading window position to/from the database. -- 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

19 years, 7 months

2
1
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-730) "Copy" should copy the live revision

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-730?page=all ] Roy Russo reassigned JBPORTAL-730: ---------------------------------- Assignee: Sohil Shah (was: Roy Russo) > "Copy" should copy the live revision > ------------------------------------ > > Key: JBPORTAL-730 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-730 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.2 Branch > Reporter: Thomas Heute > Assigned To: Sohil Shah > Fix For: 2.6.Alpha1 > > > The current "copy" feature using Jackrabbit Workspace.copy() seems to copy the latest revision and only that one. > Jackrabbit implementation won't help here (since it should be faster to do it at this level) > If we decide to copy a unique revision we should copy the Live version. (can be different from the latest) > Now the question is: should we copy all revisions or only the live one ? -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-560) CLONE -Referencing JAR file in persistence.xml - Still a bug and referenced duplicate issue does not exist

by Gregory Nolle (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-560?page=comments#action_12345147 ] Gregory Nolle commented on EJBTHREE-560: ---------------------------------------- Is this going to be fixed? There's a comment saying that it's a duplicate bug, which is true, but the original bug was never fixed despite it being marked as resolved! I submitted a patch to fix the issue 2 months ago and it has yet to show up in any release. Any timeframe on when this is going to be sorted out? > CLONE -Referencing JAR file in persistence.xml - Still a bug and referenced duplicate issue does not exist > ---------------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-560 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-560 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC1 > Reporter: geoffm74 > Attachments: PersistenceUnitDeployment.diff > > > I've installed EJB3.0RC1 and the release notes states that now all persistence.xml features are implemented. So I went on trying to use the jar file referencing. > Unfortunately I found that during deployment the only place being searched for this jar file was in JBOSS_HOME/bin. I tried with absolute paths and relative - but it kept hangin on to the bin folder - probably the working folder for jboss launcher. > My jar is bundled with my ear - where should it really be to get the jar reference workin? I think the bin folder is not a proper place.... > Peter -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-406) debug.seam causes exception

by jarkko Lietolahti (JIRA)

debug.seam causes exception --------------------------- Key: JBSEAM-406 URL: http://jira.jboss.com/jira/browse/JBSEAM-406 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.1 Environment: jboss 4.0.5CR1 with Seam CVS and RC9 of EJB3 Reporter: jarkko Lietolahti Accessing http://localhost:8080/seamApp/debug.seam causes the following exception in log (and 404 on the brorwser). 150438 16:57:07,871 ERROR [PhaseListenerManager] Exception in PhaseListener RENDER_RESPONSE(6) beforePhase. javax.faces.el.PropertyNotFoundException: /file:/home/jarkko/seam-workspace/tear/src/tc3.ear/tc3Web.war/WEB-INF/lib/jboss-seam-debug.jar!/META-INF/debug.xhtml @63,90 rendered="#{empty org$jboss$seam$debug$contexts.conversationEntries}": Bean: org.jboss.seam.debug.Contexts$$EnhancerByCGLIB$$fb7d5aec, property: conversationEntries at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:58) at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1076) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:231) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239) at org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:50) at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:33) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:153) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:619) -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3758) Keeping min-pool-size always connected regardless of idle-timeout-minutes

by Galder Zamarreno (JIRA)

Keeping min-pool-size always connected regardless of idle-timeout-minutes ------------------------------------------------------------------------- Key: JBAS-3758 URL: http://jira.jboss.com/jira/browse/JBAS-3758 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.4.GA Reporter: Galder Zamarreno Assigned To: Weston Price Priority: Minor Customer would like to have the min-pool-size number of connections always connected, not being disconnected after the idle-timeout-minutes. Idle connections between max-pool-size and min-pool-size would be closed as per idle-timeout-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

19 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-403) Test Seam 1.1 against the JSF 1.2 RI

by Gavin King (JIRA)

Test Seam 1.1 against the JSF 1.2 RI ------------------------------------ Key: JBSEAM-403 URL: http://jira.jboss.com/jira/browse/JBSEAM-403 Project: JBoss Seam Issue Type: Task Components: JSF Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.1 -- 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

19 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-740) Document c3po configuration more explicitly

by Ryan Campbell (JIRA)

Document c3po configuration more explicitly -------------------------------------------- Key: JBPM-740 URL: http://jira.jboss.com/jira/browse/JBPM-740 Project: JBoss jBPM Issue Type: Task Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.1.3 Please document how to configure C3PO with jBPM outside of an application server. -- 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

19 years, 7 months

3
2
0 / 0

Oportunidad de inversión, Departamentos 1 y 2 dormitorios, Inmobiliaria Senexco

by Senexco

19 years, 7 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 October 2006