February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1877) Chengin a consumer id in the wsrp admin portlet leads to an error

by Thomas Heute (JIRA)

Chengin a consumer id in the wsrp admin portlet leads to an error ----------------------------------------------------------------- Key: JBPORTAL-1877 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1877 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.4 Final Reporter: Thomas Heute Assigned To: Chris Laprun Fix For: 2.6.5 Final To reproduce: - Create a consumer - on the screen to add the WSDL address change the consumer id and click on save -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1449) Check subsumption between restrictions

by Toni Rikkola (JIRA)

Check subsumption between restrictions -------------------------------------- Key: JBRULES-1449 URL: http://jira.jboss.com/jira/browse/JBRULES-1449 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Reporter: Toni Rikkola Pattern1 ( x > 10 ) Pattern2 ( x > 100 ) Pattern1 also covers Pattern2. This means that subsumption exists. This data is used when reporting subsumtion between patterns and rules. It is also needed when reporting overlaps. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-686) Inconsistent Channel#getState return semantics between byte and streaming state transfer

by Vladimir Blagojevic (JIRA)

Inconsistent Channel#getState return semantics between byte and streaming state transfer ---------------------------------------------------------------------------------------- Key: JGRP-686 URL: http://jira.jboss.com/jira/browse/JGRP-686 Project: JGroups Issue Type: Bug Affects Versions: 2.6.1, 2.6, 2.5.2, 2.5.1, 2.5 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.6.2, 2.7 We have inconsistency between byte and streaming based state transfer when it comes to semantics of returning from Channel#getState call. In streaming state transfer calling thread returns from Channel#getState when application installs a state (or fails) and for byte transfer calling thread returns from Channel#getState as soon as state arrives to channel and *prior* to state installation in client application. We should make Channel#getState calling thread return *after* state installation for byte based state transfer as well. -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5179) Expose statistic type ManagedProperty for DataSources

by Scott M Stark (JIRA)

Expose statistic type ManagedProperty for DataSources ----------------------------------------------------- Key: JBAS-5179 URL: http://jira.jboss.com/jira/browse/JBAS-5179 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JCA service, Management services Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta4 To really complete the DataSource management view prototype we need to expose some statistic type of properties. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-5111) Upgrade jboss aop to 2.0.0.CRx (from 2.0.0.CR1)

by Dimitris Andreadis (JIRA)

Upgrade jboss aop to 2.0.0.CRx (from 2.0.0.CR1) ----------------------------------------------- Key: JBAS-5111 URL: http://jira.jboss.com/jira/browse/JBAS-5111 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: AOP Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Dimitris Andreadis Assigned To: Kabir Khan Priority: Critical Fix For: JBossAS-5.0.0.Beta4 Basically we need by Jan/18th (or earlier) a new release of jboss APO that resolves the performance problem of JBAOP-497. -- 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, 5 months

2
14
0 / 0

[JBoss JIRA] Created: (JBFORUMS-270) clustered forums

by Luca Stancapiano (JIRA)

clustered forums ---------------- Key: JBFORUMS-270 URL: http://jira.jboss.com/jira/browse/JBFORUMS-270 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Affects Versions: 1.1.0 GA Environment: linux Reporter: Luca Stancapiano Assigned To: Ryszard Kozmik Fix For: 1.1.0 GA hi... I expose all operations that I've done to use jboss forums in a cluster.... they are trasparent . Ant system for build will create three versions of jboss forums. They are: - default .... (jboss-forums.ear) not clusterized version. - ha... (jboss-forums-ha.ear) clustered version not dependent by jboss portal - ha-jbp... (jboss-forums-ha-jbp.ear) clustered version dependent by jboss portal they are many but essentials: - remove of xdoclet in all classes of jboss.portlet.forums.impl package that create configuration files for hibernate. Now there are three type of configurations (default, ha, ha-jbp) and we don't more embed configurations into classes. - creation of a new hbm.xml file that contains all queries executed into forums. Each version has a new Queries.hbm.xml with a different configuration. So we can to assign what query needs to be cacheable. ForumsModuleImpl class uses this configuration instead to declare the queries and never configure cacheable option into the code. Added flush operation for each save with hibernate. It is important for a correct use of clustering - modified build.xml of auth-jaae-plugin so it can to be added also into new two versions of forums. - added a cache-plugin. It is the standalone service for clustering used for ha version. - updated configure target of main build.xml to manage cache-plugin. - updated output, deploy, undeploy, explode and configure targets of build.xml into forums module to create the two new versions of forums. Added the creation of new modules , management of cache-plugin and dependencies to new libraries (jgroups and jboss cache). Removed operations of xdoclet-hiberante and substituted by copy of static configuration files for hibernate. - updated hibernate.jar to 3.2.4.SP1_CP version to introduce clustering with jboss cache. Added jgroups and jboss cache libraries into thirdparty and tools configuration -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-525) Should be possible to serialize a ContainerProxyCacheKey containing (unserializable) MetaData

by Kabir Khan (JIRA)

Should be possible to serialize a ContainerProxyCacheKey containing (unserializable) MetaData --------------------------------------------------------------------------------------------- Key: JBAOP-525 URL: http://jira.jboss.com/jira/browse/JBAOP-525 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR7 -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBAS-3075) ClassLoading code out of sync.

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3075?page=all ] Dimitris Andreadis updated JBAS-3075: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Reschedule for CR1 > ClassLoading code out of sync. > ------------------------------ > > Key: JBAS-3075 > URL: http://jira.jboss.com/jira/browse/JBAS-3075 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Adrian Brock > Fix For: JBossAS-5.0.0.CR1 > > > The classloading code is out-of-sync between jboss-4.0.x and jboss-head. > Looks like all the changes/fixes have not been applied in head. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2563) Cleanup the build for jboss5

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2563?page=all ] Dimitris Andreadis updated JBAS-2563: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Reschedule for CR1 > Cleanup the build for jboss5 > ---------------------------- > > Key: JBAS-2563 > URL: http://jira.jboss.com/jira/browse/JBAS-2563 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-5.0.0.CR1 > > > The current jboss-head build seems rather crusty with outdated modules (media which I removed) and weird modules like jbossas. From the dev list: > This is the remoting/jbossas integration code. > i.e. the UnifiedInvoker > It shouldn't really be in jbossas which was meant to be the top level build folder replacement for "build" > e.g. in the new build > cvs .. co jbossas > cd jbossas > ant rebuild > would pull down all modules and thirdparty and build the release. > Instead jbossas has turned into another "varia" ;-) > On Tue, 2005-12-13 at 03:00, Scott M Stark wrote: > > Why is there this jbossas module in jboss-head when there is also > > remoting being pulled via the thirdparty? > > > We need a plan on cleaning up the jboss-head build using the jbossbuild before creating a jboss5 branch. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2282) JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2282?page=all ] Dimitris Andreadis updated JBAS-2282: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-5.0.0.Beta4) Reschedule for CR1 > JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs > --------------------------------------------------------------------------------- > > Key: JBAS-2282 > URL: http://jira.jboss.com/jira/browse/JBAS-2282 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XML services > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Scott M Stark > Assigned To: Alexey Loubyansky > Fix For: JBossAS-5.0.0.CR1 > > Attachments: jboss-entity-resolver.zip > > > The org.jboss.util.xml.JBossEntityResolver is not dealing with systemIDs that are valid non-file URLs. For example, this xml fragment from a testcase which uses the jboss resource URL: > <?xml version="1.0" encoding="UTF-8"?> >  > <jaas:policy > xsi:schemaLocation="urn:jboss:security-config resource:security-config_4_1.xsd" > xmlns:jaas="urn:jboss:security-config" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > > does map to a valid URL which can be loaded, but the parsing of this URL by the getLocalEntityName ends up throwing away the full path info to produce a resource name of schema/security-config_4_1.xsd. This would work inside the jboss server provided the security-config_4_1.xsd is bundled into a classpath location following the location conventions expected by the JBossEntityResolver, but does not work in the testsuite where this is not the case, and would not work for user defined schemas located elsewhere. It would seem we should try to load the schema from systemIDs that are valid URLs before defaulting to the jboss specific logic. -- 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, 5 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 February 2008