[ https://issues.apache.org/jira/browse/DIRSERVER-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786036#action_12786036
]
Emmanuel Lecharny commented on DIRSERVER-1433:
----------------------------------------------
Tests added for :
boolean add( SchemaObject schemaObject ) throws Exception (AttributeType only)
boolean load( String... schemas ) throws Exception
Should be removed :
boolean loadWithDeps( Schema... schemas ) throws Exception
boolean loadWithDeps( String... schemas ) throws Exception
> Add tests for every methods in SchemaManager
> --------------------------------------------
>
> Key: DIRSERVER-1433
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1433
> Project: Directory ApacheDS
> Issue Type: Test
> Affects Versions: 2.0.0-RC1
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-RC1
>
>
> We have to write tests for each of the SchemaManager method. The following list are all
the methods we want to have some test for, assuming that the add() method has already some
existing tests. The 'T' in from of a method denotates tat this method has some tests.
> Server API :
> boolean load( Schema... schemas ) throws Exception
> boolean load( String... schemas ) throws Exception
> boolean loadWithDeps( Schema... schemas ) throws Exception
> boolean loadWithDeps( String... schemas ) throws Exception
> boolean loadDisabled( Schema... schemas ) throws Exception
> boolean loadDisabled( String... schemas ) throws Exception
> boolean loadAllEnabled() throws Exception
> boolean unload( Schema... schemas )
> boolean unload( String... schemas )
> boolean enable( Schema... schemas ) throws Exception
> boolean enable( String... schemas ) throws Exception
> boolean disable( Schema... schemas )
> boolean disable( String... schemas )
> Studio API :
> boolean loadRelaxed( Schema... schemas ) throws Exception
> boolean loadRelaxed( String... schemas ) throws Exception
> boolean loadWithDepsRelaxed( Schema... schemas ) throws Exception
> boolean loadWithDepsRelaxed( String... schemas ) throws Exception
> boolean loadAllEnabledRelaxed() throws Exception
> boolean enableRelaxed( Schema... schemas )
> boolean enableRelaxed( String... schemas )
> boolean disabledRelaxed( Schema... schemas )
> boolean disabledRelaxed( String... schemas )
> boolean verify( Schema... schemas ) throws Exception
> boolean verify( String... schemas ) throws Exception
> Utility methods :
> T boolean add( SchemaObject schemaObject ) throws Exception
> AttributeType lookupAttributeTypeRegistry( String oid ) throws NamingException
> LdapComparator<?> lookupComparatorRegistry( String oid ) throws NamingException
> void initialize() throws Exception
> boolean isSchemaLoaded( String schemaName )
> getters/setters :
> Registries getRegistries()
> AttributeTypeRegistry getAttributeTypeRegistry()
> ComparatorRegistry getComparatorRegistry()
> DITContentRuleRegistry getDITContentRuleRegistry()
> DITStructureRuleRegistry getDITStructureRuleRegistry()
> MatchingRuleRegistry getMatchingRuleRegistry()
> MatchingRuleUseRegistry getMatchingRuleUseRegistry()
> NormalizerRegistry getNormalizerRegistry()
> NameFormRegistry getNameFormRegistry()
> ObjectClassRegistry getObjectClassRegistry()
> LdapSyntaxRegistry getLdapSyntaxRegistry()
> SyntaxCheckerRegistry getSyntaxCheckerRegistry()
> Map<String, OidNormalizer> getNormalizerMapping()
> void setRegistries( Registries registries )
> List<Throwable> getErrors()
> void setSchemaLoader( SchemaLoader schemaLoader )
> LdapDN getNamingContext()
> SchemaLoader getLoader()
> OidRegistry getOidRegistry()
> Schema getLoadedSchema( String schemaName )
> Should disappear :
> public boolean swapRegistries( Registries targetRegistries ) throws NamingException
> SchemaObject unregister( SchemaObject schemaObject ) throws NamingException
> SchemaObject unregisterAttributeType( String attributeTypeOid ) throws NamingException
> SchemaObject unregisterComparator( String comparatorOid ) throws NamingException
> SchemaObject unregisterDitControlRule( String ditControlRuleOid ) throws NamingException
> SchemaObject unregisterDitStructureRule( String ditStructureRuleOid ) throws NamingException
> SchemaObject unregisterMatchingRule( String matchingRuleOid ) throws NamingException
> SchemaObject unregisterMatchingRuleUse( String matchingRuleUseOid ) throws NamingException
> SchemaObject unregisterNameForm( String nameFormOid ) throws NamingException
> SchemaObject unregisterNormalizer( String normalizerOid ) throws NamingException
> SchemaObject unregisterObjectClass( String objectClassOid ) throws NamingException
> SchemaObject unregisterLdapSyntax( String ldapSyntaxOid ) throws NamingException
> SchemaObject unregisterSyntaxChecker( String syntaxCheckerOid ) throws NamingException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Add tests for every methods in SchemaManager
--------------------------------------------
Key: DIRSERVER-1433
URL: https://issues.apache.org/jira/browse/DIRSERVER-1433
Project: Directory ApacheDS
Issue Type: Test
Affects Versions: 2.0.0-RC1
Reporter: Emmanuel Lecharny
Priority: Critical
Fix For: 2.0.0-RC1
We have to write tests for each of the SchemaManager method. The following list are all the
methods we want to have some test for, assuming that the add() method has already some existing
tests. The 'T' in from of a method denotates tat this method has some tests.
Server API :
boolean load( Schema... schemas ) throws Exception
boolean load( String... schemas ) throws Exception
boolean loadWithDeps( Schema... schemas ) throws Exception
boolean loadWithDeps( String... schemas ) throws Exception
boolean loadDisabled( Schema... schemas ) throws Exception
boolean loadDisabled( String... schemas ) throws Exception
boolean loadAllEnabled() throws Exception
boolean unload( Schema... schemas )
boolean unload( String... schemas )
boolean enable( Schema... schemas ) throws Exception
boolean enable( String... schemas ) throws Exception
boolean disable( Schema... schemas )
boolean disable( String... schemas )
Studio API :
boolean loadRelaxed( Schema... schemas ) throws Exception
boolean loadRelaxed( String... schemas ) throws Exception
boolean loadWithDepsRelaxed( Schema... schemas ) throws Exception
boolean loadWithDepsRelaxed( String... schemas ) throws Exception
boolean loadAllEnabledRelaxed() throws Exception
boolean enableRelaxed( Schema... schemas )
boolean enableRelaxed( String... schemas )
boolean disabledRelaxed( Schema... schemas )
boolean disabledRelaxed( String... schemas )
boolean verify( Schema... schemas ) throws Exception
boolean verify( String... schemas ) throws Exception
Utility methods :
T boolean add( SchemaObject schemaObject ) throws Exception
AttributeType lookupAttributeTypeRegistry( String oid ) throws NamingException
LdapComparator<?> lookupComparatorRegistry( String oid ) throws NamingException
void initialize() throws Exception
boolean isSchemaLoaded( String schemaName )
getters/setters :
Registries getRegistries()
AttributeTypeRegistry getAttributeTypeRegistry()
ComparatorRegistry getComparatorRegistry()
DITContentRuleRegistry getDITContentRuleRegistry()
DITStructureRuleRegistry getDITStructureRuleRegistry()
MatchingRuleRegistry getMatchingRuleRegistry()
MatchingRuleUseRegistry getMatchingRuleUseRegistry()
NormalizerRegistry getNormalizerRegistry()
NameFormRegistry getNameFormRegistry()
ObjectClassRegistry getObjectClassRegistry()
LdapSyntaxRegistry getLdapSyntaxRegistry()
SyntaxCheckerRegistry getSyntaxCheckerRegistry()
Map<String, OidNormalizer> getNormalizerMapping()
void setRegistries( Registries registries )
List<Throwable> getErrors()
void setSchemaLoader( SchemaLoader schemaLoader )
LdapDN getNamingContext()
SchemaLoader getLoader()
OidRegistry getOidRegistry()
Schema getLoadedSchema( String schemaName )
Should disappear :
public boolean swapRegistries( Registries targetRegistries ) throws NamingException
SchemaObject unregister( SchemaObject schemaObject ) throws NamingException
SchemaObject unregisterAttributeType( String attributeTypeOid ) throws NamingException
SchemaObject unregisterComparator( String comparatorOid ) throws NamingException
SchemaObject unregisterDitControlRule( String ditControlRuleOid ) throws NamingException
SchemaObject unregisterDitStructureRule( String ditStructureRuleOid ) throws NamingException
SchemaObject unregisterMatchingRule( String matchingRuleOid ) throws NamingException
SchemaObject unregisterMatchingRuleUse( String matchingRuleUseOid ) throws NamingException
SchemaObject unregisterNameForm( String nameFormOid ) throws NamingException
SchemaObject unregisterNormalizer( String normalizerOid ) throws NamingException
SchemaObject unregisterObjectClass( String objectClassOid ) throws NamingException
SchemaObject unregisterLdapSyntax( String ldapSyntaxOid ) throws NamingException
SchemaObject unregisterSyntaxChecker( String syntaxCheckerOid ) throws NamingException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi, so I have made some progress lately. I have written unit tests on the schemaManager for the AttributeType schema object, and it helped me to fix numerous errors. I also fixed some other errors in some other tests, and I'm back to where I was stuck : core-integ. That's not a bad situation though, as many cleanup has been done since the last time I was able to run all the tests, but I'm confident this time that I'm move forward to the end of this huge refactoring ... (uhhh, seems that I alreay said that many times ;)
[ https://issues.apache.org/jira/browse/DIRSTUDIO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot updated DIRSTUDIO-603:
---------------------------------------------
Fix Version/s: 1.5.2
> Error browsing/entering rfc2307 compliant host entry
> ----------------------------------------------------
>
> Key: DIRSTUDIO-603
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-603
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldifeditor
> Affects Versions: 1.5.1
> Environment: Ubuntu 9.04
> java version 1.6.0_0
> Reporter: Jonathan Craig
> Fix For: 1.5.2
>
>
> A rfc2307 entry is as follows:
> dn: cn=loopback+ipHostNumber=127.0.0.1,ou=Hosts,dc=mygfs,dc=com
> objectClass: ipHost
> objectClass: device
> objectClass: top
> cn: loopback
> ipHostNumber: 127.0.0.1
> When I browse this group I receive the following error:
> 'Read Children' has encountered a problem.
> Error while reading entry
> - unexpected token: 127.0.0.1
> javax.naming.InvalidNameException: unexpected token: 127.0.0.1 [Root exception is line
1:26: unexpected token: 127.0.0.1]
> at org.apache.directory.shared.ldap.name.ComplexLdapDnParser.parseDn(ComplexLdapDnParser.java:55)
> at org.apache.directory.shared.ldap.name.LdapDnParser.parseInternal(LdapDnParser.java:97)
> at org.apache.directory.shared.ldap.name.LdapDN.<init>(LdapDN.java:205)
> at org.apache.directory.studio.ldapbrowser.core.utils.JNDIUtils.getDn(JNDIUtils.java:48)
> at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.searchAndUpdateModel(SearchRunnable.java:331)
> at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.executeSearch(InitializeChildrenRunnable.java:361)
> at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.initializeChildren(InitializeChildrenRunnable.java:212)
> at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.run(InitializeChildrenRunnable.java:171)
> at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:114)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: line 1:26: unexpected token: 127.0.0.1
> at org.apache.directory.shared.ldap.name.AntlrDnParser.attributeValue(AntlrDnParser.java:550)
> at org.apache.directory.shared.ldap.name.AntlrDnParser.attributeTypeAndValue(AntlrDnParser.java:405)
> at org.apache.directory.shared.ldap.name.AntlrDnParser.relativeDistinguishedName(AntlrDnParser.java:252)
> at org.apache.directory.shared.ldap.name.AntlrDnParser.relativeDistinguishedNames(AntlrDnParser.java:307)
> at org.apache.directory.shared.ldap.name.ComplexLdapDnParser.parseDn(ComplexLdapDnParser.java:51)
> ... 9 more
> unexpected token: 127.0.0.1
> When I use the "new entry from scratch" wizard I receive an "invalid RDN" during data
entry. First I select the three object classes from above. I then add the cn= entry. I
then start entering the ipHostNumber and if the host number ends in ".[0-9]*" the preview
says "RDN is invalid". If I end the ipHostNumber with a "." or ".[a-zA-Z]*" the RDN is accepted
and the entry created. The entries that are created in this manner are viewable in the browser.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot closed DIRSTUDIO-601.
--------------------------------------------
Resolution: Fixed
Assignee: Pierre-Arnaud Marcelot
Fixed at revision 887222.
http://svn.apache.org/viewvc?rev=887222&view=rev
> The 'Perform Search/Search Again' button in the Search Result Editor does not work correctly
> --------------------------------------------------------------------------------------------
>
> Key: DIRSTUDIO-601
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-601
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 1.5.1
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Pierre-Arnaud Marcelot
> Priority: Critical
> Fix For: 1.5.2
>
>
> The 'Perform Search/Search Again' button in the Search Result Editor does not work correctly.
> If I click on the 'Perform Search/Search Again' button, the search is not updated.
> If the search was not yet performed, it isn't either at the end of the command.
> if the search was already performed, the search results are not updated (even if entries
have changed and does not match the search anymore).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Arnaud Marcelot closed DIRSTUDIO-602.
--------------------------------------------
Resolution: Fixed
It should be fixed now.
> Unable to start an Apache DS version 1.5.5 server
> -------------------------------------------------
>
> Key: DIRSTUDIO-602
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-602
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-apacheds
> Affects Versions: 1.5.1
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Pierre-Arnaud Marcelot
> Priority: Blocker
> Fix For: 1.5.2
>
>
> Unable to start an Apache DS version 1.5.5 server.
> NPE when copying that damn apacheds-launcher library...
> !ENTRY org.eclipse.ui 4 0 2009-12-03 16:32:33.271
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.apache.directory.studio.apacheds.ApacheDsPluginUtils.copyLibrary(ApacheDsPluginUtils.java:224)
> at org.apache.directory.studio.apacheds.ApacheDsPluginUtils.verifyLibrariesFolder(ApacheDsPluginUtils.java:99)
> at org.apache.directory.studio.apacheds.actions.RunAction.run(RunAction.java:173)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1598)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1622)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1607)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1396)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3484)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3068)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.apache.directory.studio.Application.start(Application.java:58)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Error browsing/entering rfc2307 compliant host entry
----------------------------------------------------
Key: DIRSTUDIO-603
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-603
Project: Directory Studio
Issue Type: Bug
Components: studio-ldifeditor
Affects Versions: 1.5.1
Environment: Ubuntu 9.04
java version 1.6.0_0
Reporter: Jonathan Craig
A rfc2307 entry is as follows:
dn: cn=loopback+ipHostNumber=127.0.0.1,ou=Hosts,dc=mygfs,dc=com
objectClass: ipHost
objectClass: device
objectClass: top
cn: loopback
ipHostNumber: 127.0.0.1
When I browse this group I receive the following error:
'Read Children' has encountered a problem.
Error while reading entry
- unexpected token: 127.0.0.1
javax.naming.InvalidNameException: unexpected token: 127.0.0.1 [Root exception is line 1:26:
unexpected token: 127.0.0.1]
at org.apache.directory.shared.ldap.name.ComplexLdapDnParser.parseDn(ComplexLdapDnParser.java:55)
at org.apache.directory.shared.ldap.name.LdapDnParser.parseInternal(LdapDnParser.java:97)
at org.apache.directory.shared.ldap.name.LdapDN.<init>(LdapDN.java:205)
at org.apache.directory.studio.ldapbrowser.core.utils.JNDIUtils.getDn(JNDIUtils.java:48)
at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.searchAndUpdateModel(SearchRunnable.java:331)
at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.executeSearch(InitializeChildrenRunnable.java:361)
at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.initializeChildren(InitializeChildrenRunnable.java:212)
at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.run(InitializeChildrenRunnable.java:171)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:114)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: line 1:26: unexpected token: 127.0.0.1
at org.apache.directory.shared.ldap.name.AntlrDnParser.attributeValue(AntlrDnParser.java:550)
at org.apache.directory.shared.ldap.name.AntlrDnParser.attributeTypeAndValue(AntlrDnParser.java:405)
at org.apache.directory.shared.ldap.name.AntlrDnParser.relativeDistinguishedName(AntlrDnParser.java:252)
at org.apache.directory.shared.ldap.name.AntlrDnParser.relativeDistinguishedNames(AntlrDnParser.java:307)
at org.apache.directory.shared.ldap.name.ComplexLdapDnParser.parseDn(ComplexLdapDnParser.java:51)
... 9 more
unexpected token: 127.0.0.1
When I use the "new entry from scratch" wizard I receive an "invalid RDN" during data entry.
First I select the three object classes from above. I then add the cn= entry. I then start
entering the ipHostNumber and if the host number ends in ".[0-9]*" the preview says "RDN is
invalid". If I end the ipHostNumber with a "." or ".[a-zA-Z]*" the RDN is accepted and the
entry created. The entries that are created in this manner are viewable in the browser.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Committed at revision 887167. http://svn.apache.org/viewvc?rev=887167&view=rev Regards, P-A On 4 déc. 2009, at 08:53, Pierre-Arnaud Marcelot wrote: > Hi Felix, > > On 3 déc. 2009, at 22:01, Felix Knecht wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Pierre-Arnaud Marcelot schrieb: >>> Hi all, >>> >>> I'd like to propose the removal of our specific per-plugin version to use the inherited parent pom version instead. >> >> That was a requirement at the time I created the maven build - but I've >> never really understood, why they might have a different version ... > > That's exactly what I remembered when writing the first mail actually. > > The idea was to recreate the build we had with Ant+Ivy and in case of a small update only distribute the plugins that got modified since the last version. > > But with our multi-modules maven project and the use of the release plugin, this is clearly something we can't really do. > > I think at the time I didn't know Maven that well, especially the automated releases part. > > My bad... :( > > >> Remove them :-) > > Sure. > I'm almost done and ready to commit. > > Thanks, > Pierre-Arnaud
WARN: Null LdapSession given to cleanUpSession.
-----------------------------------------------
Key: DIRSERVER-1432
URL: https://issues.apache.org/jira/browse/DIRSERVER-1432
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.5
Environment: Ubuntu 9.10 and Debian Lenny
Reporter: A. M.
Priority: Minor
When searching using ldapsearch the following message appears in the log:
[15:09:06] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Null LdapSession
given to cleanUpSession.
Sometimes also this:
[15:09:14] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Unexpected exception
forcing session to close: sending disconnect notice to client.
java.lang.NullPointerException
at org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:129)
at org.apache.directory.server.ldap.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:56)
at org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:232)
at org.apache.directory.server.ldap.LdapProtocolHandler.messageReceived(LdapProtocolHandler.java:194)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:721)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:433)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:47)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:801)
at org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:71)
at org.apache.mina.core.session.IoEvent.run(IoEvent.java:63)
at org.apache.mina.filter.executor.UnorderedThreadPoolExecutor$Worker.runTask(UnorderedThreadPoolExecutor.java:480)
at org.apache.mina.filter.executor.UnorderedThreadPoolExecutor$Worker.run(UnorderedThreadPoolExecutor.java:434)
at java.lang.Thread.run(Thread.java:619)
[15:09:14] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Null LdapSession
given to cleanUpSession.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1430.
----------------------------------------
fixed
> The GlobalOid registry is not updated (or rebuilt) when loading a ful schema
> ----------------------------------------------------------------------------
>
> Key: DIRSERVER-1430
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1430
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 2.0.0-RC1
>
>
> The globalOidRegistry is not updated when loading a full schema
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1430.
------------------------------------------
Resolution: Fixed
The Registries was not cloned correctly.
Fixed with http://svn.apache.org/viewvc?rev=887004&view=rev
> The GlobalOid registry is not updated (or rebuilt) when loading a ful schema
> ----------------------------------------------------------------------------
>
> Key: DIRSERVER-1430
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1430
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 2.0.0-RC1
>
>
> The globalOidRegistry is not updated when loading a full schema
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi Felix, On 3 déc. 2009, at 22:01, Felix Knecht wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Pierre-Arnaud Marcelot schrieb: >> Hi all, >> >> I'd like to propose the removal of our specific per-plugin version to use the inherited parent pom version instead. > > That was a requirement at the time I created the maven build - but I've > never really understood, why they might have a different version ... That's exactly what I remembered when writing the first mail actually. The idea was to recreate the build we had with Ant+Ivy and in case of a small update only distribute the plugins that got modified since the last version. But with our multi-modules maven project and the use of the release plugin, this is clearly something we can't really do. I think at the time I didn't know Maven that well, especially the automated releases part. My bad... :( > Remove them :-) Sure. I'm almost done and ready to commit. Thanks, Pierre-Arnaud
[ https://issues.apache.org/jira/browse/DIRSERVER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785596#action_12785596
]
Adam J commented on DIRSERVER-1431:
-----------------------------------
What is the correct way to install ApacheDS?
> Install ApachdDS on AIX 5.3
> ---------------------------
>
> Key: DIRSERVER-1431
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Environment: AIX 5.3 system model 9133-55A
> Reporter: Adam J
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am trying to install ApacheDS. I download the tar file and here is the output of my
steps I have taken:
> # pwd
> /tmp/apachedirectory
> # ls
> apacheds-1.5.5.tar
> # tar -xf apacheds-1.5.5.tar
> # ls
> apacheds-1.5.5.tar apacheds_1.5.5
> # cd apacheds_1.5.5
> # ls
> LICENSE apacheds.bat bin cpappend.bat lib
> NOTICE apacheds.sh conf feather.ico var
> # ./apacheds.sh
> _ _ ____ ____
> / \ _ __ ___ ___| |__ ___| _ \/ ___|
> / _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
> / ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
> /_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
> |_|
> [14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
OID for name 'krb5PrincipalName' was not found within the OID registry
> [14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
> *** It just hangs here after this error, and does not proceed to execute the install.
> Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785597#action_12785597
]
Adam J commented on DIRSERVER-1431:
-----------------------------------
So there is no installation process? Is it similar to tomcat install? Is there
a way to have it up at all times, without having on hanging through terminal?
> Install ApachdDS on AIX 5.3
> ---------------------------
>
> Key: DIRSERVER-1431
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Environment: AIX 5.3 system model 9133-55A
> Reporter: Adam J
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am trying to install ApacheDS. I download the tar file and here is the output of my
steps I have taken:
> # pwd
> /tmp/apachedirectory
> # ls
> apacheds-1.5.5.tar
> # tar -xf apacheds-1.5.5.tar
> # ls
> apacheds-1.5.5.tar apacheds_1.5.5
> # cd apacheds_1.5.5
> # ls
> LICENSE apacheds.bat bin cpappend.bat lib
> NOTICE apacheds.sh conf feather.ico var
> # ./apacheds.sh
> _ _ ____ ____
> / \ _ __ ___ ___| |__ ___| _ \/ ___|
> / _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
> / ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
> /_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
> |_|
> [14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
OID for name 'krb5PrincipalName' was not found within the OID registry
> [14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
> *** It just hangs here after this error, and does not proceed to execute the install.
> Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785591#action_12785591
]
Pierre-Arnaud Marcelot commented on DIRSERVER-1431:
---------------------------------------------------
Actually the tar.gz and zip files are not installers but simple archive packages.
What you've done by launching the 'apacheds.sh' script is launching the server...
That's it.
It should be running on port 10389.
> Install ApachdDS on AIX 5.3
> ---------------------------
>
> Key: DIRSERVER-1431
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Environment: AIX 5.3 system model 9133-55A
> Reporter: Adam J
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am trying to install ApacheDS. I download the tar file and here is the output of my
steps I have taken:
> # pwd
> /tmp/apachedirectory
> # ls
> apacheds-1.5.5.tar
> # tar -xf apacheds-1.5.5.tar
> # ls
> apacheds-1.5.5.tar apacheds_1.5.5
> # cd apacheds_1.5.5
> # ls
> LICENSE apacheds.bat bin cpappend.bat lib
> NOTICE apacheds.sh conf feather.ico var
> # ./apacheds.sh
> _ _ ____ ____
> / \ _ __ ___ ___| |__ ___| _ \/ ___|
> / _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
> / ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
> /_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
> |_|
> [14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
OID for name 'krb5PrincipalName' was not found within the OID registry
> [14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
> *** It just hangs here after this error, and does not proceed to execute the install.
> Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785587#action_12785587
]
Stefan Seelmann commented on DIRSERVER-1431:
--------------------------------------------
Hi Adam,
this "error" message is printed by ApacheDS 1.5.5, but it is not really an error, we just
used the wrong log level. Please ignore those two lines.
Regarding hang: in your case - as you use the tar archive - there is no installer. The script
"./apacheds" just starts up ApacheDS. So ApacheDS should be up an running and listening on
port 10389 :-)
> Install ApachdDS on AIX 5.3
> ---------------------------
>
> Key: DIRSERVER-1431
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Environment: AIX 5.3 system model 9133-55A
> Reporter: Adam J
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am trying to install ApacheDS. I download the tar file and here is the output of my
steps I have taken:
> # pwd
> /tmp/apachedirectory
> # ls
> apacheds-1.5.5.tar
> # tar -xf apacheds-1.5.5.tar
> # ls
> apacheds-1.5.5.tar apacheds_1.5.5
> # cd apacheds_1.5.5
> # ls
> LICENSE apacheds.bat bin cpappend.bat lib
> NOTICE apacheds.sh conf feather.ico var
> # ./apacheds.sh
> _ _ ____ ____
> / \ _ __ ___ ___| |__ ___| _ \/ ___|
> / _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
> / ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
> /_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
> |_|
> [14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
OID for name 'krb5PrincipalName' was not found within the OID registry
> [14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
> *** It just hangs here after this error, and does not proceed to execute the install.
> Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785583#action_12785583
]
Adam J commented on DIRSERVER-1431:
-----------------------------------
Hi Emmanuel,
Ok, thought that error would help, first time I install ApacheDS.
# java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap3260sr5-20090529_04(SR5))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32
jvmap3260sr5-20090519_35743 (JIT enabled, AOT enabled)
J9VM - 20090519_035743_bHdSMr
JIT - r9_20090518_2017
GC - 20090417_AA)
JCL - 20090529_01
#
> Install ApachdDS on AIX 5.3
> ---------------------------
>
> Key: DIRSERVER-1431
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Environment: AIX 5.3 system model 9133-55A
> Reporter: Adam J
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am trying to install ApacheDS. I download the tar file and here is the output of my
steps I have taken:
> # pwd
> /tmp/apachedirectory
> # ls
> apacheds-1.5.5.tar
> # tar -xf apacheds-1.5.5.tar
> # ls
> apacheds-1.5.5.tar apacheds_1.5.5
> # cd apacheds_1.5.5
> # ls
> LICENSE apacheds.bat bin cpappend.bat lib
> NOTICE apacheds.sh conf feather.ico var
> # ./apacheds.sh
> _ _ ____ ____
> / \ _ __ ___ ___| |__ ___| _ \/ ___|
> / _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
> / ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
> /_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
> |_|
> [14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
OID for name 'krb5PrincipalName' was not found within the OID registry
> [14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
> *** It just hangs here after this error, and does not proceed to execute the install.
> Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Ersin ER a écrit : > Hi, > > As far as I understand size of a page in our JDBM implementation is > specified in terms of number of entries, not in bytes. So we're not using > fixed length pages. In such a case how can we control the amount of memory > that JDBM uses? And from both theoretical and practical perspective, how > does variable length pages affect performance? (Or am I mistaken about > this?) > I have no idea. This is definitively something we have to dig if we want to be serious about tunning, in any case. Right now, we focused on getting the server woring and be compliant... > Greetings, > >
Hi, As far as I understand size of a page in our JDBM implementation is specified in terms of number of entries, not in bytes. So we're not using fixed length pages. In such a case how can we control the amount of memory that JDBM uses? And from both theoretical and practical perspective, how does variable length pages affect performance? (Or am I mistaken about this?) Greetings, -- Ersin ER http://www.ersiner.net
[ https://issues.apache.org/jira/browse/DIRSERVER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785568#action_12785568
]
Emmanuel Lecharny commented on DIRSERVER-1431:
----------------------------------------------
Those errors are irrelevant at this point.
Which JVM are you using on your machine ?
> Install ApachdDS on AIX 5.3
> ---------------------------
>
> Key: DIRSERVER-1431
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Environment: AIX 5.3 system model 9133-55A
> Reporter: Adam J
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I am trying to install ApacheDS. I download the tar file and here is the output of my
steps I have taken:
> # pwd
> /tmp/apachedirectory
> # ls
> apacheds-1.5.5.tar
> # tar -xf apacheds-1.5.5.tar
> # ls
> apacheds-1.5.5.tar apacheds_1.5.5
> # cd apacheds_1.5.5
> # ls
> LICENSE apacheds.bat bin cpappend.bat lib
> NOTICE apacheds.sh conf feather.ico var
> # ./apacheds.sh
> _ _ ____ ____
> / \ _ __ ___ ___| |__ ___| _ \/ ___|
> / _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
> / ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
> /_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
> |_|
> [14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
OID for name 'krb5PrincipalName' was not found within the OID registry
> [14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
> *** It just hangs here after this error, and does not proceed to execute the install.
> Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Install ApachdDS on AIX 5.3
---------------------------
Key: DIRSERVER-1431
URL: https://issues.apache.org/jira/browse/DIRSERVER-1431
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.5
Environment: AIX 5.3 system model 9133-55A
Reporter: Adam J
I am trying to install ApacheDS. I download the tar file and here is the output of my steps
I have taken:
# pwd
/tmp/apachedirectory
# ls
apacheds-1.5.5.tar
# tar -xf apacheds-1.5.5.tar
# ls
apacheds-1.5.5.tar apacheds_1.5.5
# cd apacheds_1.5.5
# ls
LICENSE apacheds.bat bin cpappend.bat lib
NOTICE apacheds.sh conf feather.ico var
# ./apacheds.sh
_ _ ____ ____
/ \ _ __ ___ ___| |__ ___| _ \/ ___|
/ _ \ | '_ \ / _` |/ __| '_ \ / _ \ | | \___ \
/ ___ \| |_) | (_| | (__| | | | __/ |_| |___) |
/_/ \_\ .__/ \__,_|\___|_| |_|\___|____/|____/
|_|
[14:50:47] WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] - OID for
name 'krb5PrincipalName' was not found within the OID registry
[14:50:49] ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
- attributeType w/ OID 2.5.4.16 not registered!
*** It just hangs here after this error, and does not proceed to execute the install.
Any suggestions on what I can do to resolve this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pierre-Arnaud Marcelot schrieb: > Hi all, > > I'd like to propose the removal of our specific per-plugin version to use the inherited parent pom version instead. That was a requirement at the time I created the maven build - but I've never really understood, why they might have a different version ... Remove them :-) Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksYJ0QACgkQ2lZVCB08qHHL7ACdHvLF+RGnb0uEtBrddZtU3S8q JvsAoMvq80LtAGztSZrQz50/wjMY5DMq =iX2m -----END PGP SIGNATURE-----
Excellent thanks for the heads up Emmanuel. Alex On Thu, Dec 3, 2009 at 1:38 PM, Emmanuel Lecharny <elecharny@gmail.com>wrote: > Hi, > > after a few days without computer (my laptop died), and a couple of days > instling my brand new MBP, I was able to work again on the schema. > > The code is much cleaner, with many refactoring done, improvement, cleaning > and factorisation. AT addition has been fully tested (unit tests added), at > least directly in the SchemaManager. The same work still has to be done for > the direct injection into the server. > > I will work on the schema enabling and disabling soon, the code is ready > but some tests are needed. > > Some JIRA will be created for each set of tests needed, for each > SchemaObjects. > > So far, looking better and better ! > -- Alex Karasulu My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://directory.apache.org Apache MINA :: http://mina.apache.org
Pierre-Arnaud Marcelot wrote: > Hi all, > > I'd like to propose the removal of our specific per-plugin version to use the inherited parent pom version instead. > ... > These properties have always been a source of annoyance because they're not very well handled by the release plugin (and sometimes, some of them are not replaced correctly) and I think they're not really necessary. > > Since we're releasing the project as a whole, I think each project needs to inherit the version defined in the parent pom. > > WDYT? > Any objection? Just go for it. Everything that could make releasing easier and less error-prone is OK. Kind Regards, Stefan
The GlobalOid registry is not updated (or rebuilt) when loading a ful schema
----------------------------------------------------------------------------
Key: DIRSERVER-1430
URL: https://issues.apache.org/jira/browse/DIRSERVER-1430
Project: Directory ApacheDS
Issue Type: Bug
Reporter: Emmanuel Lecharny
Assignee: Emmanuel Lecharny
Priority: Blocker
Fix For: 2.0.0-RC1
The globalOidRegistry is not updated when loading a full schema
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Implement tests for Syntax additions in SchemaManager
-----------------------------------------------------
Key: DIRSERVER-1429
URL: https://issues.apache.org/jira/browse/DIRSERVER-1429
Project: Directory ApacheDS
Issue Type: Test
Affects Versions: 1.5.5
Reporter: Emmanuel Lecharny
Fix For: 2.0.0-RC1
We need tests for the SchemaManager, in shared-ldap-schema-loader project :
- The syntax must not already exist
- The associated SyntxChecker must exist
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi, after a few days without computer (my laptop died), and a couple of days instling my brand new MBP, I was able to work again on the schema. The code is much cleaner, with many refactoring done, improvement, cleaning and factorisation. AT addition has been fully tested (unit tests added), at least directly in the SchemaManager. The same work still has to be done for the direct injection into the server. I will work on the schema enabling and disabling soon, the code is ready but some tests are needed. Some JIRA will be created for each set of tests needed, for each SchemaObjects. So far, looking better and better !
[ https://issues.apache.org/jira/browse/DIRSERVER-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785430#action_12785430
]
Emmanuel Lecharny commented on DIRSERVER-1428:
----------------------------------------------
Also we should test that :
- a valid OC is accepted (obviously !)
- an OC is accepted even if some AT in the MAY or MUST are duplicated (ie, we have twice the
same AT in MAY)
- an OC is accepted even if some AT is duplicated in MAY or MUST, but defined with different
names (as 'cn' and CommonName' in MAY)
- an OC is accepted even if an AT is present in the MAY and MUST at the same time (even if
different names are used)
> Implement tests for ObjectClass additions in SchemaManager
> ----------------------------------------------------------
>
> Key: DIRSERVER-1428
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1428
> Project: Directory ApacheDS
> Issue Type: Test
> Affects Versions: 1.5.5
> Reporter: Emmanuel Lecharny
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> We need tests for the SchemaManager, in shared-ldap-schema-loader project :
> o OC with no superiors
> - All the MAY must exist
> - All the MUST must exist
> o OC with superiors
> - no cycle allowed (cannot be it's own superior)
> - if STRUCTURAL, cannot have an AUXILIARY in its superiors
> - if AUXILIARY, cannot have a STRUCTURAL in its superiors
> - if ABSTRACT, cannot have a STRUCTURAL or an AUXILIARY in its superiors
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Implement tests for ObjectClass additions in SchemaManager
----------------------------------------------------------
Key: DIRSERVER-1428
URL: https://issues.apache.org/jira/browse/DIRSERVER-1428
Project: Directory ApacheDS
Issue Type: Test
Affects Versions: 1.5.5
Reporter: Emmanuel Lecharny
Assignee: Kiran Ayyagari
Fix For: 2.0.0-RC1
We need tests for the SchemaManager, in shared-ldap-schema-loader project :
o OC with no superiors
- All the MAY must exist
- All the MUST must exist
o OC with superiors
- no cycle allowed (cannot be it's own superior)
- if STRUCTURAL, cannot have an AUXILIARY in its superiors
- if AUXILIARY, cannot have a STRUCTURAL in its superiors
- if ABSTRACT, cannot have a STRUCTURAL or an AUXILIARY in its superiors
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Errors should contain the associated SchemaObject when modifying the schema
---------------------------------------------------------------------------
Key: DIRSERVER-1427
URL: https://issues.apache.org/jira/browse/DIRSERVER-1427
Project: Directory ApacheDS
Issue Type: New Feature
Reporter: Emmanuel Lecharny
Fix For: 2.0.0-RC1
Currently, when modifying the Schema, we just gather all the exceptions. Each one of them
should be associated with the SchemaObject which generated this exception, in order to be
used by Studio.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny reassigned DIRSERVER-1427:
--------------------------------------------
Assignee: Emmanuel Lecharny
> Errors should contain the associated SchemaObject when modifying the schema
> ---------------------------------------------------------------------------
>
> Key: DIRSERVER-1427
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1427
> Project: Directory ApacheDS
> Issue Type: New Feature
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Fix For: 2.0.0-RC1
>
>
> Currently, when modifying the Schema, we just gather all the exceptions. Each one of
them should be associated with the SchemaObject which generated this exception, in order to
be used by Studio.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1426.
------------------------------------------
Resolution: Fixed
Assignee: Emmanuel Lecharny (was: Kiran Ayyagari)
All tests have been implemented.
> Implement tests for AttributeType additions in SchemaManager
> ------------------------------------------------------------
>
> Key: DIRSERVER-1426
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1426
> Project: Directory ApacheDS
> Issue Type: Test
> Components: schema
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Fix For: 2.0.0-RC1
>
>
> We need tests for the SchemaManager, in shared-ldap-schema-loader project :
> o AT with no superior
> - no syntax => error
> - Collective AT => USAGE = userApplications
> - NO-USER-MODIFICATION => operational AT
> - equalityOid must be valid
> - orderingOid must exist
> - substringOid must exist
> o AT with superior
> - no Syntax => take its superior syntax
> - Usage must be equals to its superior
> - if equality, ordering or substring are null, they must take its superior's value for
those MR
> - no cycle allowed (cannot be it's own superior)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRSERVER-1426.
----------------------------------------
Done
> Implement tests for AttributeType additions in SchemaManager
> ------------------------------------------------------------
>
> Key: DIRSERVER-1426
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1426
> Project: Directory ApacheDS
> Issue Type: Test
> Components: schema
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Fix For: 2.0.0-RC1
>
>
> We need tests for the SchemaManager, in shared-ldap-schema-loader project :
> o AT with no superior
> - no syntax => error
> - Collective AT => USAGE = userApplications
> - NO-USER-MODIFICATION => operational AT
> - equalityOid must be valid
> - orderingOid must exist
> - substringOid must exist
> o AT with superior
> - no Syntax => take its superior syntax
> - Usage must be equals to its superior
> - if equality, ordering or substring are null, they must take its superior's value for
those MR
> - no cycle allowed (cannot be it's own superior)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785409#action_12785409
]
Emmanuel Lecharny commented on DIRSERVER-1426:
----------------------------------------------
o AT with superior
- no Syntax => take its superior syntax : DONE
- Usage must be equals to its superior : DONE
- if equality, ordering or substring are null, they must take its superior's value for those
MR : DONE
> Implement tests for AttributeType additions in SchemaManager
> ------------------------------------------------------------
>
> Key: DIRSERVER-1426
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1426
> Project: Directory ApacheDS
> Issue Type: Test
> Components: schema
> Reporter: Emmanuel Lecharny
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> We need tests for the SchemaManager, in shared-ldap-schema-loader project :
> o AT with no superior
> - no syntax => error
> - Collective AT => USAGE = userApplications
> - NO-USER-MODIFICATION => operational AT
> - equalityOid must be valid
> - orderingOid must exist
> - substringOid must exist
> o AT with superior
> - no Syntax => take its superior syntax
> - Usage must be equals to its superior
> - if equality, ordering or substring are null, they must take its superior's value for
those MR
> - no cycle allowed (cannot be it's own superior)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785398#action_12785398
]
Emmanuel Lecharny commented on DIRSERVER-1426:
----------------------------------------------
o AT with no superior : All DONE
- no syntax => error : DONE
- Collective AT => USAGE = userApplications : DONE (2 tests, one positive, one negative)
- NO-USER-MODIFICATION => operational AT : DONE (2 tests, one positive, one negative)
- equalityOid must be valid : DONE
- orderingOid must exist : DONE
- substringOid must exist : DONE
- equality, ordering and substring, all valid : DONE
> Implement tests for AttributeType additions in SchemaManager
> ------------------------------------------------------------
>
> Key: DIRSERVER-1426
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1426
> Project: Directory ApacheDS
> Issue Type: Test
> Components: schema
> Reporter: Emmanuel Lecharny
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> We need tests for the SchemaManager, in shared-ldap-schema-loader project :
> o AT with no superior
> - no syntax => error
> - Collective AT => USAGE = userApplications
> - NO-USER-MODIFICATION => operational AT
> - equalityOid must be valid
> - orderingOid must exist
> - substringOid must exist
> o AT with superior
> - no Syntax => take its superior syntax
> - Usage must be equals to its superior
> - if equality, ordering or substring are null, they must take its superior's value for
those MR
> - no cycle allowed (cannot be it's own superior)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Np go 4 it! On Dec 3, 2009 11:08 AM, "Emmanuel LŽcharny" <elecharny@gmail.com> wrote: Pierre-Arnaud Marcelot a écrit : > > Hi all, > > I'd like to propose the removal of our specific per-plugin version to use the inher... no objection.
Pierre-Arnaud Marcelot a écrit : > Hi all, > > I'd like to propose the removal of our specific per-plugin version to use the inherited parent pom version instead. > > I'm talking about these properties defined in the parent pom of Studio: > ====================================================================== > <aciitemeditor.version>1.5.2-SNAPSHOT</aciitemeditor.version> > <apacheds.launcher.version>1.5.2-SNAPSHOT</apacheds.launcher.version> > <apacheds.version>1.5.2-SNAPSHOT</apacheds.version> > <apacheds.feature.version>1.5.2-SNAPSHOT</apacheds.feature.version> > <apacheds.help.version>1.5.2-SNAPSHOT</apacheds.help.version> > <apacheds.configuration.version>1.5.2-SNAPSHOT</apacheds.configuration.version> > <apacheds.configuration.feature.version>1.5.2-SNAPSHOT</apacheds.configuration.feature.version> > <apacheds.configuration.help.version>1.5.2-SNAPSHOT</apacheds.configuration.help.version> > <common.ui.version>1.5.2-SNAPSHOT</common.ui.version> > <connection.core.version>1.5.2-SNAPSHOT</connection.core.version> > <connection.ui.version>1.5.2-SNAPSHOT</connection.ui.version> > <jars.version>1.5.2-SNAPSHOT</jars.version> > <ldapbrowser.common.version>1.5.2-SNAPSHOT</ldapbrowser.common.version> > <ldapbrowser.core.version>1.5.2-SNAPSHOT</ldapbrowser.core.version> > <ldapbrowser.feature.version>1.5.2-SNAPSHOT</ldapbrowser.feature.version> > <ldapbrowser.help.version>1.5.2-SNAPSHOT</ldapbrowser.help.version> > <ldapbrowser.ui.version>1.5.2-SNAPSHOT</ldapbrowser.ui.version> > <ldifeditor.version>1.5.2-SNAPSHOT</ldifeditor.version> > <ldifeditor.feature.version>1.5.2-SNAPSHOT</ldifeditor.feature.version> > <ldifeditor.help.version>1.5.2-SNAPSHOT</ldifeditor.help.version> > <ldifparser.version>1.5.2-SNAPSHOT</ldifparser.version> > <rcp.version>1.5.2-SNAPSHOT</rcp.version> > <rcp.feature.version>1.5.2-SNAPSHOT</rcp.feature.version> > <rcp.help.version>1.5.2-SNAPSHOT</rcp.help.version> > <repository.version>1.5.2-SNAPSHOT</repository.version> > <schemaeditor.version>1.5.2-SNAPSHOT</schemaeditor.version> > <schemaeditor.feature.version>1.5.2-SNAPSHOT</schemaeditor.feature.version> > <schemaeditor.help.version>1.5.2-SNAPSHOT</schemaeditor.help.version> > <test.integration.core.version>1.5.2-SNAPSHOT</test.integration.core.version> > <test.integration.ui.version>1.5.2-SNAPSHOT</test.integration.ui.version> > <updatesite.version>1.5.2-SNAPSHOT</updatesite.version> > <valueeditors.version>1.5.2-SNAPSHOT</valueeditors.version> > ====================================================================== > > These properties have always been a source of annoyance because they're not very well handled by the release plugin (and sometimes, some of them are not replaced correctly) and I think they're not really necessary. > > Since we're releasing the project as a whole, I think each project needs to inherit the version defined in the parent pom. > > WDYT? > Any objection? > no objection.
Hi all,
I'd like to propose the removal of our specific per-plugin version to use the inherited parent
pom version instead.
I'm talking about these properties defined in the parent pom of Studio:
======================================================================
<aciitemeditor.version>1.5.2-SNAPSHOT</aciitemeditor.version>
<apacheds.launcher.version>1.5.2-SNAPSHOT</apacheds.launcher.version>
<apacheds.version>1.5.2-SNAPSHOT</apacheds.version>
<apacheds.feature.version>1.5.2-SNAPSHOT</apacheds.feature.version>
<apacheds.help.version>1.5.2-SNAPSHOT</apacheds.help.version>
<apacheds.configuration.version>1.5.2-SNAPSHOT</apacheds.configuration.version>
<apacheds.configuration.feature.version>1.5.2-SNAPSHOT</apacheds.configuration.feature.version>
<apacheds.configuration.help.version>1.5.2-SNAPSHOT</apacheds.configuration.help.version>
<common.ui.version>1.5.2-SNAPSHOT</common.ui.version>
<connection.core.version>1.5.2-SNAPSHOT</connection.core.version>
<connection.ui.version>1.5.2-SNAPSHOT</connection.ui.version>
<jars.version>1.5.2-SNAPSHOT</jars.version>
<ldapbrowser.common.version>1.5.2-SNAPSHOT</ldapbrowser.common.version>
<ldapbrowser.core.version>1.5.2-SNAPSHOT</ldapbrowser.core.version>
<ldapbrowser.feature.version>1.5.2-SNAPSHOT</ldapbrowser.feature.version>
<ldapbrowser.help.version>1.5.2-SNAPSHOT</ldapbrowser.help.version>
<ldapbrowser.ui.version>1.5.2-SNAPSHOT</ldapbrowser.ui.version>
<ldifeditor.version>1.5.2-SNAPSHOT</ldifeditor.version>
<ldifeditor.feature.version>1.5.2-SNAPSHOT</ldifeditor.feature.version>
<ldifeditor.help.version>1.5.2-SNAPSHOT</ldifeditor.help.version>
<ldifparser.version>1.5.2-SNAPSHOT</ldifparser.version>
<rcp.version>1.5.2-SNAPSHOT</rcp.version>
<rcp.feature.version>1.5.2-SNAPSHOT</rcp.feature.version>
<rcp.help.version>1.5.2-SNAPSHOT</rcp.help.version>
<repository.version>1.5.2-SNAPSHOT</repository.version>
<schemaeditor.version>1.5.2-SNAPSHOT</schemaeditor.version>
<schemaeditor.feature.version>1.5.2-SNAPSHOT</schemaeditor.feature.version>
<schemaeditor.help.version>1.5.2-SNAPSHOT</schemaeditor.help.version>
<test.integration.core.version>1.5.2-SNAPSHOT</test.integration.core.version>
<test.integration.ui.version>1.5.2-SNAPSHOT</test.integration.ui.version>
<updatesite.version>1.5.2-SNAPSHOT</updatesite.version>
<valueeditors.version>1.5.2-SNAPSHOT</valueeditors.version>
======================================================================
These properties have always been a source of annoyance because they're not very well handled
by the release plugin (and sometimes, some of them are not replaced correctly) and I think
they're not really necessary.
Since we're releasing the project as a whole, I think each project needs to inherit the version
defined in the parent pom.
WDYT?
Any objection?
Thanks,
Pierre-Arnaud
Unable to start an Apache DS version 1.5.5 server
-------------------------------------------------
Key: DIRSTUDIO-602
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-602
Project: Directory Studio
Issue Type: Bug
Components: studio-apacheds
Affects Versions: 1.5.1
Reporter: Pierre-Arnaud Marcelot
Assignee: Pierre-Arnaud Marcelot
Priority: Blocker
Fix For: 1.5.2
Unable to start an Apache DS version 1.5.5 server.
NPE when copying that damn apacheds-launcher library...
!ENTRY org.eclipse.ui 4 0 2009-12-03 16:32:33.271
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at org.apache.directory.studio.apacheds.ApacheDsPluginUtils.copyLibrary(ApacheDsPluginUtils.java:224)
at org.apache.directory.studio.apacheds.ApacheDsPluginUtils.verifyLibrariesFolder(ApacheDsPluginUtils.java:99)
at org.apache.directory.studio.apacheds.actions.RunAction.run(RunAction.java:173)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1598)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1622)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1607)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1396)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3484)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3068)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.apache.directory.studio.Application.start(Application.java:58)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/DIRSERVER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785334#action_12785334
]
Emmanuel Lecharny commented on DIRSERVER-1426:
----------------------------------------------
We need some other tests :
- addition of an AT without associated schema
- addition of an AT with an already existing OID
> Implement tests for AttributeType additions in SchemaManager
> ------------------------------------------------------------
>
> Key: DIRSERVER-1426
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1426
> Project: Directory ApacheDS
> Issue Type: Test
> Components: schema
> Reporter: Emmanuel Lecharny
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> We need tests for the SchemaManager, in shared-ldap-schema-loader project :
> o AT with no superior
> - no syntax => error
> - Collective AT => USAGE = userApplications
> - NO-USER-MODIFICATION => operational AT
> - equalityOid must be valid
> - orderingOid must exist
> - substringOid must exist
> o AT with superior
> - no Syntax => take its superior syntax
> - Usage must be equals to its superior
> - if equality, ordering or substring are null, they must take its superior's value for
those MR
> - no cycle allowed (cannot be it's own superior)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.