[jira] [Created] (OFBIZ-10439) Entity Maintenance / FindGeneric result list misses first data set
Michael Brohl created OFBIZ-10439: - Summary: Entity Maintenance / FindGeneric result list misses first data set Key: OFBIZ-10439 URL: https://issues.apache.org/jira/browse/OFBIZ-10439 Project: OFBiz Issue Type: Bug Components: framework/webtools Affects Versions: Trunk Reporter: Michael Brohl Steps to reproduce on the demo instance for trunk: # [https://demo-trunk.ofbiz.apache.org/webtools/control/EntitySQLProcessor:] select * from ORDER_HEADER -> shows 6 rows # [https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=OrderHeader=Y] -> shows 5 rows, the first one with orderId DEMO10090 is missing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-5928) Prototype of a Product Association recommender
[ https://issues.apache.org/jira/browse/OFBIZ-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520238#comment-16520238 ] Pallavi Goyal commented on OFBIZ-5928: -- Hi [~golja] , thank you for providing the prototype for the non-personalized recommendation. I was wondering if we can also have a prototype for the personalized recommendation. Please share your thoughts on the same. > Prototype of a Product Association recommender > -- > > Key: OFBIZ-5928 > URL: https://issues.apache.org/jira/browse/OFBIZ-5928 > Project: OFBiz > Issue Type: New Feature >Reporter: Anahita Goljahani >Priority: Minor > Attachments: product-recommendation.patch, recommender.zip, > recommender.zip > > > Hi all, as anticipated in my ApacheCon Europe presentation 'Introduction to a > Recommender System for Apache OFBiz' (downloadable from > https://cwiki.apache.org/confluence/x/OYPfAg), I have developed a prototype > of a Product Association recommender for OFBiz. Product Association > recommendations are suggestions of the type 'Customers who bought this item > also bought:', that are provided to online shoppers to help them in the > selection of products to buy. > Attached to this Jira ticket you will find a zip archive containing a > component named 'recommender', which implements the logic to generate > Production Association recommendations. The component contains a short guide > to its functionalities in the main folder. The guide also includes a short > paragraph that explains how to run a recommender demo. > I would really appreciate any review, feedback and suggestion by anyone > interested in this topic. > Thank you -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10123) Tomcat SSO in Cluster
[ https://issues.apache.org/jira/browse/OFBIZ-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520108#comment-16520108 ] James Yong commented on OFBIZ-10123: Hi Jacques, If IPv4 is not forced when cluster is enabled, the following error will occur on my Mac: *Can't assign requested address; No faulty members identified.* See also http://fixlinux.com/2011/08/17/tomcat-cluster-fails-to-start-on-os-x-lion/ No, I didn't test with a load balancer. It was manually tested while changing the urls on the browser. Regards, James > Tomcat SSO in Cluster > - > > Key: OFBIZ-10123 > URL: https://issues.apache.org/jira/browse/OFBIZ-10123 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Labels: Cluster, Login > Fix For: 17.12.01 > > Attachments: OFBIZ-10123.patch > > > Add Tomcat SSO support in clustered environment using ClusterSingleSignOn as > discussed in OFBIZ-10047. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[
https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520089#comment-16520089
]
Mathieu Lirzin commented on OFBIZ-4274:
---
I have been working on a POC during the last month. What has been implemented
is the support of the {{method}} attribute corresponds to OFBIZ-10438.
Additionally I have worked on supporting URI templates with multi-part paths
but I still need to find a solution to re-implement the support of overridden
view URI without using {{RequestHandler::getOverrideViewURI.}}
> Implement a REST Servlet
>
>
> Key: OFBIZ-4274
> URL: https://issues.apache.org/jira/browse/OFBIZ-4274
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
>Affects Versions: Trunk
>Reporter: Adrian Crum
>Priority: Major
> Labels: REST
> Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml,
> rest-conf.xml, swagger-pos-openapi.png
>
>
> Implement a REST servlet that will map REST requests to OFBiz services.
> Details are in the comments.
> [here is the discussion which took place on the dev
> ML|http://markmail.org/message/ai6q2fbksowaayn4]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10123) Tomcat SSO in Cluster
[ https://issues.apache.org/jira/browse/OFBIZ-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520087#comment-16520087 ] Jacques Le Roux commented on OFBIZ-10123: - Hi James, I only reviewed for now. Why do you need to force IPv4? Also I believe it should be parametrized and not the default. More later... Did you also test with a real cluster? I mean behind a Load Balancer. Thanks > Tomcat SSO in Cluster > - > > Key: OFBIZ-10123 > URL: https://issues.apache.org/jira/browse/OFBIZ-10123 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Labels: Cluster, Login > Fix For: 17.12.01 > > Attachments: OFBIZ-10123.patch > > > Add Tomcat SSO support in clustered environment using ClusterSingleSignOn as > discussed in OFBIZ-10047. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10438) Add method attribute to request-map to controll a uri can be called GET or POST only
[
https://issues.apache.org/jira/browse/OFBIZ-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520070#comment-16520070
]
Mathieu Lirzin commented on OFBIZ-10438:
Thanks for the feedback, I am looking into it.
> Add method attribute to request-map to controll a uri can be called GET or
> POST only
>
>
> Key: OFBIZ-10438
> URL: https://issues.apache.org/jira/browse/OFBIZ-10438
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments:
> OFBIZ-10438_0001-Improved-Add-ControlServlet-service-method.patch,
> OFBIZ-10438_0002-Improved-Add-optional-method-attribute-in-request-ma.patch,
> OFBIZ-10438_0003-Improved-Factorize-default-request-search-in-Request.patch,
> OFBIZ-10438_0004-Improved-Add-RequestHandler-resolveURI-method.patch
>
>
> As discussed in OFBIZ-4274, OFBiz runs doGet method in ControlServlet no
> matter what request it is.
> I like Mathieu's comment on adding a method attribute to the request-map
> element, it's almost the same as we implemented in our openapi:
>
> {code:java}
>
>
>
>
>
>
> {code}
> The difference is that we DON'T support method list expression:
> {code:java}
> ...
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10438) Add method attribute to request-map to controll a uri can be called GET or POST only
[
https://issues.apache.org/jira/browse/OFBIZ-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520061#comment-16520061
]
Shi Jinghai commented on OFBIZ-10438:
-
Hi Mathieu,
Amazing to see your patches, great work!
While I tested them in the following 3 cases, case 1 is OK, case 2 and 3 are
not OK:
*CASE 1*: Loading and parsing speed of controller.xml:
The loading and parsing speeds with or without your patch in my local
environment are same.
*CASE 2*: Error message when method not match:
a. edit framework/webtools/webapp/webtools/WEB-INF/controller.xml, add
method="post" to ping uri
{code:java}
{code}
b. visit [https://localhost:8443/webtools/control/ping] in browser
c. error message:
{code:java}
org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[ping]; this request does not exist or cannot be called directly.{code}
*CASE 3*: Without /control in uri (when we build openapi, we hope the uri can
be as clean as possible):
a. edit framework/webtools/webapp/webtools/WEB-INF/web.xml:
{code:java}
// add /ping to allowedPaths
allowedPaths
/ping:/ping.txt:/error:/control:/select:/index.html:/index.jsp:/default.html:/default.jsp
// change ControlServlet from /control/* to /*
ControlServlet
/*
{code}
b. edit framework/webtools/webapp/webtools/WEB-INF/controller.xml, remove
method="post" from ping uri
c. visit [https://localhost:8443/webtools/ping] in browser
d. PONG is displayed correctly
e. edit framework/webtools/webapp/webtools/WEB-INF/controller.xml, add
method="post" to ping uri
f. visit [https://localhost:8443/webtools/ping] in browser
g. error message:
{code:java}
ERROR in error page, (infinite loop or error page not found with name
[/error/error.jsp]), but here is the text just in case it helps you:
org.apache.ofbiz.webapp.control.RequestHandlerException: Unknown request
[ping]; this request does not exist or cannot be called directly.
{code}
Maybe case 3 is out of scope of this issue, you can ignore it.
Kind Regards,
> Add method attribute to request-map to controll a uri can be called GET or
> POST only
>
>
> Key: OFBIZ-10438
> URL: https://issues.apache.org/jira/browse/OFBIZ-10438
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments:
> OFBIZ-10438_0001-Improved-Add-ControlServlet-service-method.patch,
> OFBIZ-10438_0002-Improved-Add-optional-method-attribute-in-request-ma.patch,
> OFBIZ-10438_0003-Improved-Factorize-default-request-search-in-Request.patch,
> OFBIZ-10438_0004-Improved-Add-RequestHandler-resolveURI-method.patch
>
>
> As discussed in OFBIZ-4274, OFBiz runs doGet method in ControlServlet no
> matter what request it is.
> I like Mathieu's comment on adding a method attribute to the request-map
> element, it's almost the same as we implemented in our openapi:
>
> {code:java}
>
>
>
>
>
>
> {code}
> The difference is that we DON'T support method list expression:
> {code:java}
> ...
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
