July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5648) Upgrade to jboss-jaxr-1.0.2.SP1

by Darran Lofthouse (JIRA)

Upgrade to jboss-jaxr-1.0.2.SP1 ------------------------------- Key: JBAS-5648 URL: http://jira.jboss.com/jira/browse/JBAS-5648 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JAXR service Affects Versions: JBossAS-4.2.2.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.2.3.GA -- 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4448) Properties MBean attribues don't update properly

by John Mazzitelli (JIRA)

Properties MBean attribues don't update properly ------------------------------------------------ Key: JBAS-4448 URL: http://jira.jboss.com/jira/browse/JBAS-4448 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Reporter: John Mazzitelli Priority: Minor I have this in my jboss-service.xml for a custom MBean that has a Properties attribute: <attribute name="ConfigurationOverrides" serialDataType="jbxb"> <java:properties xmlns:java="urn:jboss:java-properties" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd"> <java:property> <java:key>my-data-directory</java:key> <java:value>${jboss.server.data.dir}/subdir</java:value> </java:property> ... and more java:property definitions ... I have other non-Properties attributes in my MBean as well. This works fine when starting up. My MBean's setConfigurationOverrides(Properties p) method is called with proper values and everything works. However, if I go to the JMX console, and edit one of my other attributes (simple String attribute), it seems my Properties attribute gets hosed - its values are all screwed up. -- 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

17 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1343) Create a wiki wiki with a possible workaround

by Galder Zamarreno (JIRA)

Create a wiki wiki with a possible workaround --------------------------------------------- Key: JBCACHE-1343 URL: http://jira.jboss.com/jira/browse/JBCACHE-1343 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Possibly update or link somehow from http://wiki.jboss.org/wiki/JDBCCacheLoader <properties> cache.jdbc.datasource=java:/pantherCacheDB cache.jdbc.table.name=jbosscache cache.jdbc.table.create=false cache.jdbc.table.drop=false cache.jdbc.table.primarykey=jbosscache_pk cache.jdbc.fqn.column=fqn cache.jdbc.fqn.type=character varying cache.jdbc.node.column=node cache.jdbc.node.type=bytea cache.jdbc.parent.column=parentfqn cache.jdbc.sql-concat=1||2 </properties> could be deployed as <property name="properties"> <map class="java.util.Properties" keyClass="java.lang.String" valueClass="java.lang.String"> <entry> <key>cache.jdbc.datasource</key> <value>java:/pantherCacheDB</value> </entry> <entry> <key>cache.jdbc.table.name</key> <value>jbosscache</value> </entry> <entry> <key>cache.jdbc.table.create</key> <value>false</value> </entry> <entry> <key>cache.jdbc.table.drop</key> <value>false</value> </entry> <entry> <key>cache.jdbc.table.primarykey</key> <value>jbosscache_pk</value> </entry> <entry> <key>cache.jdbc.fqn.column</key> <value>fqn</value> </entry> <entry> <key>cache.jdbc.fqn.type</key> <value>character varying</value> </entry> <entry> <key>cache.jdbc.node.column</key> <value>node</value> </entry> <entry> <key>cache.jdbc.node.type</key> <value>bytea</value> </entry> <entry> <key>cache.jdbc.parent.column</key> <value>parentfqn</value> </entry> <entry> <key>cache.jdbc.sql-concat</key> <value>1||2</value> </entry> </map> </property> -- 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

17 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2028) Change the active live version of a CMS item should start the ApprovePublish workflow

by Martin Putz (JIRA)

Change the active live version of a CMS item should start the ApprovePublish workflow -------------------------------------------------------------------------------------- Key: JBPORTAL-2028 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2028 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.5 Final Reporter: Martin Putz Assigned To: Sohil Shah A normal CMS user is allowed to change the active live version of an item without asking the admin to do so. Changing the live version should start the ApprovePublish workflow. -- 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2029) Provide the 'Make "Live"' checkox at creation time of a new CMS item

by Martin Putz (JIRA)

Provide the 'Make "Live"' checkox at creation time of a new CMS item -------------------------------------------------------------------- Key: JBPORTAL-2029 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2029 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.5 Final Reporter: Martin Putz Assigned To: Sohil Shah If a CMS user edits an item he can decide to make it live or not. If a CMS user creates a new item he has no decision. A new item automaticly start the ApprovePublish worklow. He should have the option the create a new item and to save it for on-going work. -- 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4589) Upgrade to JSF RI 1.2_05

by Juergen Zimmermann (JIRA)

Upgrade to JSF RI 1.2_05 ------------------------ Key: JBAS-4589 URL: http://jira.jboss.com/jira/browse/JBAS-4589 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Juergen Zimmermann FYI: I ran my testsuite with JSF 1.2_05 RC1 and hadn't any problems. The release notes can be found at https://javaserverfaces.dev.java.net/nonav/rlnotes/1.2_05/changelog.html Citation: "Another change which may impact applications is that we've merged all ServletContextListeners into one listener. In 1.2_04, we had three separate listeners. If a container wasn't compliant in invoking listeners defined in a TLD, the developer had to know all three of these. It seemed to have been a mistake to have so many. The only listener to worry about at this point is com.sun.faces.config.ConfigureListener." ConfigureListener is just being used in org/jboss/web/jsf/integration/config/JBossJSFConfigureListener.java So everything looks fine. -- 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

17 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1306) Search interface for JBoss Cache

by Manik Surtani (JIRA)

Search interface for JBoss Cache -------------------------------- Key: JBCACHE-1306 URL: http://jira.jboss.com/jira/browse/JBCACHE-1306 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.2.0 Could involve either Hibernate Search or JOFTI. Re: Hibernate Search: "HS uses Hibernate's event model to detect changes in objects and updates it's index accordingly. The interface with HS involves search terms which uses the index to extract a set of PKs, which HS uses with Hibernate to return a set of Objects. According to Emmanuel, all that needs to be done is to change HS to use an interface rather than Hibernate's event model directly, and Hibernate's querying directly, and write an implementation that uses JBC's notifications and a cache access instead of the Hibernate counterparts." -- 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

17 years, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JGRP-795) TP: setting a thread factory should set the factory in the corresponding thread pool too

by Bela Ban (JIRA)

TP: setting a thread factory should set the factory in the corresponding thread pool too ---------------------------------------------------------------------------------------- Key: JGRP-795 URL: http://jira.jboss.com/jira/browse/JGRP-795 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6.4, 2.7 Currently, TP.setOOBThreadPoolThreadFactory() and TP.setDefaultThreadPoolThreadFactory() do *not* set the thread factories in teir corresponding thread pools -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2002) VersionException thrown when you try to upload an archive (ZIP) that contains files that already exists in the repository

by Javier Alperte (JIRA)

VersionException thrown when you try to upload an archive (ZIP) that contains files that already exists in the repository -------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-2002 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2002 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.4 Final Environment: JBoss AS 4.2.2, JBoss Portal 2.6.4 Reporter: Javier Alperte Assigned To: Sohil Shah Attachments: ContentCreateCommand.java NOTE: I attach a custom implementation for the "org.jboss.portal.cms.impl.jcr.command.ContentCreateCommand" that solves the problem for me. The problem: If you exports a directory content (for instance: "/default" folder), you make some changes to some files (for instance "index,html"), you zip all the files and try to upload the entire zip to the same directory (make changes over the existent files), the system throwns a VersionException because the system is trying to modify a property over an existent node without doing checkout. What are happening? The CMSAminPortlet is executing the following commands: Command storearchiveCMD = CMSService.getCommandFactory().createStoreArchiveCommand(sPath, is, sLanguage); List contentstoVersion = (List)CMSService.execute(storearchiveCMD); Command createVersions = CMSService.getCommandFactory().createContentCreateNewVersionCommand(contentstoVersion, true); CMSService.execute(createVersions); The command that - i think - is not doing his work fine is the first one (org.jboss.portal.cms.impl.jcr.command.ContentCreateCommand), the implementation is assuming that the files (file+language) doesn't exists in the repository. Exactly, the ContentCreateCommand is looking for the Node that points to the File in the repository (basePath), and adding a new Node for the given language. Instead of that, the code should check if the Node for that language already exists. If the Node (for the given language) already exists, then we only need to change the "jcr:data" and "jcr:lastModified", invoking first the "checout()" method for the node, as i show here: contentNode.checkout(); contentNode.setProperty("jcr:data", new BinaryValue(mFile.getContent().getBytes())); contentNode.setProperty("jcr:lastModified", new DateValue(Calendar.getInstance())); Then, the node is ready to be versioned by the next Command executed in the CMSAdminPortlet (createContentCreateNewVersionCommand). -- 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

17 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5700) messaging-service.xml SecurityMetaDataStore needs to have a dependency on JNDIBasedSecurityRegistration

by Anil Saldhana (JIRA)

messaging-service.xml SecurityMetaDataStore needs to have a dependency on JNDIBasedSecurityRegistration ------------------------------------------------------------------------------------------------------- Key: JBAS-5700 URL: http://jira.jboss.com/jira/browse/JBAS-5700 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (JBoss Messaging) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR2 If an user deploys an MDB jar before the security beans kick in, then the lookup for the security management (java:/securityManagement) will fail with a namenotboundexception. Since we are trying to move the messaging-service.xml to messaging-beans.xml, this issue will probably not exist for a long term. But for now, we need the following depends on <mbean code="org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore" name="jboss.messaging:service=SecurityStore"> .... <depends>JNDIBasedSecurityRegistration</depends> -- 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

17 years, 6 months

1
1
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 July 2008