[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
17 years, 3 months
[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
17 years, 3 months
[JBoss JIRA] Updated: (JBAS-2681) Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
by Seth Wilcox (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2681?page=all ]
Seth Wilcox updated JBAS-2681:
------------------------------
Attachment: LDAPAuth.patch
Fixes unexpected behavior with LdapExtLoginModule when using the password-stacking
> Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
> ---------------------------------------------------------------------------
>
> Key: JBAS-2681
> URL: http://jira.jboss.com/jira/browse/JBAS-2681
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-4.0.3 SP1
> Environment: All
> Reporter: Didier Kreutter
> Attachments: LDAPAuth.patch
>
>
> It would be nice, we could use the "useFirstPass" option of this login-module, like it can be done with the DatabaseServerLoginModule.
> With the construct of the LDAPExtLoginModule, it is not possible to use the LDAP-Directory to search for Roles without having to validate the Password, if this has been done by an precedent LoginModule (DB or SSO).
> I think the problem is in the fact, that the effective Role-Search is done in the overridden "validatePassword" function... witch will never been called when the "useFirstPass" option is set. Is it Possible to fulfill the roles in the getRoleSets() function?
--
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, 3 months