Is the OOo conversion service running?

Try adding a new logger for the o.s.n.preview package and turning it up.

Erik

On Mon, Sep 10, 2012 at 4:53 PM, Harry Wang <harryjw...@gmail.com> wrote:
> Thanks, Erik. After pulling in your commit and rebuild, I installed the jar 
> via system console and started the bundle successfully (shown as Active). Are 
> there any other steps I am supposed to do? I uploaded a PDF and a DOCX but 
> the previews of those files did not show up.
>
> Any idea?
>
> Harry
>
> On Sep 10, 2012, at 4:02 PM, Erik Froese wrote:
>
>> Hey Harry,
>>
>> Sorry I didn't get back to you earlier. I just pushed a commit to fix
>> that issue.
>>
>> https://github.com/efroese/nakamura/commit/fdc91d6c501a71eec71763c55253e76758095fd9
>>
>> Erik
>>
>>
>>
>> On Mon, Sep 10, 2012 at 2:53 PM, Harry Wang <hjw...@udel.edu> wrote:
>>> I want to keep the mailing list in the loop.
>>>
>>> Any help? Erik?
>>>
>>> Thanks,
>>>
>>> Harry
>>>
>>> On Sep 8, 2012, at 10:14 PM, Harry Wang wrote:
>>>
>>> Thanks, Erik. After building termextract, I was able to build processor
>>> successfully.
>>>
>>> I tried to use system console to install the jars (we already have nakamura
>>> running and I installed termextract jar first without problems but cannot
>>> start preview jar given some missing packages as shown below:
>>>
>>> Our nakamura was built from latest master branch.  I think the two required
>>> packages are org.hyperic.sigar and
>>> org.hyperic.sigar.ptql
>>>
>>> Any idea on how to fix this?
>>>
>>> Harry
>>>
>>> com.google.common.collect from com.google.guava (44)
>>> com.ibm.icu.text -- Cannot be resolved but is not required
>>> groovy.lang from groovy-all (8)
>>> javax.crypto from org.apache.felix.framework (0)
>>> javax.crypto.spec from org.apache.felix.framework (0)
>>> javax.imageio from org.apache.felix.framework (0)
>>> javax.imageio.metadata from org.apache.felix.framework (0)
>>> javax.imageio.plugins.jpeg from org.apache.felix.framework (0)
>>> javax.imageio.stream from org.apache.felix.framework (0)
>>> javax.net from org.apache.felix.framework (0)
>>> javax.net.ssl from org.apache.felix.framework (0)
>>> javax.print from org.apache.felix.framework (0)
>>> javax.print.attribute.standard from org.apache.felix.framework (0)
>>> javax.swing from org.apache.felix.framework (0)
>>> javax.swing.border from org.apache.felix.framework (0)
>>> javax.swing.event from org.apache.felix.framework (0)
>>> javax.swing.filechooser from org.apache.felix.framework (0)
>>> javax.swing.tree from org.apache.felix.framework (0)
>>> javax.xml.parsers from org.apache.felix.framework (0)
>>> javax.xml.transform from org.apache.felix.framework (0)
>>> junit.framework -- Cannot be resolved but is not required
>>> nu.xom -- Cannot be resolved but is not required
>>> org.apache.commons.cli,version=1.2 -- Cannot be resolved but is not required
>>> org.apache.commons.collections.comparators,version=3.2 from
>>> org.apache.commons.collections (2)
>>> org.apache.commons.collections.keyvalue,version=3.2 from
>>> org.apache.commons.collections (2)
>>> org.apache.commons.collections.list,version=3.2 from
>>> org.apache.commons.collections (2)
>>> org.apache.commons.collections.map,version=3.2 from
>>> org.apache.commons.collections (2)
>>> org.apache.commons.collections.set,version=3.2 from
>>> org.apache.commons.collections (2)
>>> org.apache.commons.httpclient from
>>> org.apache.servicemix.bundles.commons-httpclient (61)
>>> org.apache.commons.httpclient.auth from
>>> org.apache.servicemix.bundles.commons-httpclient (61)
>>> org.apache.commons.httpclient.methods from
>>> org.apache.servicemix.bundles.commons-httpclient (61)
>>> org.apache.commons.httpclient.methods.multipart from
>>> org.apache.servicemix.bundles.commons-httpclient (61)
>>> org.apache.commons.httpclient.params from
>>> org.apache.servicemix.bundles.commons-httpclient (61)
>>> org.apache.commons.httpclient.protocol from
>>> org.apache.servicemix.bundles.commons-httpclient (61)
>>> org.apache.commons.io,version=1.4 from org.apache.commons.io (5)
>>> org.apache.commons.lang,version=2.6 from org.apache.commons.lang (6)
>>> org.apache.commons.lang.builder,version=2.6 from org.apache.commons.lang (6)
>>> org.apache.commons.lang.exception,version=2.6 from org.apache.commons.lang
>>> (6)
>>> org.apache.commons.lang.math,version=2.6 from org.apache.commons.lang (6)
>>> org.apache.commons.logging from jcl.over.slf4j (47)
>>> org.apache.jempbox.xmp,version=1.6 -- Cannot be resolved but is not required
>>> org.apache.oro.text.regex -- Cannot be resolved but is not required
>>> org.apache.sling.commons.osgi,version=2.1 from org.apache.sling.commons.osgi
>>> (20)
>>> org.apache.sling.commons.scheduler,version=2.1 from
>>> org.apache.sling.commons.scheduler (21)
>>> org.apache.tika,version=1.0 from org.sakaiproject.nakamura.tika (93)
>>> org.apache.tika.metadata,version=1.0 from org.sakaiproject.nakamura.tika
>>> (93)
>>> org.apache.tika.parser,version=1.0 from org.sakaiproject.nakamura.tika (93)
>>> org.apache.tika.sax,version=1.0 from org.sakaiproject.nakamura.tika (93)
>>> org.apache.velocity from org.sakaiproject.nakamura.templates (92)
>>> org.apache.velocity.app from org.sakaiproject.nakamura.templates (92)
>>> org.apache.velocity.context from org.sakaiproject.nakamura.templates (92)
>>> org.apache.velocity.runtime.resource.loader from
>>> org.sakaiproject.nakamura.templates (92)
>>> org.bouncycastle.asn1 -- Cannot be resolved but is not required
>>> org.bouncycastle.asn1.cms -- Cannot be resolved but is not required
>>> org.bouncycastle.asn1.pkcs -- Cannot be resolved but is not required
>>> org.bouncycastle.asn1.x509 -- Cannot be resolved but is not required
>>> org.bouncycastle.cms -- Cannot be resolved but is not required
>>> org.bouncycastle.jce.provider -- Cannot be resolved but is not required
>>> org.codehaus.groovy.reflection from groovy-all (8)
>>> org.codehaus.groovy.runtime from groovy-all (8)
>>> org.codehaus.groovy.runtime.callsite from groovy-all (8)
>>> org.codehaus.groovy.runtime.typehandling from groovy-all (8)
>>> org.codehaus.groovy.runtime.wrappers from groovy-all (8)
>>> org.hyperic.sigar -- Cannot be resolved
>>> org.hyperic.sigar.ptql -- Cannot be resolved
>>> org.json from org.sakaiproject.nakamura.org.json (141)
>>> org.sakaiproject.nakamura.api.termextract from
>>> org.sakaiproject.nakamura.termextract (144)
>>> org.sakaiproject.nakamura.termextract from
>>> org.sakaiproject.nakamura.termextract (144)
>>> org.slf4j,version=1.6 from slf4j.api (55)
>>> org.w3c.dom from org.apache.felix.framework (0)
>>> org.xml.sax from org.apache.felix.framework (0)
>>>
>>>
>>> On Sep 8, 2012, at 9:36 PM, Erik Froese wrote:
>>>
>>> you need to build the termextract bundle. I'll add it to the instructions
>>> when I get home.
>>>
>>> mvn install -f bundles/termextract/pom.xml
>>>
>>> Erik
>>>
>>> On Saturday, September 8, 2012, Harry Wang wrote:
>>>>
>>>> Hi Erik,
>>>>
>>>> When I tried to build the java preview processor using mvn install -f
>>>> bundles/preview/pom.xml, I ran into the following error.
>>>>
>>>> Any idea? Thanks for your help.
>>>>
>>>> Harry
>>>>
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 7.033s
>>>> [INFO] Finished at: Sat Sep 08 10:30:05 EDT 2012
>>>> [INFO] Final Memory: 8M/81M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal on project
>>>> org.sakaiproject.nakamura.preview: Could not resolve dependencies for
>>>> project
>>>> org.sakaiproject.nakamura:org.sakaiproject.nakamura.preview:bundle:1.5.0-SNAPSHOT:
>>>> Could not find artifact
>>>> org.sakaiproject.nakamura:org.sakaiproject.nakamura.termextract:jar:1.5.0-SNAPSHOT
>>>> in xwiki (http://maven.xwiki.org/externals//) -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>>> -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [ERROR]
>>>> [ERROR] For more information about the errors and possible solutions,
>>>> please read the following articles:
>>>> [ERROR] [Help 1]
>>>> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>>>>
>>>>
>>>>
>>>> On Aug 17, 2012, at 9:59 AM, Erik Froese wrote:
>>>>
>>>>> I wrote up how to run the Java PP as a OSGi service and a standalone
>>>>> jar.
>>>>> Let me know if you need anything to get it up and running.
>>>>>
>>>>>
>>>>> https://confluence.sakaiproject.org/display/KERNDOC/Using+the+Java+Preview+Processor
>>>>>
>>>>> Erik
>>>>>
>>>>> On Mon, Aug 13, 2012 at 11:53 AM, Erik Froese <erik.fro...@gmail.com>
>>>>> wrote:
>>>>>> We have a spring planning meeting at rSmart today. I'll put it on the
>>>>>> agenda for my work.
>>>>>>
>>>>>> I'm going on vacation 8/24 - 9/4 though so we'll have to work it out
>>>>>> before then.
>>>>>>
>>>>>> Erik
>>>>>>
>>>>>> On Mon, Aug 13, 2012 at 11:36 AM, Nicolaas Matthijs
>>>>>> <nicolaas.matth...@caret.cam.ac.uk> wrote:
>>>>>>> Hi Erik,
>>>>>>>
>>>>>>> How about trying to turn this work into an official sprint deliverable
>>>>>>> (co-ordinated with Kent)? Do you think you can free up some time for
>>>>>>> the
>>>>>>> next sprint (August 16 - August 30) and will that give us enough time
>>>>>>> to do
>>>>>>> remaining implementation, some testing and bug fixing?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Nicolaas
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 25 Jul 2012, at 00:18, Erik Froese wrote:
>>>>>>>
>>>>>>>> I'm happy to let the Java PP testing slide to 1.5.0
>>>>>>>>
>>>>>>>> There are some recent improvements in the ruby PP that I need to
>>>>>>>> implement.
>>>>>>>> * sakaidocs - (easy, call out to wkhtmltopdf)
>>>>>>>> * image previews in the same format as the original
>>>>>>>>
>>>>>>>> Erik
>>>>>>>>
>>>>>>>> On Tue, Jul 24, 2012 at 10:18 AM, Kent Fitzgerald
>>>>>>>> <kentf...@umich.edu>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Several questions/comments.
>>>>>>>>> There has already been  1.4.1. release proposed for immediately
>>>>>>>>> following
>>>>>>>>> 1.4.0 that would be isolated to code reformatting . Which would take
>>>>>>>>> precedence?
>>>>>>>>>
>>>>>>>>> We should definitely do a bug bash. One of the dangers of doing a
>>>>>>>>> bug
>>>>>>>>> bash
>>>>>>>>> focused on the preview processor is that we'll likely have people
>>>>>>>>> uploading
>>>>>>>>> hundreds of files each. Subjectively, this could give the impression
>>>>>>>>> of
>>>>>>>>> decreased performance just because we're hitting it much harder.
>>>>>>>>>
>>>>>>>>> More importantly, in addition to the bug bash, we need to do
>>>>>>>>> controlled
>>>>>>>>> tests on processing time on different data types. I'd like to break
>>>>>>>>> it
>>>>>>>>> down
>>>>>>>>> by file types and have truly controlled tests, in addition to
>>>>>>>>> different
>>>>>>>>> file
>>>>>>>>> types we'll need files of varying  sizes to compare performance not
>>>>>>>>> just
>>>>>>>>> on
>>>>>>>>> quantity but on complexity. This needs to be compared to the
>>>>>>>>> performance
>>>>>>>>> of
>>>>>>>>> the current implementation.
>>>>>>>>>
>>>>>>>>> I think we all agree that this is an important feature that we
>>>>>>>>> shouldn't
>>>>>>>>> try
>>>>>>>>> to rush out the door.
>>>>>>>>>
>>>>>>>>> I have to read back through the thread, but is there set-up
>>>>>>>>> documentation?
>>>>>>>>> Currently we have a section on the OAE Configuration and Deployment
>>>>>>>>> page
>>>>>>>>> [1]
>>>>>>>>> for the preview processor. It's contains multiple supporting
>>>>>>>>> external
>>>>>>>>> links
>>>>>>>>> that have proven confusing for many people trying to get preview
>>>>>>>>> processor
>>>>>>>>> running locally. We'll need to make sure we have adequate
>>>>>>>>> documentation.
>>>>>>>>>
>>>>>>>>> As a side note, I will be out of the office starting this Friday
>>>>>>>>> through
>>>>>>>>> next week.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>>
>>>
>>>
>>>
>> _______________________________________________
>> oae-dev mailing list
>> oae-dev@collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to