[
https://issues.apache.org/jira/browse/DIRSERVER-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981367#action_12981367
]
Chris Council edited comment on DIRSERVER-1598 at 1/13/11 12:01 PM:
--------------------------------------------------------------------
Running 'mvn jetty:run' with apacheds-all 1.5.7, I get the exception
Caused by: java.io.FileNotFoundException: ERR_10004 Expecting to find a
schema.ldif file in provided baseDirectory path
'/y/apacheds-embedded/ApacheDS/target/work/server-work/schema/ou=schema.ldif'
but no such file found.
at
org.apache.directory.shared.ldap.schema.loader.ldif.LdifSchemaLoader.<init>(LdifSchemaLoader.java:113)
at org.example.StartStopListener.initSchema(StartStopListener.java:150)
at
org.example.StartStopListener.contextInitialized(StartStopListener.java:89)
... 41 more
2011-01-13 09:57:23.681::INFO: Started [email protected]:8090
[INFO] Started Jetty Server
...which I believe is a known issue when running in a container (fixed in
1.5.8-SNAPSHOT?). When I extract the schema files from apacheds-all and stick
them in /y/apacheds-embedded/ApacheDS/target/work/server-work/schema/ (as a
workaround), I get further, but I still get an ERR_04450:
2011-01-13 09:59:36.533::INFO: jetty-6.1.21
2011-01-13 09:59:36.798::INFO: No Transaction manager found - if your webapp
requires one, please configure one.
schema partition directory exists, skipping schema extraction
[09:59:51] ERROR
[org.apache.directory.shared.ldap.entry.DefaultServerAttribute] - ERR_04450 The
value {0} is incorrect, it hasnt been added
was (Author: chriscouncil):
Running 'mvn jetty:run' with apacheds-all 1.5.7, I get the exception
Caused by: java.io.FileNotFoundException: ERR_10004 Expecting to find a
schema.ldif file in provided baseDirectory path
'/y/apacheds-embedded/ApacheDS/target/work/server-work/schema/ou=schema.ldif'
but no such file found.
at
org.apache.directory.shared.ldap.schema.loader.ldif.LdifSchemaLoader.<init>(LdifSchemaLoader.java:113)
at org.example.StartStopListener.initSchema(StartStopListener.java:150)
at
org.example.StartStopListener.contextInitialized(StartStopListener.java:89)
... 41 more
2011-01-13 09:57:23.681::INFO: Started [email protected]:8090
[INFO] Started Jetty Server
...which I believe is a known issue. When I extract the schema files from
apacheds-all and stick them in
/y/apacheds-embedded/ApacheDS/target/work/server-work/schema/ (as a
workaround), I get this error:
2011-01-13 09:59:36.533::INFO: jetty-6.1.21
2011-01-13 09:59:36.798::INFO: No Transaction manager found - if your webapp
requires one, please configure one.
schema partition directory exists, skipping schema extraction
[09:59:51] ERROR
[org.apache.directory.shared.ldap.entry.DefaultServerAttribute] - ERR_04450 The
value {0} is incorrect, it hasnt been added
> Code referenced in "Embedding ApacheDS as a Web Application" doesn't compile
> with apacheds-all 1.5.8-SNAPSHOT
> -------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1598
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1598
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Chris Council
>
> The code referenced from
> http://directory.apache.org/apacheds/1.5/43-embedding-apacheds-as-a-web-application.html
> doesn't compile with apacheds-all 1.5.8-SNAPSHOT and it doesn't seem to work
> with apacheds-all 1.5.7.
> This also applies to a project created using the instructions provided in the
> "Creating the WebApp using the ApacheDS Maven Archetype" section on that same
> page.
> Specifically, there is no longer a "setWorkingDirectory" method in
> org.apache.directory.server.core.DefaultDirectoryService. I'm not sure
> exactly how to solve this issue, it's not immediately obvious what the
> replacement method is.
> Also, it was rather difficult to get apacheds-all 1.5.8-SNAPSHOT in the first
> place - after some time, I finally determined that it was available from
> http://repository.apache.org/ (I think). It would be nice to have this
> information on that page as well. Still, I had to grab the artifact manually
> and install it in a local maven repo, since it didn't seem to download from
> the http://repository.apache.org/ repo correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
