October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (GPD-3) implement a generation mechanism for the new task forms

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-3?page=all ] Koen Aers updated GPD-3: ------------------------ Fix Version/s: jBPM jPDL Designer 3.1.3 Affects Version/s: (was: jBPM JPDL Designer 3.1.0 alpha1) > implement a generation mechanism for the new task forms > ------------------------------------------------------- > > Key: GPD-3 > URL: http://jira.jboss.com/jira/browse/GPD-3 > Project: JBoss jBPM GPD > Issue Type: Task > Components: jpdl > Reporter: Koen Aers > Assigned To: Koen Aers > Fix For: jBPM jPDL Designer 3.1.3 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1111) JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT

by Len DiMaggio (JIRA)

JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1111 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111 Project: JBoss Messaging Issue Type: Bug Components: JMS Security Affects Versions: 1.4.0.GA Environment: RHEL5 Java 1.5 JBESB - At revision 15800 JBM 1.4.0.GA Reporter: Len DiMaggio Assigned To: Tim Fox Priority: Minor This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! ** I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172 -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-531) Import/Export of Portal Page and Portlet Database Settings

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=all ] Thomas Heute updated JBPORTAL-531: ---------------------------------- Fix Version/s: 2.8 Final > Import/Export of Portal Page and Portlet Database Settings > ---------------------------------------------------------- > > Key: JBPORTAL-531 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-531 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.2 Final, 2.6.2 Final > Reporter: James Williams > Fix For: 2.8 Final > > > There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance. > For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-531) Import/Export of Portal Page and Portlet Database Settings

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=comments#action_12382373 ] Thomas Heute commented on JBPORTAL-531: --------------------------------------- THis is not something we can do with the current isntances deployment. Each portlet-instances.xml must live within their war file (so that the class is loaded before the instance is created), this is not something that can be centralized in 2.6 branch, > Import/Export of Portal Page and Portlet Database Settings > ---------------------------------------------------------- > > Key: JBPORTAL-531 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-531 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.2 Final, 2.6.2 Final > Reporter: James Williams > > There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance. > For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-531) Import/Export of Portal Page and Portlet Database Settings

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=all ] Thomas Heute updated JBPORTAL-531: ---------------------------------- Affects Version/s: 2.6.2 Final > Import/Export of Portal Page and Portlet Database Settings > ---------------------------------------------------------- > > Key: JBPORTAL-531 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-531 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.2 Final, 2.6.2 Final > Reporter: James Williams > > There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance. > For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4809) JCA deployer and metadata incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file

by Weston Price (JIRA)

JCA deployer and metadata incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file --------------------------------------------------------------------------------------------------- Key: JBAS-4809 URL: http://jira.jboss.com/jira/browse/JBAS-4809 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Weston Price Assigned To: Weston Price Fix For: JBossAS-5.0.0.Beta3 The ManagedConnectionEmptyContentAdapter did not correctly unmarshall XA based deployments. As a result, non datasource XA deployments (most notably JmsXA) are being incorrectly identified with local tx support and causing failures. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1752) Update SSO documentation to use AS 4.2 instead of 4.0.x

by Chris Laprun (JIRA)

Update SSO documentation to use AS 4.2 instead of 4.0.x ------------------------------------------------------- Key: JBPORTAL-1752 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1752 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1038) Allow export of database to xml

by William DeCoste (JIRA)

Allow export of database to xml ------------------------------- Key: JBPORTAL-1038 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1038 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: William DeCoste Priority: Minor This feature was requested by Intuit. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1264) NPE at BaseObjectClassFieldExtractor.getLongValue with null fields

by Alexandre Gattiker (JIRA)

NPE at BaseObjectClassFieldExtractor.getLongValue with null fields ------------------------------------------------------------------ Key: JBRULES-1264 URL: http://jira.jboss.com/jira/browse/JBRULES-1264 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Reporter: Alexandre Gattiker Assigned To: Mark Proctor Removing one of the three rules magically solves the problem. java.lang.NullPointerException at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106) at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203) at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467) at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153) at org.drools.reteoo.Rete.assertObject(Rete.java:177) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201) at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659) at com.sample.DroolsTest.main(DroolsTest.java:21) package com.sample; import java.io.InputStreamReader; import java.io.Reader; import org.drools.RuleBase; import org.drools.RuleBaseFactory; import org.drools.WorkingMemory; import org.drools.compiler.PackageBuilder; import org.drools.rule.Package; public class DroolsTest { public static final void main(String[] args) { try { RuleBase ruleBase = readRule(); WorkingMemory workingMemory = ruleBase.newStatefulSession(); workingMemory.insert(new Attribute()); workingMemory.insert(new Message()); workingMemory.fireAllRules(); } catch (Throwable t) { t.printStackTrace(); } } private static RuleBase readRule() throws Exception { Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl")); PackageBuilder builder = new PackageBuilder(); builder.addPackageFromDrl(source); Package pkg = builder.getPackage(); RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage(pkg); return ruleBase; } public static class Message { //empty } public static class Attribute { public Integer getValue() { return null; } } } package com.sample import com.sample.DroolsTest.Message; import com.sample.DroolsTest.Attribute; rule "rule_1" when Message() Attribute(value == 1) then System.err.println("case 1"); end rule "rule_2" when Message() Attribute(value == 2) then System.err.println("case 2"); end rule "rule_3" when Message() $a:Attribute(value == 3) then System.err.println("case 3"); end -- 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, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1750) Explain effect of different values for error handling properties

by Chris Laprun (JIRA)

Explain effect of different values for error handling properties ---------------------------------------------------------------- Key: JBPORTAL-1750 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1750 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun -- 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, 3 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 2007