September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1040) Enhancements to DnD

by Roy Russo (JIRA)

Enhancements to DnD ------------------- Key: JBPORTAL-1040 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1040 Project: JBoss Portal Issue Type: Feature Request 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 1. fix ordering to insert at the bottom-most area (after the last portlet). 2. dotted line cleanup.. a. Either default to a simple insertion line, or b. try to simulate netvibes behaviour, of moving all below windows down and showing a highlighted target area. 3. cleanup messy and ill-performant code. (StringBuffers are your friend) 4. title bars, only, should be clickable for dragging. 5. Cursor should change to *something* when over a draggable region (before clicking). -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-483) Open Decision Table API to allow custom RuleSheetListeners

by Steven Williams (JIRA)

Open Decision Table API to allow custom RuleSheetListeners ---------------------------------------------------------- Key: JBRULES-483 URL: http://jira.jboss.com/jira/browse/JBRULES-483 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Steven Williams Assigned To: Mark Proctor I have a need for a different format for my decision tables - basically instead of the current format with one row per rule with conditions across the top I need to support a matrix-like structure where both the horizontal and the vertical axes represent conditions and the intersection represents the action. In order to do this I created my own MatrixRuleSheetListener inheriting from RuleSheetListener and overriding certain methods. This all works fine however I had to hack the drools code a little to allow me to do it. I was wondering if it would be possible to open up the API to allow this. Specifically: 1. add method to org.drools.decisiontable.parser.RuleSheetListener protected void addRule(Rule rule) { this._ruleList.add(rule); } 2. add empty protected methods preInitRuleTable(row, column, value) and postInitRuleTable(row, column, value, rule) to org.drools.decisiontable.parser.RuleSheetListener which are called from the start and end of the initRuleTable method. 3. Add agendaGroup property to org.drools.decisiontable.model.Rule 4. Add a new method compile(InputStream, InputType, RuleSheetListener) to org.drools.decisiontable.SpreadsheetCompiler I have attached these changes to this request. Steve -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3660) Error starting up jaspi config on jboss-head testsuite module

by Jaroslaw Kijanowski (JIRA)

Error starting up jaspi config on jboss-head testsuite module ------------------------------------------------------------- Key: JBAS-3660 URL: http://jira.jboss.com/jira/browse/JBAS-3660 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Jaroslaw Kijanowski Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta The testsuite fails while starting the "jaspi" instance in jbossas beta 5: tests.log: *************************** tests-security-jaspi-unit: [echo] creating jaspi config [copy] Copying 153 files to /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/jboss-5.0.0.Beta/server/jaspi [echo] Overwriting config descriptors [copy] Copying 2 files to /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/jboss-5.0.0.Beta/server/jaspi [server:start] Starting server "jaspi" with command: [server:start] /opt/jrockit-jdk1.5.0_06/bin/java -cp /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/jboss-5.0.0.Beta/bin/run.jar:/opt/jrockit-jdk1.5.0_06/lib/tools.jar org.jboss.Main -c jaspi -b localhost BUILD FAILED /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/build.xml:827: The following error occurred while executing this line: /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/build.xml:2414: Error starting server "jaspi": Server failed to start; see logs. ************************** The server.log contains this: ************************** 11:25:01,556 ERROR [AbstractKernelController] Error installing to Configured: name=jboss.web:service=WebServer state=Instantiated mode=Manual requiredState=Configured org.jboss.deployment.DeploymentException: No Attribute found with name: AuthorizationManagerService for jboss.web:service=WebServer at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:129) ************************** -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-367) Eclipse dependancy versions are too strict/narrow

by Darryl Miles (JIRA)

Eclipse dependancy versions are too strict/narrow ------------------------------------------------- Key: JBIDE-367 URL: http://jira.jboss.com/jira/browse/JBIDE-367 Project: JBoss IDE Issue Type: Bug Components: Build System (Releng) Affects Versions: 2.0.0.Beta1 Reporter: Darryl Miles Assigned To: Marshall Culpepper Priority: Minor Release versioning is too strict and does not allow compatible newer versions of WTP/EMFXSD to be installed. Related URLs: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=87879&postdays=0... http://opensource.atlassian.com/projects/hibernate/browse/HBX-709 This is the error list for after I upgraded WTP to the current I-build for this week. Note I have all of these features/plugins installed but slightly newer versions of them the problem is the features.xml for the JbossIDE product is too strict insisting in the exact version it was built with. When it should really make that the oldest version it will accept. Plug-in "org.eclipse.wst.xml.core" version "1.1.0.v200606142000" referenced by this feature is missing. Plug-in "org.eclipse.wst.xml.ui" version "1.0.100.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.sse.core" version "1.1.0.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.sse.ui" version "1.0.101.v200606191900" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.uriresolver" version "1.1.0.v200606130645" referenced by this feature is missing. Plug-in "org.eclipse.wst.validation" version "1.1.0.v200606130645" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.frameworks" version "1.1.0.v200606130645" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.ui" version "1.1.0.v200606142122" referenced by this feature is missing. Plug-in "org.eclipse.emf.ecore" version "2.2.0.v200606271057" referenced by this feature is missing. Plug-in "org.eclipse.emf.ecore.xmi" version "2.2.0.v200606271057" referenced by this feature is missing. Plug-in "org.eclipse.jst.jsp.core" version "1.1.0.v200606191945" referenced by this feature is missing. Plug-in "org.eclipse.jst.jsp.ui" version "1.1.0.v200606191945" referenced by this feature is missing. Plug-in "org.eclipse.wst.html.core" version "1.1.0.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.html.standard.dtds" version "1.0.0" referenced by this feature is missing. Plug-in "org.eclipse.wst.html.ui" version "1.0.100.v200606191945" referenced by this feature is missing. Plug-in "org.eclipse.wst.css.core" version "1.1.0.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.css.ui" version "1.0.100.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.javascript.core" version "1.0.0.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.javascript.ui" version "1.0.0.v200606141450" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.environment" version "1.0.100.v200606130645" referenced by this feature is missing. Plug-in "org.eclipse.emf.common" version "2.2.0.v200606271057" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.emf" version "1.1.0.v200606130645" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.emfworkbench.integration" version "1.1.0.v200606130645" referenced by this feature is missing. Plug-in "org.eclipse.emf.edit" version "2.2.0.v200606271057" referenced by this feature is missing. Plug-in "org.eclipse.xsd" version "2.2.0.v200606271057" referenced by this feature is missing. Plug-in "org.eclipse.wst.common.project.facet.core" version "1.1.0.v200606130645" referenced by this feature is missing. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-432) One connection per unique JMS server leak

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-432?page=all ] Clebert Suconic updated JBMESSAGING-432: ---------------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90803 > One connection per unique JMS server leak > ----------------------------------------- > > Key: JBMESSAGING-432 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-432 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Reporter: Tim Fox > Assigned To: Clebert Suconic > Priority: Minor > Fix For: 1.0.1.CR5 > > > Methods on connection factory are executed in ConnectionFactoryDelegate on their own client. > This clien is not closed after use, otherwise we end up running out of resources since after closing the client the socket connections are discarded by remoting and end up in the TIME_WAIT state, so cam quickly fill up. > This means that for the lifetime of the VM there will be one socket connection per unique jms server. So a small leak. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-408) Queue binds in jndi but cannot be looked up

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-408?page=all ] Clebert Suconic closed JBMESSAGING-408. --------------------------------------- > Queue binds in jndi but cannot be looked up > ------------------------------------------- > > Key: JBMESSAGING-408 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-408 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: Windows XP, JBoss 4.0.4GA with EJB3 > Reporter: Paul Smith > Assigned To: Clebert Suconic > Attachments: JBoss_queue_binding_issue.zip, test.tar.gz > > > The issue is described under the following forum entry: > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82842 > In short the queue is bound in jndi but cannot be looked up from the context. I have traced what messaging I can but can find no errors. I have also attached the relevant configuration xml and test EJB3 session bean. The connection factory can be looked up correctly but the queue cannot for some reason. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-408) Queue binds in jndi but cannot be looked up

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-408?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-408: --------------------------------------------- You will find test.tar.gz with my package (which has a small build.xml) and few changes I have made. > Queue binds in jndi but cannot be looked up > ------------------------------------------- > > Key: JBMESSAGING-408 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-408 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: Windows XP, JBoss 4.0.4GA with EJB3 > Reporter: Paul Smith > Assigned To: Clebert Suconic > Attachments: JBoss_queue_binding_issue.zip, test.tar.gz > > > The issue is described under the following forum entry: > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82842 > In short the queue is bound in jndi but cannot be looked up from the context. I have traced what messaging I can but can find no errors. I have also attached the relevant configuration xml and test EJB3 session bean. The connection factory can be looked up correctly but the queue cannot for some reason. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBMESSAGING-408) Queue binds in jndi but cannot be looked up

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-408?page=all ] Clebert Suconic resolved JBMESSAGING-408. ----------------------------------------- Fix Version/s: (was: 1.0.1.CR5) Resolution: Cannot Reproduce Bug I suspect you have a configuration issue with your security system. I have deployed your application, and never had any exceptions. (I had to place jboss-messaging.jar into /lib though). > Queue binds in jndi but cannot be looked up > ------------------------------------------- > > Key: JBMESSAGING-408 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-408 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: Windows XP, JBoss 4.0.4GA with EJB3 > Reporter: Paul Smith > Assigned To: Clebert Suconic > Attachments: JBoss_queue_binding_issue.zip, test.tar.gz > > > The issue is described under the following forum entry: > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82842 > In short the queue is bound in jndi but cannot be looked up from the context. I have traced what messaging I can but can find no errors. I have also attached the relevant configuration xml and test EJB3 session bean. The connection factory can be looked up correctly but the queue cannot for some reason. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-408) Queue binds in jndi but cannot be looked up

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-408?page=all ] Clebert Suconic updated JBMESSAGING-408: ---------------------------------------- Attachment: test.tar.gz > Queue binds in jndi but cannot be looked up > ------------------------------------------- > > Key: JBMESSAGING-408 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-408 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.0.1.CR2 > Environment: Windows XP, JBoss 4.0.4GA with EJB3 > Reporter: Paul Smith > Assigned To: Clebert Suconic > Fix For: 1.0.1.CR5 > > Attachments: JBoss_queue_binding_issue.zip, test.tar.gz > > > The issue is described under the following forum entry: > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82842 > In short the queue is bound in jndi but cannot be looked up from the context. I have traced what messaging I can but can find no errors. I have also attached the relevant configuration xml and test EJB3 session bean. The connection factory can be looked up correctly but the queue cannot for some reason. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-5) Integrate OpenDS in HEAD testsuite

by Anil Saldhana (JIRA)

Integrate OpenDS in HEAD testsuite ---------------------------------- Key: SECURITY-5 URL: http://jira.jboss.com/jira/browse/SECURITY-5 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Reporter: Anil Saldhana Assigned To: Anil Saldhana My preliminary testing with OpenDS has been a success. I was able to secure a jmx-console using the LdapLoginModule with the example1.ldif in http://wiki.jboss.org/wiki/Wiki.jsp?page=LdapExtLoginModule Since the configuration of OpenDS is based on scripts that internally call java classes, it should be easy to integrate it into HEAD testsuite. My prelim testing details: ==================================================================== C:\cygwin\home\asaldhana\opends\OpenDS-0.1-build007\bin>start-ds [12/Sep/2006:12:57:14 -0500] category=CORE severity=NOTICE id=458886 msg="OpenDS Directory Server 0.1-build007 starting up." [12/Sep/2006:12:57:15 -0500] category=BACKEND severity=NOTICE id=8847402 msg="A database backend containing 1 entries has started." [12/Sep/2006:12:57:16 -0500] category=CONFIG severity=SEVERE_WARNING id=3277325 msg="Access control has been disabled." [12/Sep/2006:12:57:17 -0500] category=CORE severity=NOTICE id=458887 msg="The Di rectory Server has started successfully." [12/Sep/2006:12:57:17 -0500] category=CORE severity=NOTICE id=458891 msg="The Di rectory Server has sent an alert notification generated by class org.opends.serv er.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, al ert ID 458887): The Directory Server has started successfully.." ================================================================================ ============================================================================= C:\cygwin\home\asaldhana\opends\OpenDS-0.1-build007\bin>ldapmodify -h localhost -D "cn=Directory Manager" -w password -a -f a.ldif Processing ADD request for dc=jboss,dc=org. ADD operation successful for DN dc=jboss,dc=org. Processing ADD request for ou=People,dc=jboss,dc=org. ADD operation successful for DN ou=People,dc=jboss,dc=org. Processing ADD request for uid=jduke,ou=People,dc=jboss,dc=org. ADD operation successful for DN uid=jduke,ou=People,dc=jboss,dc=org. Processing ADD request for ou=Roles,dc=jboss,dc=org. ADD operation successful for DN ou=Roles,dc=jboss,dc=org. Processing ADD request for cn=Echo,ou=Roles,dc=jboss,dc=org. ADD operation successful for DN cn=Echo,ou=Roles,dc=jboss,dc=org. Processing ADD request for cn=TheDuke,ou=Roles,dc=jboss,dc=org. ADD operation successful for DN cn=TheDuke,ou=Roles,dc=jboss,dc=org. =============================================================================== ============================================================================== C:\cygwin\home\asaldhana\opends\OpenDS-0.1-build007\bin>ldapsearch -h localhost -b "dc=jboss,dc=org" -s sub "objectclass=*" dn: dc=jboss,dc=org objectClass: top objectClass: dcObject objectClass: organization o: JBoss dc: jboss dn: ou=People,dc=jboss,dc=org objectClass: top objectClass: organizationalUnit ou: People dn: uid=jduke,ou=People,dc=jboss,dc=org objectClass: top objectClass: person objectClass: uidObject userPassword: {SSHA}XM3FqJX2rfY5Cnzd1Q77gBIsSaiS/MWFfg2LPw== cn: Java Duke sn: Duke uid: jduke ===================================================================================== The application policy: <application-policy name = "jmx-console"> <authentication> <login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required"> <module-option name="java.naming.factory.initial"> com.sun.jndi.ldap.LdapCtxFactory </module-option> <module-option name="java.naming.provider.url"> ldap://localhost:389/ </module-option> <module-option name="java.naming.security.authentication"> simple </module-option> <module-option name="principalDNPrefix">uid=</module-option> <module-option name="principalDNSuffix">,ou=People,dc=jboss,dc=org</module-option> <module-option name="rolesCtxDN">ou=Roles,dc=jboss,dc=org</module-option> <module-option name="uidAttributeID">member</module-option> <module-option name="matchOnUserDN">true</module-option> <module-option name="roleAttributeID">cn</module-option> <module-option name="roleAttributeIsDN">false</module-option> <module-option name="searchTimeLimit">5000</module-option> <module-option name="searchScope">ONELEVEL_SCOPE</module-option> </login-module> </authentication> </application-policy> -- 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, 10 months

1
3
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 September 2006