ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OFBIZ-9198) Missing file results in error
Date Sat, 04 Feb 2017 12:33:52 GMT

     [ https://issues.apache.org/jira/browse/OFBIZ-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jacques Le Roux resolved OFBIZ-9198.
       Resolution: Fixed
    Fix Version/s: 16.11.02
                   Upcoming Release

Thankd for report Ingo

I resolved the issue in 
trunk r1781662  
R16.11 and R15.12 r1781664 
Other branches don't contain ecomseo

I was unable to load your data, got this error
bq. ERROR: parsing file: ERROR parsing Entity Xml file: org.xml.sax.SAXException: A transaction
error occurred reading data<br/>org.xml.sax.SAXException: Fatal Error reading XML on
line 2, column 2<br/>org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 2;
The markup in the document following the root element must be well-formed.
and did not look further.

Please check if the fix is OK with you and close if you agree

> Missing file results in error
> -----------------------------
>                 Key: OFBIZ-9198
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9198
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: specialpurpose/ecommerce
>    Affects Versions: Release Branch 13.07, Trunk, Release Branch 15.12, Release Branch
>            Reporter: Ingo Wolfmayr
>            Assignee: Jacques Le Roux
>            Priority: Critical
>             Fix For: Upcoming Release, 16.11.02
>         Attachments: errror.txt
> When accessing a file/image in ecommerce (only seo version) that is physically missing
or the dataresource attribute isPublic=="N" the request results in an a loop.
> Demo data: 
> <Content contentId="test" contentTypeId="DOCUMENT" dataResourceId="test" statusId="CTNT_PUBLISHED"/>
> <DataResource dataResourceId="test" dataResourceTypeId="LOCAL_FILE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" dataResourceName="Test Image" objectInfo="PATH TO FILE" isPublic="N"
> <Content contentId="testurl" contentTypeId="DOCUMENT" dataResourceId="testurl" statusId="CTNT_PUBLISHED"/>
> <DataResource dataResourceId="testurl" dataResourceTypeId="URL_RESOURCE" dataTemplateTypeId="NONE"
statusId="CTNT_PUBLISHED" objectInfo="/testbild-content" isPublic="N"/>
> <ContentAssoc contentId="test" contentIdTo="testurl" contentAssocTypeId="ALTERNATE_URL"
fromDate="2006-09-22 00:00:00.0"/>
> Call:
> /ecomseo/testbild-content
> /ecomseo/stream?contentId=test
> I found that because I had server problems (server down), so it is quite easy to kill
the server by streaming a not existing contentId via via the ecomseo app.
> /ecomseo/stream?contentId=test1

This message was sent by Atlassian JIRA

View raw message