Forum Ametys

I got the plugin.xml file up and running and the service showed up and is rendering the html file that I declared in my file generator in the xmap file. But I am having some issues with the routing of resource requests (js, css, img files) via my xmap file.

I have a reader defined and I am matching appropriate url's, as defined in the html file I am reading through, but I am getting a "No pipeline matched request: ..." error for my JS and CSS files.

If I am reading the error correctly, it is not looking in my defined sitemap.xmap file, but instead it is reading "resource://org/ametys/runtime/kernel/sitemap.xmap" this it would not finding the <map:match> with a matching pattern I defined in my xmap file.

Is there something I am missing here? It seems like the request isn't being completely handled by the cocoon pipeline I defined for my service.

I noticed that the existing services distributed with Ametys are all located in the $CATALINA_HOME/webapps/cms/WEB-INF/lib folder as a pair of jar files, one with the service java classes, cocoon pipeline xmap file, plugin.xml file, etc.; the other with various resources, images, css files, js files, etc.

I have tried to create a proof of concept service following this template with no success. I followed the layout of the google maps plugin.

I created a plugin.xml file that I believe has the minimum requirements filled out:

<?xml version="1.0" encoding="UTF-8" ?>

<plugin xmlns="http://www.ametys.org/schema/plugin"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.ametys.org/schema/plugin http://www.ametys.org/schema/plugin-2.0.xsd"
        runtimeVersion="2.0" version="2.0">
    
    <extension point="org.ametys.web.service.ServiceExtensionPoint"
        class="org.ametys.web.service.StaticService"
        id="org.ametys.plugins.spreadsheet.Spreadsheet">
 
        <url>service/spreadsheet/spreadsheet.xhtml</url>
 
        <label>PLUGINS_SPREADSHEET_SERVICE_LABEL</label>
        <description>PLUGINS_SPREADSHEET_SERVICE_DESCRIPTION</description>
 
    </extension>
    
</plugin>

I am unsure what to put into the id attribute of the extension tag and I am unsure what to put into the label and description tags. It looks like the existing services use place holders that get replaced somehow but I am not sure.

I also created a cocoon pipeline with a <map:match> who's pattern matches the url from the plugin.xml file. The pipeline is very simple for proof of concept purposes. It is the default file generator with src pointing to a xhtml file with some static html on it, and the cocoon xhtml serializer, I got the declaration from the Apache Cocoon website.

I packed up these files into a jar file and put them into the $CATALINA_HOME/webapps/cms/WEB-INF/lib folder. Then I restarted Ametys and, not too surprisingly the service didn't show up. I then restarted Tomcat and the service didn't show up. What am I missing?

I have tried it on both up-to-date Firefox (v 24.0) and Chromium (v 28.0.1500.71). On both of these browsers I get the warning page that the browser is not supported though.

The demo works for both of them just fine. But my page was getting stuck on 0% on the loading page after the user login.

I have checked the log files for Tomcat and found nothing, just the list of previous successful GET requests.
I checked the log files for Ametys CMS and there was nothing listed there.
When I looked at the requests on Firebug the request was just sitting there waiting for the server but the server didn't seem to get the request at all.

But after 20 minutes or so of restarting and re-testing and deleting/re-checking the log files it started to work. I have no idea what make the difference that got it to work because I didn't do anything afterwards that I didn't also do before I created this thread. But the CMS is in fact working without any errors now.

I did discover that I should have been using on some of the scripts, the jdbc_users_auth.sql and the jdbc_fousers_auth.sql so long as I am not doing 3rd party authorization, the sql scripts differ from their non "_auth.sql" counterparts by just the 'password' field.

I dropped the 'Users' and the 'FOUsers' tables and ran the "_auth.sql" versions of the two scripts and it solved my problem. I am currently not having any issues with the CMS.

Thank you for the help and I will not hesitate to post on here again if I run into more problems.