[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892690#comment-17892690 ] Jacques Le Roux commented on OFBIZ-13152: - As you can see, this is not something done by OFBiz, it's Tomcat. We can't do nothing about it. BTW, you are not using the last safe version of it. It's Tomcat 9.0.91: https://issues.apache.org/jira/browse/OFBIZ-13124 So I guess you are not using OFBiz trunk HEAD which is the only safe version of trunk. Even if we recommend to not use trunk (even HEAD) but the last safe releases of 18.12: https://ofbiz.apache.org/download.html > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13152. --- Assignee: Jacques Le Roux Resolution: Information Provided > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Assignee: Jacques Le Roux >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13160) Rename 2 UtilValidate class methods for clarity
[ https://issues.apache.org/jira/browse/OFBIZ-13160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13160. --- Resolution: Implemented > Rename 2 UtilValidate class methods for clarity > > > Key: OFBIZ-13160 > URL: https://issues.apache.org/jira/browse/OFBIZ-13160 > Project: OFBiz > Issue Type: Improvement > Components: framework/base >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > [~danwatford] proposed to rename and better describe the 2 UtilValidate > class methods: > isUrl and urlInString. I respectively suggested isUrlInString and > isUrlInStringAndDoesNotStartByComponentProtocol. > Daniel also provided an UtilValidateTests class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[
https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892596#comment-17892596
]
ASF subversion and git services commented on OFBIZ-13147:
-
Commit 8ccee0f4842f9bd60de59755af8a424a707bbc29 in ofbiz-plugins's branch
refs/heads/release24.09 from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=8ccee0f48 ]
Improved: Prevent URL parameters manipulation (OFBIZ-13147)
Removes "JavaScriptEnabled=Y" in scrum DemoTest
Adds a missing
System.setProperty("SolrDispatchFilter", "runsAfterControlFilter");
expression on SolrTests::testAddProductToIndex
> Prevent URL parameters manipulation
> ---
>
> Key: OFBIZ-13147
> URL: https://issues.apache.org/jira/browse/OFBIZ-13147
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS, ALL PLUGINS
>Affects Versions: 18.12.16
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 18.12.17
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892599#comment-17892599 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 42b9ad8dbd416bf7ed73ad95e94681329cc83ac7 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=42b9ad8dbd ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) The "JavaScriptEnabled=Y" and "&wt=javabin" references are weaknesses. I temporarily put them in ControlFilter::doFilter to allow things (demo and integration tests) to work for my test (only possible on a site w. domain IP), ie not locally. I think we can remove "JavaScriptEnabled=Y". I put it there because we use it in links at https://ofbiz.apache.org/ofbiz-demos.html. Maybe other places where it's easy to remove w/o side effects. It's anyway an user preference, not mandatory in query string. I needed "&wt=javabin" for the Solr tests to pass. Sometimes ago I already faced a such issue. And then put in place what's needed. ControlFilter::isSolrTest is the solution by generalising this usage. > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892602#comment-17892602 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 222bf3cdd4b6bc533f7d99bd261b5147cd4557f8 in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=222bf3cdd4 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Fixes a "typo" > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[
https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892595#comment-17892595
]
ASF subversion and git services commented on OFBIZ-13147:
-
Commit 18f011d64c9d461ba5c8ab2cfa53205de7731a22 in ofbiz-plugins's branch
refs/heads/release18.12 from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=18f011d64 ]
Improved: Prevent URL parameters manipulation (OFBIZ-13147)
Removes "JavaScriptEnabled=Y" in scrum DemoTest
Adds a missing
System.setProperty("SolrDispatchFilter", "runsAfterControlFilter");
expression on SolrTests::testAddProductToIndex
Conflicts handled by hand
scrum/template/includes/DemoTest.ftl
solr/src/main/java/org/apache/ofbiz/solr/test/SolrTests.java
> Prevent URL parameters manipulation
> ---
>
> Key: OFBIZ-13147
> URL: https://issues.apache.org/jira/browse/OFBIZ-13147
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS, ALL PLUGINS
>Affects Versions: 18.12.16
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 18.12.17
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[
https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892586#comment-17892586
]
ASF subversion and git services commented on OFBIZ-13147:
-
Commit 18b5ab49174e9f8d15bc193360ab4736381e48a5 in ofbiz-plugins's branch
refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=18b5ab491 ]
Improved: Prevent URL parameters manipulation (OFBIZ-13147)
Removes "JavaScriptEnabled=Y" in scrum DemoTest
Adds a missing
System.setProperty("SolrDispatchFilter", "runsAfterControlFilter");
expression on SolrTests::testAddProductToIndex
> Prevent URL parameters manipulation
> ---
>
> Key: OFBIZ-13147
> URL: https://issues.apache.org/jira/browse/OFBIZ-13147
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS, ALL PLUGINS
>Affects Versions: 18.12.16
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 18.12.17
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892585#comment-17892585 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 1e0ded9e56050fe66727d65e9526c80bcbe5edee in ofbiz-site's branch refs/heads/master from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-site.git;h=1e0ded9 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Removes "JavaScriptEnabled=Y", it's not mandatory > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13160) Rename 2 UtilValidate class methods for clarity
[ https://issues.apache.org/jira/browse/OFBIZ-13160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892517#comment-17892517 ] ASF subversion and git services commented on OFBIZ-13160: - Commit efb43da46a6db4688b610387a596eef49e2f73e5 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=efb43da46a ] Improved: Rename 2 UtilValidate class methods for clarity (OFBIZ-13160) Daniel Watford proposed to rename and better describe the 2 UtilValidate class methods: isUrl and urlInString. I respectively suggested isUrlInString and isUrlInStringAndDoesNotStartByComponentProtocol. Daniel also provided an UtilValidateTests class. Thanks: Daniel > Rename 2 UtilValidate class methods for clarity > > > Key: OFBIZ-13160 > URL: https://issues.apache.org/jira/browse/OFBIZ-13160 > Project: OFBiz > Issue Type: Improvement > Components: framework/base >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > [~danwatford] proposed to rename and better describe the 2 UtilValidate > class methods: > isUrl and urlInString. I respectively suggested isUrlInString and > isUrlInStringAndDoesNotStartByComponentProtocol. > Daniel also provided an UtilValidateTests class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13160) Rename 2 UtilValidate class methods for clarity
Jacques Le Roux created OFBIZ-13160: --- Summary: Rename 2 UtilValidate class methods for clarity Key: OFBIZ-13160 URL: https://issues.apache.org/jira/browse/OFBIZ-13160 Project: OFBiz Issue Type: Improvement Components: framework/base Affects Versions: Upcoming Branch Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: Upcoming Branch [~danwatford] proposed to rename and better describe the 2 UtilValidate class methods: isUrl and urlInString. I respectively suggested isUrlInString and isUrlInStringAndDoesNotStartByComponentProtocol. Daniel also provided an UtilValidateTests class. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13151) Use Development Containers as development environments with necessary build tools already available
[ https://issues.apache.org/jira/browse/OFBIZ-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Watford closed OFBIZ-13151. -- Fix Version/s: Upcoming Branch Resolution: Implemented > Use Development Containers as development environments with necessary build > tools already available > --- > > Key: OFBIZ-13151 > URL: https://issues.apache.org/jira/browse/OFBIZ-13151 > Project: OFBiz > Issue Type: Improvement > Components: tools >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > Fix For: Upcoming Branch > > > Development Containers are becoming a popular method of ensuring a > container-based development environment has all the tools needed by a > developer to work on a project. > Development Containers ([https://containers.dev/)] depend on the developer's > host system running a container runtime, such as Docker. They are supported > in IntelliJ and VS Code. > Inclusion of a Development Container configuration in the ofbiz-framework > sources will allow new developers to open their IDE with all development > tools - such as the correct version of Java SDK - already in place. This > should improve the on-boarding experience for new developers. > Outside of IDE integration, tools such as DevPod can be used to create and > run Development Containers targeting a project. Users can then SSH into the > container and carry out development tasks such as gradle builds. This might > be an integration point for IDEs that do not currently have support > Development Containers, such as Eclipse. > > Further reading: > [https://blog.jetbrains.com/idea/2024/07/using-dev-containers-in-jetbrains-ides-part-1/] > [https://github.com/JetBrains/devcontainers-examples] > [https://containers.dev/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892385#comment-17892385 ] Arashpreet Singh commented on OFBIZ-13152: -- This is the HTML response. > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[
https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892384#comment-17892384
]
Arashpreet Singh commented on OFBIZ-13152:
--
{{HTTP Status 500 – Internal Server
Errorbody
\{font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b
\{color:white;background-color:#525D76;} h1 \{font-size:22px;} h2
\{font-size:16px;} h3 \{font-size:14px;} p \{font-size:12px;} a \{color:black;}
.line
\{height:1px;background-color:#525D76;border:none;}HTTP
Status 500 – Internal Server ErrorType
Status ReportMessage Internal Server
ErrorDescription The server encountered an unexpected condition
that prevented it from fulfilling the request.Apache
Tomcat/9.0.69}}
> Inconsistent Error Handling for Entity Creation via Exported Service
>
>
> Key: OFBIZ-13152
> URL: https://issues.apache.org/jira/browse/OFBIZ-13152
> Project: OFBiz
> Issue Type: Bug
> Components: rest-api
>Reporter: Arashpreet Singh
>Priority: Major
> Attachments: trunk-logs.txt
>
>
> There appears to be a problem with the OFBiz error-handling mechanism when
> creating an entity using an exported service. Initially, if incorrect input
> data is provided, OFBiz correctly returns a meaningful error message from the
> backend. However, upon resubmitting the same request without any changes,
> instead of returning the same meaningful error, the system responds with a
> 500 internal server error and an HTML response.
> Interestingly, when OFBiz is restarted, the first request with the same
> incorrect data again returns a proper, meaningful error message. But all
> subsequent requests with the same data continue to produce a 500 response,
> which is not ideal for consistent error reporting.
> This issue impacts debugging and error handling for services that rely on
> accurate back-end responses. The expected behavior would be to consistently
> return the meaningful error for all requests, regardless of whether OFBiz has
> been restarted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892357#comment-17892357
]
Jacques Le Roux commented on OFBIZ-13150:
-
(y)
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Assignee: Nicolas Malin
>Priority: Major
> Fix For: 24.09.01
>
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892366#comment-17892366 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 05d0de94bab85e96de30bf42b20e89ea2b8ffae2 in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=05d0de94ba ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Improves SecuredUpload.java in order to not accept Base64 encoded query strings even if "base64" is already in deniedWebShellTokens, better guarantee. Thanks to Nicolas. Just an indentation in ControlFilter. Add tcp and (for udp) in deniedWebShellTokens to stop reverse shells. > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892364#comment-17892364 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 3eb3fc9b156f4f27d4270ceadd808d87748d9095 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=3eb3fc9b15 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Improves SecuredUpload.java in order to not accept Base64 encoded query strings even if "base64" is already in deniedWebShellTokens, better guarantee. Thanks to Nicolas. Just an indentation in ControlFilter. Add tcp and (for udp) in deniedWebShellTokens to stop reverse shells. > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892362#comment-17892362 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 721e2e8cd52a809b78e524cf09976c9410834720 in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=721e2e8cd5 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Improves SecuredUpload.java in order to not accept Base64 encoded query strings even if "base64" is already in deniedWebShellTokens, better guarantee. Thanks to Nicolas. Just an indentation in ControlFilter. Add tcp and (for udp) in deniedWebShellTokens to stop reverse shells. Conflicts handled by hand framework/security/config/security.properties framework/security/src/main/java/org/apache/ofbiz/security/SecuredUpload.java framework/webapp/src/main/java/org/apache/ofbiz/webapp/control/ControlFilter.java > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892317#comment-17892317
]
ASF subversion and git services commented on OFBIZ-13150:
-
Commit 62e7aa24fe16cc9378d6f13bcd6a0a02e3dcf005 in ofbiz-framework's branch
refs/heads/release24.09 from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=62e7aa24fe ]
Fixed: example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
reports an error (OFBIZ-13150)
Error due to call the method as copyIfRequiredSystemPage groovy event where the
function has been move on private helper function for PortalPageServices.
To fix, we restore it on PortalPageMethods and call it from PortalPageServices
through script invoker (to escape code duplication).
Thanks to Jacques Le Roux for the issue
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Assignee: Nicolas Malin
>Priority: Major
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-13150.
-
Fix Version/s: 24.09.01
Resolution: Fixed
Thanks Jacques for this alert,
I fixed the issue
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Assignee: Nicolas Malin
>Priority: Major
> Fix For: 24.09.01
>
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892313#comment-17892313
]
ASF subversion and git services commented on OFBIZ-13150:
-
Commit 727f3cec1e2739a01420888306f66d1b5cc49eae in ofbiz-framework's branch
refs/heads/trunk from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=727f3cec1e ]
Fixed: example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
reports an error (OFBIZ-13150)
Error due to call the method as copyIfRequiredSystemPage groovy event where the
function has been move on private helper function for PortalPageServices.
To fix, we restore it on PortalPageMethods and call it from PortalPageServices
through script invoker (to escape code duplication).
Thanks to Jacques Le Roux for the issue
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Assignee: Nicolas Malin
>Priority: Major
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin reassigned OFBIZ-13150:
-
Assignee: Nicolas Malin
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Assignee: Nicolas Malin
>Priority: Major
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (OFBIZ-13157) Add group option on drow-down in xml screen form
[
https://issues.apache.org/jira/browse/OFBIZ-13157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Malin closed OFBIZ-13157.
-
Resolution: Done
> Add group option on drow-down in xml screen form
> -
>
> Key: OFBIZ-13157
> URL: https://issues.apache.org/jira/browse/OFBIZ-13157
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/widget
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Labels: Option, group, screen, widget, xml
> Attachments: Capture d’écran du 2024-10-21 11-33-31.png
>
>
> When you define a drop-down field in xml form, add new optional level with
> group-options to organize options.
> {code:java}
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Group-options can received all type options :
> {code:java}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> At this time only the drop-down is supported, group-option can works for
> radio and check but not implement on ftl macro library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13157) Add group option on drow-down in xml screen form
[
https://issues.apache.org/jira/browse/OFBIZ-13157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892249#comment-17892249
]
ASF subversion and git services commented on OFBIZ-13157:
-
Commit 24fc14a6eaadd9f97d4bd1263426ca6ef042d68b in ofbiz-framework's branch
refs/heads/trunk from Nicolas Malin
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=24fc14a6ea ]
Implemented: Add group option on drow-down in xml screen form (OFBIZ-13157)
(#842)
When you define a drop-down field in xml form, add new optional level with
group-options to organize options.
Group-options can receive all options type :
At this time only the drop-down is supported, group-option can works for radio
and check but not implement on ftl macro library.
> Add group option on drow-down in xml screen form
> -
>
> Key: OFBIZ-13157
> URL: https://issues.apache.org/jira/browse/OFBIZ-13157
> Project: OFBiz
> Issue Type: Improvement
> Components: framework/widget
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Labels: Option, group, screen, widget, xml
> Attachments: Capture d’écran du 2024-10-21 11-33-31.png
>
>
> When you define a drop-down field in xml form, add new optional level with
> group-options to organize options.
> {code:java}
>
>
>
>
>
>
>
>
>
>
>
> {code}
> Group-options can received all type options :
> {code:java}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
> At this time only the drop-down is supported, group-option can works for
> radio and check but not implement on ftl macro library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892206#comment-17892206 ] Jacques Le Roux commented on OFBIZ-13152: - OK, it seems it's Tomcat that intercepts in the 2nd case and raise a 500. What is the error (HTML response) in the browser? > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892202#comment-17892202 ] ASF subversion and git services commented on OFBIZ-13147: - Commit ad9035e2e4cd625816c97e3d3f528d1b51f5ecfd in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=ad9035e2e4 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Allows Solr tests to pass, so far so good... > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892201#comment-17892201 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 94e40f98620d0a98ea96af49209e4b303a1c925c in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=94e40f9862 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Allows Solr tests to pass, so far so good... Conflict handled by hand > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892203#comment-17892203 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 63201f5228bf5f44b9c3c65381d2c597fe829118 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=63201f5228 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Allows Solr tests to pass, so far so good... > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892140#comment-17892140 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 83f35c9004c2c8c01464b963cee005e1a61f902c in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=83f35c9004 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Allows JavaScriptEnabled=Y to pass. > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892139#comment-17892139 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 58ed838b4a0816555f928f4b453509b18082708b in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=58ed838b4a ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Allows JavaScriptEnabled=Y to pass. > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892138#comment-17892138 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 84ff5ee6f25605c48d11c84794fcfd959c7334fa in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=84ff5ee6f2 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Allows JavaScriptEnabled=Y to pass. Conflict handled by hand > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13123) Updated several (transitive) dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892121#comment-17892121 ] ASF subversion and git services commented on OFBIZ-13123: - Commit dd2e27f6d74cacd577011de8ddad4c31a28a1fee in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=dd2e27f6d7 ] Fixed: Updated several (transitive) dependencies (OFBIZ-13123) (#819) Forgot to remove basetests.xml from base ofbiz-component.xml > Updated several (transitive) dependencies > - > > Key: OFBIZ-13123 > URL: https://issues.apache.org/jira/browse/OFBIZ-13123 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Danny Trunk >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > https://github.com/apache/ofbiz-framework/pull/819 (framework) > https://github.com/apache/ofbiz-plugins/pull/125 (plugins) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892127#comment-17892127 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 166bbdf6d75edb41831fa21f2b83f0a056036fd2 in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=166bbdf6d7 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Fixes previous commit MODULE is not module > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892124#comment-17892124 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 612ad736b5c93db923573388e8565d32db4f90f4 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=612ad736b5 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) I found that java.util.Base64 is not easy to use. Hopefully putting base64 in deniedWebShellTokens should be enough > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892122#comment-17892122 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 68156f75a35d9ec30714699be32e0ad407aff278 in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=68156f75a3 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) I found that java.util.Base64 is not easy to use. Hopefully putting base64 in deniedWebShellTokens should be enough > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13123) Updated several (transitive) dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892123#comment-17892123 ] ASF subversion and git services commented on OFBIZ-13123: - Commit 891c41fe064c7cac41de6f193212bf64fc0b52e3 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=891c41fe06 ] Fixed: Updated several (transitive) dependencies (OFBIZ-13123) (#819) Forgot to remove basetests.xml from base ofbiz-component.xml > Updated several (transitive) dependencies > - > > Key: OFBIZ-13123 > URL: https://issues.apache.org/jira/browse/OFBIZ-13123 > Project: OFBiz > Issue Type: Sub-task > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Danny Trunk >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > > https://github.com/apache/ofbiz-framework/pull/819 (framework) > https://github.com/apache/ofbiz-plugins/pull/125 (plugins) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892120#comment-17892120 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 7c986a63258f1fff1268c65e13699f977c85c635 in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=7c986a6325 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) I found that java.util.Base64 is not easy to use. Hopefully putting base64 in deniedWebShellTokens should be enough Conflicts handled by hand > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13151) Use Development Containers as development environments with necessary build tools already available
[ https://issues.apache.org/jira/browse/OFBIZ-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892078#comment-17892078 ] ASF subversion and git services commented on OFBIZ-13151: - Commit bb13554641e7e884b5ea5e677b9bb6468f71acad in ofbiz-framework's branch refs/heads/trunk from Daniel Watford [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=bb13554641 ] Added: Development Container configuration (OFBIZ-13151) Introduced a Development Container (devcontainer) which provides container-based development where tools needed by a developer are already installed, hopefully improving the developer onboarding experience. > Use Development Containers as development environments with necessary build > tools already available > --- > > Key: OFBIZ-13151 > URL: https://issues.apache.org/jira/browse/OFBIZ-13151 > Project: OFBiz > Issue Type: Improvement > Components: tools >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > Development Containers are becoming a popular method of ensuring a > container-based development environment has all the tools needed by a > developer to work on a project. > Development Containers ([https://containers.dev/)] depend on the developer's > host system running a container runtime, such as Docker. They are supported > in IntelliJ and VS Code. > Inclusion of a Development Container configuration in the ofbiz-framework > sources will allow new developers to open their IDE with all development > tools - such as the correct version of Java SDK - already in place. This > should improve the on-boarding experience for new developers. > Outside of IDE integration, tools such as DevPod can be used to create and > run Development Containers targeting a project. Users can then SSH into the > container and carry out development tasks such as gradle builds. This might > be an integration point for IDEs that do not currently have support > Development Containers, such as Eclipse. > > Further reading: > [https://blog.jetbrains.com/idea/2024/07/using-dev-containers-in-jetbrains-ides-part-1/] > [https://github.com/JetBrains/devcontainers-examples] > [https://containers.dev/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892076#comment-17892076 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 2a60c0b50a147ddc2ff2b58d7955928c0f3cea44 in ofbiz-framework's branch refs/heads/release18.12 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=2a60c0b50a ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Handles Base64 encoded reverse shells Conflicts handled by hand > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892077#comment-17892077 ] ASF subversion and git services commented on OFBIZ-13147: - Commit ea6ae97b750223f57956f9b0a758669e80a50ad3 in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=ea6ae97b75 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Handles Base64 encoded reverse shells > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13147) Prevent URL parameters manipulation
[ https://issues.apache.org/jira/browse/OFBIZ-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892071#comment-17892071 ] ASF subversion and git services commented on OFBIZ-13147: - Commit 8d837744413d8b3f1c2c28ff3a437103d0c7a8f5 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=8d83774441 ] Improved: Prevent URL parameters manipulation (OFBIZ-13147) Handles Base64 encoded reverse shells > Prevent URL parameters manipulation > --- > > Key: OFBIZ-13147 > URL: https://issues.apache.org/jira/browse/OFBIZ-13147 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS, ALL PLUGINS >Affects Versions: 18.12.16 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 18.12.17 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892050#comment-17892050 ] Arashpreet Singh commented on OFBIZ-13152: -- Yes, I am using trunk. > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arashpreet Singh updated OFBIZ-13152: - Attachment: trunk-logs.txt > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892040#comment-17892040 ] Arashpreet Singh commented on OFBIZ-13152: -- [^trunk-logs.txt] Logs file attached. > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: trunk-logs.txt > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13159: Attachment: OFBIZ-13159-2.patch > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159-1.patch, OFBIZ-13159-2.patch, > OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[
https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891945#comment-17891945
]
Jacques Le Roux commented on OFBIZ-13159:
-
It's certainly perfectible before using the bom.jon file, notably as suggested
at
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=287607444#SBOMSoftwareBillofMaterials-UsingSBOMs
One possible thing is to automatically generate it at the end of the build
process. Adding {{test.finalizedBy(cyclonedxBom)}} at the end of build.gradle
is enough: [^OFBIZ-13159-2.patch]
> Create a 'Software Bill of Materials' (SBOM)
> --
>
> Key: OFBIZ-13159
> URL: https://issues.apache.org/jira/browse/OFBIZ-13159
> Project: OFBiz
> Issue Type: Improvement
> Components: Gradle
>Affects Versions: Upcoming Branch
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-13159-1.patch, OFBIZ-13159-2.patch,
> OFBIZ-13159.patch
>
>
> As suggested by
> https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials
> we should create a SBOM
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13159: Attachment: OFBIZ-13159-1.patch > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159-1.patch, OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891865#comment-17891865 ] Jacques Le Roux commented on OFBIZ-13159: - Commenting out the includeMetadataResolution element works w/o warning: [^OFBIZ-13159-1.patch] > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159-1.patch, OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891863#comment-17891863 ] Jacques Le Roux edited comment on OFBIZ-13159 at 10/22/24 1:08 PM: --- In case you did not read the from the link in description, [here is the CycloneDX reference|https://github.com/CycloneDX/cyclonedx-gradle-plugin] So to run the task it's simply: gradle cyclonedxBom was (Author: jacques.le.roux): In case you did not read the from the link in description, [here the CycloneDX reference|https://github.com/CycloneDX/cyclonedx-gradle-plugin] So to run the task it's simply: gradle cyclonedxBom > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891863#comment-17891863 ] Jacques Le Roux commented on OFBIZ-13159: - In case you did not read the from the link in description, [here the CycloneDX reference|https://github.com/CycloneDX/cyclonedx-gradle-plugin] So to run the task it's simply: gradle cyclonedxBom > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891860#comment-17891860 ] Jacques Le Roux commented on OFBIZ-13159: - After some efforts, [^OFBIZ-13159.patch] works, with 2 warnings: > Task :cyclonedxBom Unknown keyword meta:enum - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword Unknown keyword deprecated - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
[ https://issues.apache.org/jira/browse/OFBIZ-13159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13159: Attachment: OFBIZ-13159.patch > Create a 'Software Bill of Materials' (SBOM) > -- > > Key: OFBIZ-13159 > URL: https://issues.apache.org/jira/browse/OFBIZ-13159 > Project: OFBiz > Issue Type: Improvement > Components: Gradle >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Upcoming Branch > > Attachments: OFBIZ-13159.patch > > > As suggested by > https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials > we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13159) Create a 'Software Bill of Materials' (SBOM)
Jacques Le Roux created OFBIZ-13159: --- Summary: Create a 'Software Bill of Materials' (SBOM) Key: OFBIZ-13159 URL: https://issues.apache.org/jira/browse/OFBIZ-13159 Project: OFBiz Issue Type: Improvement Components: Gradle Affects Versions: Upcoming Branch Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: Upcoming Branch As suggested by https://cwiki.apache.org/confluence/display/SECURITY/SBOM+Software+Bill+of+Materials we should create a SBOM -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13158) Update method to check if the string starts with component:// instead of merely containing it
Jacques Le Roux created OFBIZ-13158: --- Summary: Update method to check if the string starts with component:// instead of merely containing it Key: OFBIZ-13158 URL: https://issues.apache.org/jira/browse/OFBIZ-13158 Project: OFBiz Issue Type: Improvement Components: framework/base Affects Versions: 18.12.16 Reporter: Jacques Le Roux Assignee: Deepak Dixit Fix For: 18.12.17 To work the component protocol must be placed at start of URL -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (OFBIZ-13155) Update to Apache Tika 3.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-13155: - Here the error stack for testSendOrderConfirmation 2024-10-21 18:30:48,405 |main |ServiceDispatcher |T| [[Sync service failed...- total:0.0,since last(Begin):0.0]] - 'test-dispatcher-BwGo6DM4DS / sendMailFromScreen' 2024-10-21 18:30:48,406 |main |TransactionUtil |W| Calling transaction setRollbackOnly; this stack trace shows where this is happening: java.lang.Exception: Service [sendMailFromScreen] threw an unexpected exception/error at org.apache.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:372) [main/:?] at org.apache.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:306) [main/:?] at org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:556) [main/:?] at org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244) [main/:?] at org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93) [main/:?] at org.apache.ofbiz.order.order.OrderServices.sendOrderNotificationScreen(OrderServices.java:2858) [main/:?] at org.apache.ofbiz.order.order.OrderServices.sendOrderConfirmNotification(OrderServices.java:2679) [main/:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] at org.apache.ofbiz.service.engine.StandardJavaEngine.serviceInvoker(StandardJavaEngine.java:101) [main/:?] at org.apache.ofbiz.service.engine.StandardJavaEngine.runSync(StandardJavaEngine.java:57) [main/:?] at org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:429) [main/:?] at org.apache.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:244) [main/:?] at org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runSync(GenericDispatcherFactory.java:93) [main/:?] at org.codehaus.groovy.vmplugin.v8.IndyInterface.fromCache(IndyInterface.java:321) [groovy-4.0.22.jar:4.0.22] at org.apache.ofbiz.ecommerce.order.test.OrderNotificationTests.testSendOrderConfirmation(OrderNotificationTests.groovy:36) [main/:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] at junit.framework.TestCase.runTest(TestCase.java:177) [junit-4.13.2.jar:4.13.2] at junit.framework.TestCase.runBare(TestCase.java:142) [junit-4.13.2.jar:4.13.2] at junit.framework.TestResult$1.protect(TestResult.java:122) [junit-4.13.2.jar:4.13.2] at junit.framework.TestResult.runProtected(TestResult.java:142) [junit-4.13.2.jar:4.13.2] at junit.framework.TestResult.run(TestResult.java:125) [junit-4.13.2.jar:4.13.2] at junit.framework.TestCase.run(TestCase.java:130) [junit-4.13.2.jar:4.13.2] at junit.framework.TestSuite.runTest(TestSuite.java:241) [junit-4.13.2.jar:4.13.2] at junit.framework.TestSuite.run(TestSuite.java:236) [junit-4.13.2.jar:4.13.2] at junit.framework.TestSuite.runTest(TestSuite.java:241) [junit-4.13.2.jar:4.13.2] at junit.framework.TestSuite.run(TestSuite.java:236) [junit-4.13.2.jar:4.13.2] at org.apache.ofbiz.testtools.TestRunContainer.start(TestRunContainer.java:90) [main/:?] at org.apache.ofbiz.base.container.ContainerLoader.startLoadedContainers(ContainerLoader.java:153) [main/:?] at org.apache.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:77) [main/:?] at org.apache.ofbiz.base.start.StartupControlPanel.loadContainers(StartupControlPanel.java:146) [main/:?] at org.apache.ofbiz.base.start.StartupControlPanel.start(StartupControlPanel.java:70) [main/:?] at org.apache.ofbiz.base.start.Start.main(Start.java:89) [main/:?] 2024-10-21 18:30:48,409 |main |OrderServices |E| null org.apache.ofbiz.service.GenericServiceException: Service [sendMailFromScreen] target threw an unexpected exception (org/apache/avalon/framework/configuration/ConfigurationException) at org.apache.ofbiz.service.engine.StandardJavaEngine.serviceInvoker(StandardJavaE
[jira] [Commented] (OFBIZ-13155) Update to Apache Tika 3.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891598#comment-17891598 ] ASF subversion and git services commented on OFBIZ-13155: - Commit fffa395d17a930bfc6c10b6986876b48ebc63c6d in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=fffa395d17 ] Improved: Update to Apache Tika 3.0.0 (OFBIZ-13155) This reverts commit 7c3a622f08e37d6a68125844383820dac1592f23. When running testSendOrderConfirmation and testFopMacroLibrary there are a lot of issues with dependencies related to org.apache.xmlgraphics Tika, FOP and PDFBox To be checked before going further using PDFBox 33.0.3 and FOP 2.10 I'll put the the error stack for testSendOrderConfirmation in the Jira > Update to Apache Tika 3.0.0 > --- > > Key: OFBIZ-13155 > URL: https://issues.apache.org/jira/browse/OFBIZ-13155 > Project: OFBiz > Issue Type: Improvement > Components: content, framework/security, framework/widget >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Follows [https://lists.apache.org/thread/wz7ds83q39t74n5lloy87m504m9r7gs9] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13157) Add group option on drow-down in xml screen form
Nicolas Malin created OFBIZ-13157:
-
Summary: Add group option on drow-down in xml screen form
Key: OFBIZ-13157
URL: https://issues.apache.org/jira/browse/OFBIZ-13157
Project: OFBiz
Issue Type: Improvement
Components: framework/widget
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Attachments: Capture d’écran du 2024-10-21 11-33-31.png
When you define a drop-down field in xml form, add new optional level with
group-options to organize options.
{code:java}
{code}
Group-options can received all type options :
{code:java}
{code}
At this time only the drop-down is supported, group-option can works for radio
and check but not implement on ftl macro library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (OFBIZ-13155) Update to Apache Tika 3.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13155. --- Fix Version/s: Upcoming Branch Resolution: Fixed > Update to Apache Tika 3.0.0 > --- > > Key: OFBIZ-13155 > URL: https://issues.apache.org/jira/browse/OFBIZ-13155 > Project: OFBiz > Issue Type: Improvement > Components: content, framework/security, framework/widget >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: Upcoming Branch > > > Follows [https://lists.apache.org/thread/wz7ds83q39t74n5lloy87m504m9r7gs9] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13156) Use media type "text/javascript" instead of "application/javascript to follow RFC-9239
[ https://issues.apache.org/jira/browse/OFBIZ-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891448#comment-17891448 ] ASF subversion and git services commented on OFBIZ-13156: - Commit 847c0056aa3c835748474d31d4fc784e1ebf3412 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=847c0056aa ] Improved: Use media type "text/javascript" instead of "application/javascript to follow RFC-9239 (OFBIZ-13156) See https://datatracker.ietf.org/doc/html/rfc9239#name-iana-considerations > Use media type "text/javascript" instead of "application/javascript to follow > RFC-9239 > -- > > Key: OFBIZ-13156 > URL: https://issues.apache.org/jira/browse/OFBIZ-13156 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows TIKA-4119 > bq. RFC-9239 obsoletes some javascript media types, including > "application/javascript", which is currently returned by Tika for javascript > files. "text/javascript" is defined as the most widely supported one, so Tika > should reflect this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-13156) Use media type "text/javascript" instead of "application/javascript to follow RFC-9239
[ https://issues.apache.org/jira/browse/OFBIZ-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13156. --- Resolution: Fixed > Use media type "text/javascript" instead of "application/javascript to follow > RFC-9239 > -- > > Key: OFBIZ-13156 > URL: https://issues.apache.org/jira/browse/OFBIZ-13156 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows TIKA-4119 > bq. RFC-9239 obsoletes some javascript media types, including > "application/javascript", which is currently returned by Tika for javascript > files. "text/javascript" is defined as the most widely supported one, so Tika > should reflect this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13155) Update to Apache Tika 3.0.0
[ https://issues.apache.org/jira/browse/OFBIZ-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891447#comment-17891447 ] ASF subversion and git services commented on OFBIZ-13155: - Commit 7c3a622f08e37d6a68125844383820dac1592f23 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=7c3a622f08 ] Improved: Update to Apache Tika 3.0.0 (OFBIZ-13155) Implications: * javax.xml.bind.DatatypeConverter replaced by jakarta.xml.bind.DatatypeConverter * upload of PDFBox to 3.0.3 * need of org.apache.pdfbox.Loader in SecuredUpload.java (see https://pdfbox.apache.org/3.0/migration.html#use-loader-to-get-a-pdf-document) While reading https://downloads.apache.org/tika/3.0.0/CHANGES-3.0.0.txt found that we use a lot of "application/javascript" while "text/javascript" is recommended by RFC-9239. > Update to Apache Tika 3.0.0 > --- > > Key: OFBIZ-13155 > URL: https://issues.apache.org/jira/browse/OFBIZ-13155 > Project: OFBiz > Issue Type: Improvement > Components: content, framework/security, framework/widget >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > > Follows [https://lists.apache.org/thread/wz7ds83q39t74n5lloy87m504m9r7gs9] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13156) Use media type "text/javascript" instead of "application/javascript to follow RFC-9239
[ https://issues.apache.org/jira/browse/OFBIZ-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891446#comment-17891446 ] ASF subversion and git services commented on OFBIZ-13156: - Commit f96232d75369f28b8a662085f3e69954c88e0598 in ofbiz-plugins's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=f96232d75 ] Improved: Use media type "text/javascript" instead of "application/javascript to follow RFC-9239 (OFBIZ-13156) See https://datatracker.ietf.org/doc/html/rfc9239#name-iana-considerations > Use media type "text/javascript" instead of "application/javascript to follow > RFC-9239 > -- > > Key: OFBIZ-13156 > URL: https://issues.apache.org/jira/browse/OFBIZ-13156 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows TIKA-4119 > bq. RFC-9239 obsoletes some javascript media types, including > "application/javascript", which is currently returned by Tika for javascript > files. "text/javascript" is defined as the most widely supported one, so Tika > should reflect this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13156) Use media type "text/javascript" instead of "application/javascript to follow RFC-9239
[ https://issues.apache.org/jira/browse/OFBIZ-13156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13156: Description: This follows TIKA-4119 bq. RFC-9239 obsoletes some javascript media types, including "application/javascript", which is currently returned by Tika for javascript files. "text/javascript" is defined as the most widely supported one, so Tika should reflect this. > Use media type "text/javascript" instead of "application/javascript to follow > RFC-9239 > -- > > Key: OFBIZ-13156 > URL: https://issues.apache.org/jira/browse/OFBIZ-13156 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Upcoming Branch >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > This follows TIKA-4119 > bq. RFC-9239 obsoletes some javascript media types, including > "application/javascript", which is currently returned by Tika for javascript > files. "text/javascript" is defined as the most widely supported one, so Tika > should reflect this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13156) Use media type "text/javascript" instead of "application/javascript to follow RFC-9239
Jacques Le Roux created OFBIZ-13156: --- Summary: Use media type "text/javascript" instead of "application/javascript to follow RFC-9239 Key: OFBIZ-13156 URL: https://issues.apache.org/jira/browse/OFBIZ-13156 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Upcoming Branch Reporter: Jacques Le Roux Assignee: Jacques Le Roux Fix For: Upcoming Branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13155) Update to Apache Tika 3.0.0
Jacques Le Roux created OFBIZ-13155: --- Summary: Update to Apache Tika 3.0.0 Key: OFBIZ-13155 URL: https://issues.apache.org/jira/browse/OFBIZ-13155 Project: OFBiz Issue Type: Improvement Components: content, framework/security, framework/widget Affects Versions: Upcoming Branch Reporter: Jacques Le Roux Assignee: Jacques Le Roux Follows [https://lists.apache.org/thread/wz7ds83q39t74n5lloy87m504m9r7gs9] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13154) Add uri shortener function
Nicolas Malin created OFBIZ-13154:
-
Summary: Add uri shortener function
Key: OFBIZ-13154
URL: https://issues.apache.org/jira/browse/OFBIZ-13154
Project: OFBiz
Issue Type: Improvement
Components: framework
Reporter: Nicolas Malin
Assignee: Nicolas Malin
This improvement offer the possibility to use a shortener url to call ofbiz
when it render a url.
The origin requirement is to send by email a url to contact OFBiz without any
information on technical or functionnal context like JWToken, userLogin,
orderId, partyId and so on. OFBiz forward only a short reference that match the
actual uri wanted.
Example :
* ecommerce/myaccount/order/ORD10034 -> s/tiozerzaze
*
ecommerce/myaccount?token=JWT[more..than..100]axdr&userLoginId=m...@ofbiz.org
-> s/epsserlner
When a request arrive in OFBiz with the pattern
{noformat}
s/{shortener}
{noformat}
, the request handler forward to matched uri.
To generate a shortener on freemarker template just use it like it :
{code}
<@ofbizUrl pathShortener="true">${MyBigUriToSecure}
{code}
For email template it's ugly recommand to use *webSiteId* and *fullPath*
{code}
<@ofbizUrl webSiteId="MyWebSite" fullPath="true"
pathShortener="true">${MyBigUriToSecure}
{code}
With this you can have a url like this : https://mywebsite.mydomain/s/rytedqzdfd
At this time only *<@ofbizUrl *macro freemarker support it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890858#comment-17890858
]
Nicolas Malin commented on OFBIZ-13150:
---
Oh thanks for this alert, I'll look at it.
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Priority: Major
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890849#comment-17890849
]
Jacques Le Roux edited comment on OFBIZ-13150 at 10/18/24 8:04 AM:
---
I found at least
myportal/control/ManagePortalPages?parentPortalPageId=PartyProfile. I guess
there could be more.
[~nmalin] here is [^OFBIZ-13150.patch] that fixes the problem. Maybe rather a
workaround, that's why I did not push. I prefer your review since you made the
migration and are more knowing the whole thing around PortalPage migration.
The error message says that there is no copyIfRequiredSystemPage() in
PortalPageMethods. That's right, copyIfRequiredSystemPage() is in
PortalPageServices. Both are in org.apache.ofbiz.common. I believe because
PortalPageServices is not a class, only methods, you can"t use private methods
there, same in PortalPageMethods. It even seems that you need to declare a
[Groovy trait to allow use of private
methods|https://groovy-lang.org/objectorientation.html#_private_methods].
I don't know why PortalPageMethods was "preferred" by Groovy, maybe because it
appears before when compiling Groovy? Anyway, I moved both "private" methods
to PortalPageMethods and make some modifications for the whole to work.
TIA for your review, please take it easy, no hurry, not a big deal as it works
anyway :)
was (Author: jacques.le.roux):
I found at least
myportal/control/ManagePortalPages?parentPortalPageId=PartyProfile. I guess
there could be more.
[~nmalin] here is a patch that fixes the problem. Maybe rather a workaround,
that's why I did not push. I prefer your review since you made the migration
and are more knowing the whole thing around PortalPage migration.
The error message says that there is no copyIfRequiredSystemPage() in
PortalPageMethods. That's right, copyIfRequiredSystemPage() is in
PortalPageServices. Both are in org.apache.ofbiz.common. I believe because
PortalPageServices is not a class, only methods, you can"t use private methods
there, same in PortalPageMethods. It even seems that you need to declare a
[Groovy trait to allow use of private
methods|https://groovy-lang.org/objectorientation.html#_private_methods].
I don't know why PortalPageMethods was "preferred" by Groovy, maybe because it
appears before when compiling Groovy? Anyway, I moved both "private" methods
to PortalPageMethods and make some modifications for the whole to work.
TIA for your review, please take it easy, no hurry, not a big deal as it works
anyway :)
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Priority: Major
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890849#comment-17890849
]
Jacques Le Roux commented on OFBIZ-13150:
-
I found at least
myportal/control/ManagePortalPages?parentPortalPageId=PartyProfile. I guess
there could be more.
[~nmalin] here is a patch that fixes the problem. Maybe rather a workaround,
that's why I did not push. I prefer your review since you made the migration
and are more knowing the whole thing around PortalPage migration.
The error message says that there is no copyIfRequiredSystemPage() in
PortalPageMethods. That's right, copyIfRequiredSystemPage() is in
PortalPageServices. Both are in org.apache.ofbiz.common. I believe because
PortalPageServices is not a class, only methods, you can"t use private methods
there, same in PortalPageMethods. It even seems that you need to declare a
[Groovy trait to allow use of private
methods|https://groovy-lang.org/objectorientation.html#_private_methods].
I don't know why PortalPageMethods was "preferred" by Groovy, maybe because it
appears before when compiling Groovy? Anyway, I moved both "private" methods
to PortalPageMethods and make some modifications for the whole to work.
TIA for your review, please take it easy, no hurry, not a big deal as it works
anyway :)
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Priority: Major
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-13150:
Attachment: OFBIZ-13150.patch
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Priority: Major
> Attachments: OFBIZ-13150.patch
>
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
[ https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890814#comment-17890814 ] Jacques Le Roux commented on OFBIZ-13153: - Please confirm that you are using multitenant=Y in general.properties > "null DispatchContext" issue under high load and concurrency > > > Key: OFBIZ-13153 > URL: https://issues.apache.org/jira/browse/OFBIZ-13153 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 18.12.16 > Environment: Virtual Machine: > OS: RHEL 8.9 > VCPU: 16 > Total RAM: 64 GB > Heap allocation (Xmx): 8 GB >Reporter: Mayank S >Priority: Major > Labels: performance > Fix For: 18.12.17 > > Original Estimate: 24h > Remaining Estimate: 24h > > While performance-testing Ofbiz 18 under high load (200 concurrent users), we > have observed an intermittent error, stating "null DispatchContext". > While doing more analysis, we realized it is a thread-safety issue, and it > was fixed by adding the 'synchronized' keyword to the following method > signatures in ServiceDispatcher.java: > public static synchronized getInstance (Delegator delegator) > public static synchronized void register (DispatchContext context) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[
https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890440#comment-17890440
]
Jacques Le Roux commented on OFBIZ-13152:
-
22.01 is abandonned, next stable is now 24.09. Are you using trunk?
Again
{quote}the stack of errors in log would be quite interesting.
{quote}
> Inconsistent Error Handling for Entity Creation via Exported Service
>
>
> Key: OFBIZ-13152
> URL: https://issues.apache.org/jira/browse/OFBIZ-13152
> Project: OFBiz
> Issue Type: Bug
> Components: rest-api
>Reporter: Arashpreet Singh
>Priority: Major
>
> There appears to be a problem with the OFBiz error-handling mechanism when
> creating an entity using an exported service. Initially, if incorrect input
> data is provided, OFBiz correctly returns a meaningful error message from the
> backend. However, upon resubmitting the same request without any changes,
> instead of returning the same meaningful error, the system responds with a
> 500 internal server error and an HTML response.
> Interestingly, when OFBiz is restarted, the first request with the same
> incorrect data again returns a proper, meaningful error message. But all
> subsequent requests with the same data continue to produce a 500 response,
> which is not ideal for consistent error reporting.
> This issue impacts debugging and error handling for services that rely on
> accurate back-end responses. The expected behavior would be to consistently
> return the meaningful error for all requests, regardless of whether OFBiz has
> been restarted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890405#comment-17890405 ] Arashpreet Singh edited comment on OFBIZ-13152 at 10/17/24 11:58 AM: - Within release22.01 it works as expected was (Author: arash): * Within release22.01 it works as expected > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890405#comment-17890405 ] Arashpreet Singh edited comment on OFBIZ-13152 at 10/17/24 11:58 AM: - * Within release22.01 it works as expected was (Author: arash): * Within trunk even the first request fails (at least on my end). Fails in respect to: I just get a generic 500 error, not the service level error * Within release22.01 it works as expected > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
[ https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890415#comment-17890415 ] Mayank S edited comment on OFBIZ-13153 at 10/17/24 10:58 AM: - I am well aware of the demerits of synchronization; however, using synchronized in the getInstance () method of Singleton classes is common practice. 'localContext' in the ServiceDispatcher class is essentially like a singleton map which is storing the dispatch-context objects. We tried making it a ConcurrentHashMap instead of a HashMap but it still didn't fix the issue. Hence, we synchronized the register (DispatchContext) method. I believe this method is called only during start-up/ one time for each tenant dispatcher, and hence the performance implication is not much if we are looking at only one call being affected, amongst thousands to millions of calls. However, if it fails to register the dispatch context once, for some reason, the dispatcher always comes as null for that tenant continuously in each subsequent call, increasing the error-rate. If there is any other solution to this problem, which has been tested and proven with a high load of 200 concurrent users or higher, then please let me know. was (Author: JIRAUSER307429): I am well aware of the demerits of synchronization; however, using synchronized in the getInstance () method of Singleton classes is common practice. 'localContext' in the ServiceDispatcher class is essentially like a singleton map which is storing the dispatch-context objects. We tried making it a ConcurrentHashMap instead of a HashMap but it still didn't fix the issue. Hence, we synchronized the register (DispatchContext) method. I believe this method is called only during start-up/ one time for each tenant dispatcher, and hence the performance implication is not much if we are looking at only one call being affected, amongst thousands to millions of calls. If there is any other solution to this problem, which has been tested and proven with a high load of 200 concurrent users or higher, then please let me know. > "null DispatchContext" issue under high load and concurrency > > > Key: OFBIZ-13153 > URL: https://issues.apache.org/jira/browse/OFBIZ-13153 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 18.12.16 > Environment: Virtual Machine: > OS: RHEL 8.9 > VCPU: 16 > Total RAM: 64 GB > Heap allocation (Xmx): 8 GB >Reporter: Mayank S >Priority: Major > Labels: performance > Fix For: 18.12.17 > > Original Estimate: 24h > Remaining Estimate: 24h > > While performance-testing Ofbiz 18 under high load (200 concurrent users), we > have observed an intermittent error, stating "null DispatchContext". > While doing more analysis, we realized it is a thread-safety issue, and it > was fixed by adding the 'synchronized' keyword to the following method > signatures in ServiceDispatcher.java: > public static synchronized getInstance (Delegator delegator) > public static synchronized void register (DispatchContext context) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
[ https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890415#comment-17890415 ] Mayank S commented on OFBIZ-13153: -- I am well aware of the demerits of synchronization; however, using synchronized in the getInstance () method of Singleton classes is common practice. 'localContext' in the ServiceDispatcher class is essentially like a singleton map which is storing the dispatch-context objects. We tried making it a ConcurrentHashMap instead of a HashMap but it still didn't fix the issue. Hence, we synchronized the register (DispatchContext) method. I believe this method is called only during start-up/ one time for each tenant dispatcher, and hence the performance implication is not much if we are looking at only one call being affected, amongst thousands to millions of calls. If there is any other solution to this problem, which has been tested and proven with a high load of 200 concurrent users or higher, then please let me know. > "null DispatchContext" issue under high load and concurrency > > > Key: OFBIZ-13153 > URL: https://issues.apache.org/jira/browse/OFBIZ-13153 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 18.12.16 > Environment: Virtual Machine: > OS: RHEL 8.9 > VCPU: 16 > Total RAM: 64 GB > Heap allocation (Xmx): 8 GB >Reporter: Mayank S >Priority: Major > Labels: performance > Fix For: 18.12.17 > > Original Estimate: 24h > Remaining Estimate: 24h > > While performance-testing Ofbiz 18 under high load (200 concurrent users), we > have observed an intermittent error, stating "null DispatchContext". > While doing more analysis, we realized it is a thread-safety issue, and it > was fixed by adding the 'synchronized' keyword to the following method > signatures in ServiceDispatcher.java: > public static synchronized getInstance (Delegator delegator) > public static synchronized void register (DispatchContext context) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890405#comment-17890405 ] Arashpreet Singh commented on OFBIZ-13152: -- * Within trunk even the first request fails (at least on my end). Fails in respect to: I just get a generic 500 error, not the service level error * Within release22.01 it works as expected > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arashpreet Singh updated OFBIZ-13152: - Attachment: (was: 20241009_112047.MP4) > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
[ https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890341#comment-17890341 ] Jacques Le Roux commented on OFBIZ-13153: - Here are some ideas that could be exploited https://stackoverflow.com/questions/1365880/disadvantage-of-synchronized-methods-in-java. https://medium.com/@jerzy.chalupski/the-perils-of-synchronized-8bdf6572b215 For instance is only DispatchContext concerned? > "null DispatchContext" issue under high load and concurrency > > > Key: OFBIZ-13153 > URL: https://issues.apache.org/jira/browse/OFBIZ-13153 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 18.12.16 > Environment: Virtual Machine: > OS: RHEL 8.9 > VCPU: 16 > Total RAM: 64 GB > Heap allocation (Xmx): 8 GB >Reporter: Mayank S >Priority: Major > Labels: performance > Fix For: 18.12.17 > > Original Estimate: 24h > Remaining Estimate: 24h > > While performance-testing Ofbiz 18 under high load (200 concurrent users), we > have observed an intermittent error, stating "null DispatchContext". > While doing more analysis, we realized it is a thread-safety issue, and it > was fixed by adding the 'synchronized' keyword to the following method > signatures in ServiceDispatcher.java: > public static synchronized getInstance (Delegator delegator) > public static synchronized void register (DispatchContext context) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
[ https://issues.apache.org/jira/browse/OFBIZ-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890340#comment-17890340 ] Jacques Le Roux commented on OFBIZ-13153: - Hi Mayank , As synchronizng a whole method can have side effects, I'd suggest to start a thread in [dev ML|https://ofbiz.apache.org/mailing-lists.html] before blindly applying this change to OOTB code, TIA > "null DispatchContext" issue under high load and concurrency > > > Key: OFBIZ-13153 > URL: https://issues.apache.org/jira/browse/OFBIZ-13153 > Project: OFBiz > Issue Type: Bug > Components: framework/service >Affects Versions: 18.12.16 > Environment: Virtual Machine: > OS: RHEL 8.9 > VCPU: 16 > Total RAM: 64 GB > Heap allocation (Xmx): 8 GB >Reporter: Mayank S >Priority: Major > Labels: performance > Fix For: 18.12.17 > > Original Estimate: 24h > Remaining Estimate: 24h > > While performance-testing Ofbiz 18 under high load (200 concurrent users), we > have observed an intermittent error, stating "null DispatchContext". > While doing more analysis, we realized it is a thread-safety issue, and it > was fixed by adding the 'synchronized' keyword to the following method > signatures in ServiceDispatcher.java: > public static synchronized getInstance (Delegator delegator) > public static synchronized void register (DispatchContext context) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13149) Example charts don't work
[ https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890338#comment-17890338 ] Jacques Le Roux commented on OFBIZ-13149: - Actually no, I tried to remove the uglification and it does not change anything > Example charts don't work > - > > Key: OFBIZ-13149 > URL: https://issues.apache.org/jira/browse/OFBIZ-13149 > Project: OFBiz > Issue Type: Bug > Components: example >Affects Versions: Upcoming Branch, 24.09 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 24.09.01 > > > In trunk and next demos example charts don't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-13149) Example charts don't work
[
https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890125#comment-17890125
]
Jacques Le Roux edited comment on OFBIZ-13149 at 10/17/24 6:42 AM:
---
Just as a comment to possibly help a perfectionist person :) :
The problem could be related to use of uglify on jquery.flot.min.js in
themes/common-theme/webapp/common-theme/js/package.json!
{color:#bed6ff}"scripts"{color}{color:#ff}:{color} {color:#ff}{{color}
{color:#bed6ff}"uglify"{color}{color:#ff}:{color} {color:#ffc600}"uglifyjs
node_modules/flot/dist/es5/jquery.flot.js -c -m -o
node_modules/flot/dist/es5/{color}{color:#ffc600}jquery.flot.min.js{color}{color:#ffc600}"{color}
}
But I don't see how that could be. Maybe a collision because jquery.flot.min.js
is already present?
was (Author: jacques.le.roux):
Just as a comment to possibly help some perfectionist person :) :
The problem could be related to use of uglify on jquery.flot.min.js in
themes/common-theme/webapp/common-theme/js/package.json!
{color:#bed6ff}"scripts"{color}{color:#ff}:{color} {color:#ff}{{color}
{color:#bed6ff}"uglify"{color}{color:#ff}:{color} {color:#ffc600}"uglifyjs
node_modules/flot/dist/es5/jquery.flot.js -c -m -o
node_modules/flot/dist/es5/{color}{color:#ffc600}jquery.flot.min.js{color}{color:#ffc600}"{color}
}
But I don't see how that could be. Maybe a collision because jquery.flot.min.js
is already present?
> Example charts don't work
> -
>
> Key: OFBIZ-13149
> URL: https://issues.apache.org/jira/browse/OFBIZ-13149
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Major
> Fix For: 24.09.01
>
>
> In trunk and next demos example charts don't work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (OFBIZ-13149) Example charts don't work
[ https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-13149. --- Fix Version/s: 24.09.01 Assignee: Jacques Le Roux Resolution: Fixed > Example charts don't work > - > > Key: OFBIZ-13149 > URL: https://issues.apache.org/jira/browse/OFBIZ-13149 > Project: OFBiz > Issue Type: Bug > Components: example >Affects Versions: Upcoming Branch, 24.09 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 24.09.01 > > > In trunk and next demos example charts don't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13149) Example charts don't work
[
https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890125#comment-17890125
]
Jacques Le Roux commented on OFBIZ-13149:
-
Just as a comment to possibly help some perfectionist person :) :
The problem could be related to use of uglify on jquery.flot.min.js in
themes/common-theme/webapp/common-theme/js/package.json!
{color:#bed6ff}"scripts"{color}{color:#ff}:{color} {color:#ff}{{color}
{color:#bed6ff}"uglify"{color}{color:#ff}:{color} {color:#ffc600}"uglifyjs
node_modules/flot/dist/es5/jquery.flot.js -c -m -o
node_modules/flot/dist/es5/{color}{color:#ffc600}jquery.flot.min.js{color}{color:#ffc600}"{color}
}
But I don't see how that could be. Maybe a collision because jquery.flot.min.js
is already present?
> Example charts don't work
> -
>
> Key: OFBIZ-13149
> URL: https://issues.apache.org/jira/browse/OFBIZ-13149
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Priority: Major
>
> In trunk and next demos example charts don't work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-13149) Example charts don't work
[ https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890121#comment-17890121 ] ASF subversion and git services commented on OFBIZ-13149: - Commit 2f1060c7264ba470a871bb9ed10ae5be4131d1ec in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=2f1060c726 ] Fixed: Example charts don't work (OFBIZ-13149) As I don't want to dive into complication and that works, simply reverts changes in both Bars.ftl and Pie.ftl from jquery.flot.min.js to jquery.flot.js to fix the issues. We can certainly do better, if you feel so, please do... That was part of commit b063216cde4139f88d66f83a5785cd465c9a4183: Improved: Use NPM with gradle to get external JS dependencies (OFBIZ-11960) Puts the Uglify script in package.json with an example of use for jquery.flot.js The size diff between jquery.flot.js and jquery.flot.min.js is only 2%, so it's more an example... Note: to run the Uglify task alone use "gradlew npm_run_uglify" > Example charts don't work > - > > Key: OFBIZ-13149 > URL: https://issues.apache.org/jira/browse/OFBIZ-13149 > Project: OFBiz > Issue Type: Bug > Components: example >Affects Versions: Upcoming Branch, 24.09 >Reporter: Jacques Le Roux >Priority: Major > > In trunk and next demos example charts don't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-11960) Use NPM with gradle to get external JS dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890122#comment-17890122 ] ASF subversion and git services commented on OFBIZ-11960: - Commit 2f1060c7264ba470a871bb9ed10ae5be4131d1ec in ofbiz-framework's branch refs/heads/release24.09 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=2f1060c726 ] Fixed: Example charts don't work (OFBIZ-13149) As I don't want to dive into complication and that works, simply reverts changes in both Bars.ftl and Pie.ftl from jquery.flot.min.js to jquery.flot.js to fix the issues. We can certainly do better, if you feel so, please do... That was part of commit b063216cde4139f88d66f83a5785cd465c9a4183: Improved: Use NPM with gradle to get external JS dependencies (OFBIZ-11960) Puts the Uglify script in package.json with an example of use for jquery.flot.js The size diff between jquery.flot.js and jquery.flot.min.js is only 2%, so it's more an example... Note: to run the Uglify task alone use "gradlew npm_run_uglify" > Use NPM with gradle to get external JS dependencies > --- > > Key: OFBIZ-11960 > URL: https://issues.apache.org/jira/browse/OFBIZ-11960 > Project: OFBiz > Issue Type: New Feature > Components: ALL APPLICATIONS >Affects Versions: Trunk, Upcoming Branch >Reporter: Aditya Sharma >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > As discussed > [here|https://lists.apache.org/thread.html/re16808eb5b1084f822c74194d23ca073dea4f4df443184f40f5f58c6%40%3Cdev.ofbiz.apache.org%3E], > use gradle-js-plugin to ease out managing the JavaScript dependencies. The > Gradle plugin allows us to automatically download the js libraries to the > user's system like the Gradle dependencies, so we no longer need to include > them with the package. It opens door to all the packages and modules > available at [npm registry|https://www.npmjs.com/]. Also, it can be clubbed > with Grunt or Gulp implementing tasks to minify external JS and CSS files > with the custom ones, see > [here|https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/faq.md#how-do-i-run-commands-provided-by-npm-packages]. > 1. Add > [gradle-node-plugin|https://github.com/node-gradle/gradle-node-plugin]: > Gradle plugin for integrating NodeJS in your build > 2. Create [NPM|https://www.npmjs.com/] package.json with JS dependencies in > webapp > 3. Use available tasks to install dependencies > > [https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/usage.md#executing-npm-tasks] > > > [https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/usage.md#configuring-the-plugin] > 4. Use the downloaded JS files in node_modules, updating the current path of > the JS files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13149) Example charts don't work
[ https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890114#comment-17890114 ] ASF subversion and git services commented on OFBIZ-13149: - Commit b2fdc8c2fecd075bf333561e63e7e63184f90c2a in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=b2fdc8c2fe ] Fixed: Example charts don't work (OFBIZ-13149) As I don't want to dive into complication and that works, simply reverts changes in both Bars.ftl and Pie.ftl from jquery.flot.min.js to jquery.flot.js to fix the issues. We can certainly do better, if you feel so, please do... That was part of commit b063216cde4139f88d66f83a5785cd465c9a4183: Improved: Use NPM with gradle to get external JS dependencies (OFBIZ-11960) Puts the Uglify script in package.json with an example of use for jquery.flot.js The size diff between jquery.flot.js and jquery.flot.min.js is only 2%, so it's more an example... Note: to run the Uglify task alone use "gradlew npm_run_uglify" > Example charts don't work > - > > Key: OFBIZ-13149 > URL: https://issues.apache.org/jira/browse/OFBIZ-13149 > Project: OFBiz > Issue Type: Bug > Components: example >Affects Versions: Upcoming Branch, 24.09 >Reporter: Jacques Le Roux >Priority: Major > > In trunk and next demos example charts don't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-11960) Use NPM with gradle to get external JS dependencies
[ https://issues.apache.org/jira/browse/OFBIZ-11960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890115#comment-17890115 ] ASF subversion and git services commented on OFBIZ-11960: - Commit b2fdc8c2fecd075bf333561e63e7e63184f90c2a in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=b2fdc8c2fe ] Fixed: Example charts don't work (OFBIZ-13149) As I don't want to dive into complication and that works, simply reverts changes in both Bars.ftl and Pie.ftl from jquery.flot.min.js to jquery.flot.js to fix the issues. We can certainly do better, if you feel so, please do... That was part of commit b063216cde4139f88d66f83a5785cd465c9a4183: Improved: Use NPM with gradle to get external JS dependencies (OFBIZ-11960) Puts the Uglify script in package.json with an example of use for jquery.flot.js The size diff between jquery.flot.js and jquery.flot.min.js is only 2%, so it's more an example... Note: to run the Uglify task alone use "gradlew npm_run_uglify" > Use NPM with gradle to get external JS dependencies > --- > > Key: OFBIZ-11960 > URL: https://issues.apache.org/jira/browse/OFBIZ-11960 > Project: OFBiz > Issue Type: New Feature > Components: ALL APPLICATIONS >Affects Versions: Trunk, Upcoming Branch >Reporter: Aditya Sharma >Assignee: Jacques Le Roux >Priority: Trivial > Fix For: Upcoming Branch > > > As discussed > [here|https://lists.apache.org/thread.html/re16808eb5b1084f822c74194d23ca073dea4f4df443184f40f5f58c6%40%3Cdev.ofbiz.apache.org%3E], > use gradle-js-plugin to ease out managing the JavaScript dependencies. The > Gradle plugin allows us to automatically download the js libraries to the > user's system like the Gradle dependencies, so we no longer need to include > them with the package. It opens door to all the packages and modules > available at [npm registry|https://www.npmjs.com/]. Also, it can be clubbed > with Grunt or Gulp implementing tasks to minify external JS and CSS files > with the custom ones, see > [here|https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/faq.md#how-do-i-run-commands-provided-by-npm-packages]. > 1. Add > [gradle-node-plugin|https://github.com/node-gradle/gradle-node-plugin]: > Gradle plugin for integrating NodeJS in your build > 2. Create [NPM|https://www.npmjs.com/] package.json with JS dependencies in > webapp > 3. Use available tasks to install dependencies > > [https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/usage.md#executing-npm-tasks] > > > [https://github.com/node-gradle/gradle-node-plugin/blob/master/docs/usage.md#configuring-the-plugin] > 4. Use the downloaded JS files in node_modules, updating the current path of > the JS files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13153) "null DispatchContext" issue under high load and concurrency
Mayank S created OFBIZ-13153: Summary: "null DispatchContext" issue under high load and concurrency Key: OFBIZ-13153 URL: https://issues.apache.org/jira/browse/OFBIZ-13153 Project: OFBiz Issue Type: Bug Components: framework/service Affects Versions: 18.12.16 Environment: Virtual Machine: OS: RHEL 8.9 VCPU: 16 Total RAM: 64 GB Heap allocation (Xmx): 8 GB Reporter: Mayank S Fix For: 18.12.17 While performance-testing Ofbiz 18 under high load (200 concurrent users), we have observed an intermittent error, stating "null DispatchContext". While doing more analysis, we realized it is a thread-safety issue, and it was fixed by adding the 'synchronized' keyword to the following method signatures in ServiceDispatcher.java: public static synchronized getInstance (Delegator delegator) public static synchronized void register (DispatchContext context) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13149) Example charts don't work
[ https://issues.apache.org/jira/browse/OFBIZ-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13149: Description: In trunk and next demos example charts don't work. (was: In trunk and next demos example charts don't work. It's related to [https://stackoverflow.com/questions/29345524/flot-charts-giving-plot-is-not-a-function.] ) > Example charts don't work > - > > Key: OFBIZ-13149 > URL: https://issues.apache.org/jira/browse/OFBIZ-13149 > Project: OFBiz > Issue Type: Bug > Components: example >Affects Versions: Upcoming Branch, 24.09 >Reporter: Jacques Le Roux >Priority: Major > > In trunk and next demos example charts don't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889987#comment-17889987 ] Jacques Le Roux commented on OFBIZ-13152: - Also, though it seems to be a Tomcat answer, the stack of errors in log would be quite interesting. > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: 20241009_112047.MP4 > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13152: Labels: (was: critical) > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Attachments: 20241009_112047.MP4 > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889986#comment-17889986 ] Jacques Le Roux commented on OFBIZ-13152: - Hi Arashpreet, please update the version you use (Affects Version/s: field) TIA > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Labels: critical > Attachments: 20241009_112047.MP4 > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
[ https://issues.apache.org/jira/browse/OFBIZ-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-13152: Component/s: rest-api (was: ALL APPLICATIONS) Priority: Major (was: Critical) > Inconsistent Error Handling for Entity Creation via Exported Service > > > Key: OFBIZ-13152 > URL: https://issues.apache.org/jira/browse/OFBIZ-13152 > Project: OFBiz > Issue Type: Bug > Components: rest-api >Reporter: Arashpreet Singh >Priority: Major > Labels: critical > Attachments: 20241009_112047.MP4 > > > There appears to be a problem with the OFBiz error-handling mechanism when > creating an entity using an exported service. Initially, if incorrect input > data is provided, OFBiz correctly returns a meaningful error message from the > backend. However, upon resubmitting the same request without any changes, > instead of returning the same meaningful error, the system responds with a > 500 internal server error and an HTML response. > Interestingly, when OFBiz is restarted, the first request with the same > incorrect data again returns a proper, meaningful error message. But all > subsequent requests with the same data continue to produce a 500 response, > which is not ideal for consistent error reporting. > This issue impacts debugging and error handling for services that rely on > accurate back-end responses. The expected behavior would be to consistently > return the meaningful error for all requests, regardless of whether OFBiz has > been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13152) Inconsistent Error Handling for Entity Creation via Exported Service
Arashpreet Singh created OFBIZ-13152: Summary: Inconsistent Error Handling for Entity Creation via Exported Service Key: OFBIZ-13152 URL: https://issues.apache.org/jira/browse/OFBIZ-13152 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Reporter: Arashpreet Singh Attachments: 20241009_112047.MP4 There appears to be a problem with the OFBiz error-handling mechanism when creating an entity using an exported service. Initially, if incorrect input data is provided, OFBiz correctly returns a meaningful error message from the backend. However, upon resubmitting the same request without any changes, instead of returning the same meaningful error, the system responds with a 500 internal server error and an HTML response. Interestingly, when OFBiz is restarted, the first request with the same incorrect data again returns a proper, meaningful error message. But all subsequent requests with the same data continue to produce a 500 response, which is not ideal for consistent error reporting. This issue impacts debugging and error handling for services that rely on accurate back-end responses. The expected behavior would be to consistently return the meaningful error for all requests, regardless of whether OFBiz has been restarted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OFBIZ-13151) Use Development Containers as development environments with necessary build tools already available
[ https://issues.apache.org/jira/browse/OFBIZ-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Watford reassigned OFBIZ-13151: -- Assignee: Daniel Watford > Use Development Containers as development environments with necessary build > tools already available > --- > > Key: OFBIZ-13151 > URL: https://issues.apache.org/jira/browse/OFBIZ-13151 > Project: OFBiz > Issue Type: Improvement > Components: tools >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > Development Containers are becoming a popular method of ensuring a > container-based development environment has all the tools needed by a > developer to work on a project. > Development Containers ([https://containers.dev/)] depend on the developer's > host system running a container runtime, such as Docker. They are supported > in IntelliJ and VS Code. > Inclusion of a Development Container configuration in the ofbiz-framework > sources will allow new developers to open their IDE with all development > tools - such as the correct version of Java SDK - already in place. This > should improve the on-boarding experience for new developers. > Outside of IDE integration, tools such as DevPod can be used to create and > run Development Containers targeting a project. Users can then SSH into the > container and carry out development tasks such as gradle builds. This might > be an integration point for IDEs that do not currently have support > Development Containers, such as Eclipse. > > Further reading: > [https://blog.jetbrains.com/idea/2024/07/using-dev-containers-in-jetbrains-ides-part-1/] > [https://github.com/JetBrains/devcontainers-examples] > [https://containers.dev/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13151) Use Development Containers as development environments with necessary build tools already available
[ https://issues.apache.org/jira/browse/OFBIZ-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889700#comment-17889700 ] Daniel Watford commented on OFBIZ-13151: I run bluefin-dx as my operating system (https://docs.projectbluefin.io/bluefin-dx). This is an image based build of Linux where the base layer of the system comes from an image published every week or so, and the majority of user-space applications come from flatpacks, brew and containers. To avoid installing lots of development tools in user-space, I have been using devcontainers in most of my projects for the last year. They are really useful for isolating development environments to avoid dependency clash. In the case of OFBiz, I think dev containers could be useful to isolate different versions of the java SDK or Node among branches. We can also add tools, such as Act, to test GitHub Action Workflows before pushing changes to the repository. > Use Development Containers as development environments with necessary build > tools already available > --- > > Key: OFBIZ-13151 > URL: https://issues.apache.org/jira/browse/OFBIZ-13151 > Project: OFBiz > Issue Type: Improvement > Components: tools >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Priority: Trivial > > Development Containers are becoming a popular method of ensuring a > container-based development environment has all the tools needed by a > developer to work on a project. > Development Containers ([https://containers.dev/)] depend on the developer's > host system running a container runtime, such as Docker. They are supported > in IntelliJ and VS Code. > Inclusion of a Development Container configuration in the ofbiz-framework > sources will allow new developers to open their IDE with all development > tools - such as the correct version of Java SDK - already in place. This > should improve the on-boarding experience for new developers. > Outside of IDE integration, tools such as DevPod can be used to create and > run Development Containers targeting a project. Users can then SSH into the > container and carry out development tasks such as gradle builds. This might > be an integration point for IDEs that do not currently have support > Development Containers, such as Eclipse. > > Further reading: > [https://blog.jetbrains.com/idea/2024/07/using-dev-containers-in-jetbrains-ides-part-1/] > [https://github.com/JetBrains/devcontainers-examples] > [https://containers.dev/] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OFBIZ-13151) Use Development Containers as development environments with necessary build tools already available
Daniel Watford created OFBIZ-13151: -- Summary: Use Development Containers as development environments with necessary build tools already available Key: OFBIZ-13151 URL: https://issues.apache.org/jira/browse/OFBIZ-13151 Project: OFBiz Issue Type: Improvement Components: tools Affects Versions: Upcoming Branch Reporter: Daniel Watford Development Containers are becoming a popular method of ensuring a container-based development environment has all the tools needed by a developer to work on a project. Development Containers ([https://containers.dev/)] depend on the developer's host system running a container runtime, such as Docker. They are supported in IntelliJ and VS Code. Inclusion of a Development Container configuration in the ofbiz-framework sources will allow new developers to open their IDE with all development tools - such as the correct version of Java SDK - already in place. This should improve the on-boarding experience for new developers. Outside of IDE integration, tools such as DevPod can be used to create and run Development Containers targeting a project. Users can then SSH into the container and carry out development tasks such as gradle builds. This might be an integration point for IDEs that do not currently have support Development Containers, such as Eclipse. Further reading: [https://blog.jetbrains.com/idea/2024/07/using-dev-containers-in-jetbrains-ides-part-1/] [https://github.com/JetBrains/devcontainers-examples] [https://containers.dev/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
[
https://issues.apache.org/jira/browse/OFBIZ-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889566#comment-17889566
]
Jacques Le Roux commented on OFBIZ-13150:
-
That could have an effect on other parts using copyIfRequiredSystemPage()
> example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but
> reports an error
> ---
>
> Key: OFBIZ-13150
> URL: https://issues.apache.org/jira/browse/OFBIZ-13150
> Project: OFBiz
> Issue Type: Bug
> Components: example
>Affects Versions: Upcoming Branch, 24.09
>Reporter: Jacques Le Roux
>Priority: Major
>
> The error is
> {quote}No signature of method:
> org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
> applicable for argument types: () values: []
> {quote}
> It's part of PortalPageServices.groovy and could be a consequence of
> OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (OFBIZ-13150) example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports an error
Jacques Le Roux created OFBIZ-13150:
---
Summary:
example/control/ManagePortalPages?parentPortalPageId=EXAMPLE works but reports
an error
Key: OFBIZ-13150
URL: https://issues.apache.org/jira/browse/OFBIZ-13150
Project: OFBiz
Issue Type: Bug
Components: example
Affects Versions: Upcoming Branch, 24.09
Reporter: Jacques Le Roux
The error is
{quote}No signature of method:
org.apache.ofbiz.common.PortalPageMethods.copyIfRequiredSystemPage() is
applicable for argument types: () values: []
{quote}
It's part of PortalPageServices.groovy and could be a consequence of
OFBIZ-13091
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
