[jira] [Created] (CONNECTORS-564) Velocity is apparently trying to write to velocity.log, which is not correct

2012-11-06 Thread Karl Wright (JIRA) 
Karl Wright created CONNECTORS-564:
--

 Summary: Velocity is apparently trying to write to velocity.log, 
which is not correct
 Key: CONNECTORS-564
 URL: https://issues.apache.org/jira/browse/CONNECTORS-564
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework core
Affects Versions: ManifoldCF 1.0.1, ManifoldCF 1.0, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
 Fix For: ManifoldCF 1.1


When running under tomcat, Velocity apparently tries to create a velocity.log 
file under the current working directory, and does NOT use the ManifoldCF 
logging.ini file.  Here's the stack trace.

{code}
HTTP Status 500 -
type Exception report

message

description The server encountered an internal error () that prevented it from 
fulfilling this request.

exception

org.apache.jasper.JasperException: org.apache.jasper.JasperException: 
java.lang.RuntimeException: Velocity could not be initialized!
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:491)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:401)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
root cause

org.apache.jasper.JasperException: java.lang.RuntimeException: Velocity could 
not be initialized!
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:491)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:419)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
org.apache.jsp.execute_jsp._jspService(execute_jsp.java:548)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
root cause

java.lang.RuntimeException: Velocity could not be initialized!
org.apache.velocity.runtime.RuntimeInstance.requireInitialization(RuntimeInstance.java:307)
org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1531)
org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:343)
org.apache.manifoldcf.ui.i18n.Messages.outputResourceWithVelocity(Messages.java:158)
org.apache.manifoldcf.authorities.authorities.activedirectory.Messages.outputResourceWithVelocity(Messages.java:136)
org.apache.manifoldcf.authorities.authorities.activedirectory.ActiveDirectoryAuthority.outputConfigurationHeader(ActiveDirectoryAuthority.java:467)
org.apache.manifoldcf.authorities.interfaces.AuthorityConnectorFactory.outputConfigurationHeader(AuthorityConnectorFactory.java:78)
org.apache.jsp.editauthority_jsp._jspService(editauthority_jsp.java:434)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
org.apache.jsp.execute_jsp._jspService(execute_jsp.java:548)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
root cause

org.apache.velocity.exception.VelocityException: Error initializing log: Failed 
to initialize an instance of org.apache.velocity.runtime.log.Log4JLogChute with 
the current runtime configuration.
org.apache.velocity.runtime.RuntimeInstance.initializeLog(RuntimeInstance.java:875)
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:262)
org.apache.velocity.runtime.RuntimeInstance.requireInitialization(RuntimeInstance.java:302)

[jira] [Commented] (CONNECTORS-562) Some web.xml files contain wrong declarations

2012-11-06 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/CONNECTORS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491361#comment-13491361
 ] 

Erlend Garåsen commented on CONNECTORS-562:
---

Resin does not seem to complain about the changes. I also tried to run the 
integration tests for the Alfresco connector since it was affected by your 
changes. I will commit your contribution later this week since I (yet) haven't 
spent too much time on this issue. Just to be sure. :)

 Some web.xml files contain wrong declarations
 -

 Key: CONNECTORS-562
 URL: https://issues.apache.org/jira/browse/CONNECTORS-562
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF next
 Environment: Project was imported into Eclipse Juno
Reporter: Alex Ott
Assignee: Erlend Garåsen
Priority: Trivial
  Labels: patch
 Fix For: ManifoldCF next

 Attachments: mcf-fix-web.xml-errors.diff


 I'm trying to setup development environment for ManifoldCF + Eclipse, and 
 found that number of web.xml files contain wrong/outdated declarations and 
 Eclipse reports errors for them. Attached patch fixes this issue

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-563) Extended LDAP authority connector

2012-11-06 Thread Maciej Lizewski (JIRA) 

[ 
https://issues.apache.org/jira/browse/CONNECTORS-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491593#comment-13491593
 ] 

Maciej Lizewski commented on CONNECTORS-563:


Changelog updated

 Extended LDAP authority connector
 -

 Key: CONNECTORS-563
 URL: https://issues.apache.org/jira/browse/CONNECTORS-563
 Project: ManifoldCF
  Issue Type: Improvement
  Components: LDAP authority
Reporter: Maciej Lizewski

 1. possibility to include username in authority tokens (because tokens are 
 mapped to filesystem privileges there may be per-group rights or per-user 
 right assigned to documents, so it is necessary to check for user permissions 
 also)
 2. possibility to search groups by user name or user DN (there are two usage 
 scenarios involving GroupOfNames/UniqueGroupOfNames and PosixGroups. First 
 one needs to search by DN, the other by user name/uid)
 3. allow binding to LDAP server with specified credentials

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira