SVN Portlet configuration

[melpelotones]

Hi again,

Now I am configuring the subversion plugin, after reading
the reference manual I have seen that is possible to access to
secure subversion repositories.

I am accessing to my repository in this way:

portlet.xml


<portlet-name>ONESvnMonitoringPortlet</portlet-name>
<portlet-class>hu.midori.kosmos.portlet.svn.SvnMonitoringPortlet</portlet-class>
<init-param>
monitored.resource
ONE Subversion
</init-param>
<init-param>
service.url
http://localhost:8091/kosmos-server/kosmos-services/svn-service
</init-param>
<init-param>
monitored.urls

svn+ssh://myserver/home/myproject/svn_repo

</init-param>

<mime-type>text/html</mime-type>
<portlet-mode>HELP</portlet-mode>
<portlet-mode>VIEW</portlet-mode>

<supported-locale>en</supported-locale>
<supported-locale>fr</supported-locale>
<resource-bundle>hu.midori.kosmos.portlet.svn.svn_monitoring</resource-bundle>
<portlet-info>

</portlet-info>



and I am having this error

[INFO] SvnMonitoringPortlet - Initializing...
[INFO] SvnMonitoringPortlet - Viewing...
[INFO] MethodResultCacheInterceptor - Cache-miss: reloading "hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://myserver/home/myproject/svn_repo"...
[ERROR] SvnServiceImpl - Unable to process the SVN repo <java.net.MalformedURLException: unknown protocol: svn+ssh>java.net.MalformedURLException: unknown protocol: svn+ssh


Can i Use svn+ssh?
in case of being possible, how can I put the login/password in the request?

Thank you in advance,

Best Regards,

[aron.gombas]

Can i Use svn+ssh?

Yes, you should be able to use "svn+ssh", as javasvn supports it.
Can you set the logging level to DEBUG and send me that log to see which line throws the exception?

n case of being possible, how can I put the login/password in the request?

See our FAQ:

# Does Kosmos support secure Subversion repositories?

Yes. You just have to encode your credentials to the URL specified in monitored.urls: http://myusername:[e-mail]/svn/mysecurerepo

[melpelotones]

Hi, I think I solved the thing with the URL, but now, the SVN portlet
is not displaying anything.Here are the Debug Logs

I have made some chekouts-commits in the svn repository but it is
not reflected in the portlet

DEBUG http-8091-Processor25 hu.midori.kosmos.server.AbstractKosmosService - Ending store session...
DEBUG http-8091-Processor25 net.sf.ehcache.Cache - hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://user:ONE@192.168.1.14/home/ONE/svn_repo/trunks now: 1152784491467
DEBUG http-8091-Processor25 net.sf.ehcache.Cache - hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://ONE:ONE@192.168.1.14/home/ONE/svn_repo/trunks Creation Time: 1152784491467 Next To Last Access Time: 0
DEBUG http-8091-Processor25 net.sf.ehcache.Cache - hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://ONE:ONE@192.168.1.14/home/ONE/svn_repo/trunks mostRecentTime: 1152784491467
DEBUG http-8091-Processor25 net.sf.ehcache.Cache - hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://ONE:ONE@192.168.1.14/home/ONE/svn_repo/trunks Age to Idle: 14400000 Age Idled: 0
DEBUG http-8091-Processor25 net.sf.ehcache.Cache - hu.midori.kosmos.server.cache: Is element with key hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://ONE:ONE@192.168.1.14/home/ONE/svn_repo/trunks expired?: false
DEBUG http-8091-Processor25 hu.midori.kosmos.server.MethodResultCacheInterceptor - "hu.midori.kosmos.server.svn.SvnServiceImpl.getRepositories.svn+ssh://ONE:ONE@192.168.1.14/home/ONE/svn_repo/trunks" saved to cache
DEBUG http-8091-Processor25 org.springframework.remoting.support.RemoteInvocationTraceInterceptor - Finished processing of HessianServiceExporter remote call: hu.midori.kosmos.protocol.SvnService.getRepositories
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Null ModelAndView returned to DispatcherServlet with name 'kosmos-services': assuming HandlerAdapter completed request handling
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Cleared thread-bound request context: org.apache.coyote.tomcat5.CoyoteRequestFacade@6276e5
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Successfully completed request
DEBUG http-8091-Processor25 org.springframework.web.context.support.XmlWebApplicationContext - Publishing event in context [WebApplicationContext for namespace 'kosmos-services-servlet']: ServletRequestHandledEvent: url=[/kosmos-server/kosmos-services/svn-service]; client=[127.0.0.1]; method=[POST]; servlet=[kosmos-services]; session=[null]; user=[null]; time=[124ms]; status=[OK]
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - DispatcherServlet with name 'kosmos-services' received request for [/kosmos-server/kosmos-services/svn-service]
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Bound request context to thread: org.apache.coyote.tomcat5.CoyoteRequestFacade@6276e5
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Testing handler map [org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping@6be4cc] in DispatcherServlet with name 'kosmos-services'
DEBUG http-8091-Processor25 org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping - Looking up handler for [/svn-service]
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Testing handler adapter [org.springframework.web.servlet.mvc.SimpleHandlerAdapter@17a1686]
DEBUG http-8091-Processor25 org.springframework.remoting.support.RemoteInvocationTraceInterceptor - Incoming HessianServiceExporter remote call: hu.midori.kosmos.protocol.TimestampedService.getTimestamp
DEBUG http-8091-Processor25 org.springframework.aop.support.JdkRegexpMethodPointcut - Candidate is [hu.midori.kosmos.protocol.TimestampedService.getTimestamp]; pattern is [hu.midori.kosmos.protocol.CcService.getProjects]; matched=false
DEBUG http-8091-Processor25 org.springframework.aop.support.JdkRegexpMethodPointcut - Candidate is [hu.midori.kosmos.protocol.TimestampedService.getTimestamp]; pattern is [hu.midori.kosmos.protocol.JiraService.getProjects]; matched=false
DEBUG http-8091-Processor25 org.springframework.aop.support.JdkRegexpMethodPointcut - Candidate is [hu.midori.kosmos.protocol.TimestampedService.getTimestamp]; pattern is [hu.midori.kosmos.protocol.SfService.getFileReleases]; matched=false
DEBUG http-8091-Processor25 org.springframework.aop.support.JdkRegexpMethodPointcut - Candidate is [hu.midori.kosmos.protocol.TimestampedService.getTimestamp]; pattern is [hu.midori.kosmos.protocol.SvnService.getRepositories]; matched=false
DEBUG http-8091-Processor25 hu.midori.kosmos.server.AbstractKosmosService - Service invoked: returning timestamp...
DEBUG http-8091-Processor25 org.springframework.remoting.support.RemoteInvocationTraceInterceptor - Finished processing of HessianServiceExporter remote call: hu.midori.kosmos.protocol.TimestampedService.getTimestamp
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Null ModelAndView returned to DispatcherServlet with name 'kosmos-services': assuming HandlerAdapter completed request handling
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Cleared thread-bound request context: org.apache.coyote.tomcat5.CoyoteRequestFacade@6276e5
DEBUG http-8091-Processor25 org.springframework.web.servlet.DispatcherServlet - Successfully completed request
DEBUG http-8091-Processor25 org.springframework.web.context.support.XmlWebApplicationContext - Publishing event in context [WebApplicationContext for namespace 'kosmos-services-servlet']: ServletRequestHandledEvent: url=[/kosmos-server/kosmos-services/svn-service]; client=[127.0.0.1]; method=[POST]; servlet=[kosmos-services]; session=[null]; user=[null]; time=[1ms]; status=[OK]

[aron.gombas]

This seems correct to me (however it would be more interesting a longer log).
Have you tried to restart your servlet container after changing your settings?