May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (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 Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-832?page=all ] Sohil Shah resolved JBPORTAL-832. --------------------------------- Fix Version/s: 2.6 Final Resolution: Done > 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: Sohil Shah > Fix For: 2.6 Final > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1399) Make CMS workflow optional via configuration

by Thomas Heute (JIRA)

Make CMS workflow optional via configuration -------------------------------------------- Key: JBPORTAL-1399 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1399 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Thomas Heute Assigned To: Sohil Shah Fix For: 2.8 Final -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4408) LIMIT/OFFSET support in StoreManager2

by Jesper Pedersen (JIRA)

LIMIT/OFFSET support in StoreManager2 ------------------------------------- Key: JBAS-4408 URL: http://jira.jboss.com/jira/browse/JBAS-4408 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.2.0.CR2 Environment: Branch_4_2 and JDK5 Reporter: Jesper Pedersen Assigned To: Alexey Loubyansky Attachments: jbas-4408.patch The following patch adds support for LIMIT/OFFSET queries in StoreManager2. The patch has passed internal testing. Work was sponsored by World League Sports and licensed under LGPL. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-51) Define Security Caching Interface

by Anil Saldhana (JIRA)

Define Security Caching Interface --------------------------------- Key: SECURITY-51 URL: http://jira.jboss.com/jira/browse/SECURITY-51 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.GA Define a generic Security Caching Interface that can be used for authentication caching, authorization caching 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4350) External, exploded EAR not deployed at startup

by Laszlo Borsos (JIRA)

External, exploded EAR not deployed at startup ---------------------------------------------- Key: JBAS-4350 URL: http://jira.jboss.com/jira/browse/JBAS-4350 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.2.0.CR2, JBossAS-4.2.0.CR1 Environment: Win XP, Java 6.0 Reporter: Laszlo Borsos Assigned To: Dimitris Andreadis When JBoss starts up it does not deploy an EAR (outside the JBoss directory and exploded) with valid META-INF files. However, when invoking the deploy method in MainDeployer MBean from the browser, it deploys and the EJB's work well. The server log shows startup and manual deployment messages. 07:35:09,218 INFO [Server] Starting JBoss (MX MicroKernel)... 07:35:09,218 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.CR2 (build: SVNTag=JBoss_4_2_0_CR2 date=200704160918) ... 07:35:09,218 INFO [Server] Root Deployment Filename: jboss-service.xml 07:35:09,750 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 07:35:09,750 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc. 07:35:09,750 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 ... 07:35:41,078 INFO [EARDeployer] Init J2EE application: file:/C:/Wk/prg/Java/Spekker/spekker.ear 07:35:41,078 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Wk/prg/Java/Spekker/spekker.ear org.jboss.deployment.DeploymentException: No META-INF/application.xml found at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at ... 07:35:41,078 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@1689386d { url=file:/C:/Wk/prg/Java/Spekker/spekker.ear } deployer: org.jboss.deployment.EARDeployer@88d319 status: null state: FAILED watch: file:/C:/Wk/prg/Java/Spekker/spekker.ear altDD: null lastDeployed: 1176960941078 lastModified: 1176824843390 mbeans: 07:35:41,937 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 07:35:41,968 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 07:35:42,109 INFO [Server] JBoss (MX MicroKernel) [4.2.0.CR2 (build: SVNTag=JBoss_4_2_0_CR2 date=200704160918)] Started in 32s:891ms 07:52:36,828 INFO [EARDeployer] Init J2EE application: file:/C:/Wk/prg/Java/Spekker/spekker.ear/ 07:52:38,406 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 07:52:38,406 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=spekker.ear,jar=spekker-ejb.jar,name=SqlServerProxyBean,service=EJB3 with dependencies: 07:52:39,140 INFO [EJBContainer] STARTED EJB: kuvera.ejb.dataware.SqlServerProxyBean ejbName: SqlServerProxyBean 07:52:39,187 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 07:52:39,187 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=spekker.ear,jar=spekker-ejb.jar,name=LogServerProxyBean,service=EJB3 with dependencies: 07:52:39,218 INFO [EJBContainer] STARTED EJB: kuvera.ejb.util.LogServerProxyBean ejbName: LogServerProxyBean 07:52:39,265 INFO [EJB3Deployer] Deployed: file:/C:/Wk/prg/Java/Spekker/spekker.ear/spekker-ejb.jar/ 07:52:39,265 INFO [EARDeployer] Started J2EE application: file:/C:/Wk/prg/Java/Spekker/spekker.ear/ -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-685) Fine grained ACL based security

by Michael Neale (JIRA)

Fine grained ACL based security ------------------------------- Key: JBRULES-685 URL: http://jira.jboss.com/jira/browse/JBRULES-685 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-961) Context class loader not set properly when timeout callback method is called on an MDB

by pgervais (JIRA)

Context class loader not set properly when timeout callback method is called on an MDB --------------------------------------------------------------------------------------- Key: EJBTHREE-961 URL: http://jira.jboss.com/jira/browse/EJBTHREE-961 Project: EJB 3.0 Issue Type: Bug Reporter: pgervais Priority: Minor I used the @Timeout annotation on a method of an MDB, in this method a read messages from JMS. When trying to get content of an ObjectMessage, I get a ClassNotFoundException, the class is in the same EAR as the MDB, it should be 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1396) WSRP Handling of URLs can produce incorrect URLs

by Chris Laprun (JIRA)

WSRP Handling of URLs can produce incorrect URLs ------------------------------------------------ Key: JBPORTAL-1396 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1396 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.CR2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-399) add support for authentication / permissions / ownership

by Michael Neale (JIRA)

add support for authentication / permissions / ownership --------------------------------------------------------- Key: JBRULES-399 URL: http://jira.jboss.com/jira/browse/JBRULES-399 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This authentication/permissions should be tied to the user context that JAAS established. The only things that need to be programmatic are ideally ACLs on a resource. We may need however to show/hide functionality based on the users roles. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-705) Editor widgets to honour "read only" flag

by Michael Neale (JIRA)

Editor widgets to honour "read only" flag ----------------------------------------- Key: JBRULES-705 URL: http://jira.jboss.com/jira/browse/JBRULES-705 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 2 months

2
4
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 May 2007