[jira] [Updated] (OFBIZ-9796) Release Notes link on downloads page in OFBiz new website are not working for individual releases
[
https://issues.apache.org/jira/browse/OFBIZ-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Sharma updated OFBIZ-9796:
-
Attachment: screenshot-2.png
> Release Notes link on downloads page in OFBiz new website are not working for
> individual releases
> -
>
> Key: OFBIZ-9796
> URL: https://issues.apache.org/jira/browse/OFBIZ-9796
> Project: OFBiz
> Issue Type: Bug
>Reporter: Aditya Sharma
>Priority: Minor
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Steps:
> 1. Go to http://ofbiz.apache.org/index.html.
> 2. Select Downloads from the Community
> submenu.(http://ofbiz.apache.org/download.html)
> "Release Notes" links under individual releases are not working.
> Additional improvement should be following lines can be updated under
> {quote}Special Notice Regarding Branches 14.12 and 15.12{quote}
> {quote}Branches 14.12 and 15.12 will be supported until July 2017 and during
> this period bug fixes will be backported to them{quote}
> to
> {quote}Support for branches 14.12 and 15.12 had been provided till July
> 2017{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-9796) Release Notes link on downloads page in OFBiz new website are not working for individual releases
[
https://issues.apache.org/jira/browse/OFBIZ-9796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Sharma updated OFBIZ-9796:
-
Attachment: screenshot-1.png
> Release Notes link on downloads page in OFBiz new website are not working for
> individual releases
> -
>
> Key: OFBIZ-9796
> URL: https://issues.apache.org/jira/browse/OFBIZ-9796
> Project: OFBiz
> Issue Type: Bug
>Reporter: Aditya Sharma
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Steps:
> 1. Go to http://ofbiz.apache.org/index.html.
> 2. Select Downloads from the Community
> submenu.(http://ofbiz.apache.org/download.html)
> "Release Notes" links under individual releases are not working.
> Additional improvement should be following lines can be updated under
> {quote}Special Notice Regarding Branches 14.12 and 15.12{quote}
> {quote}Branches 14.12 and 15.12 will be supported until July 2017 and during
> this period bug fixes will be backported to them{quote}
> to
> {quote}Support for branches 14.12 and 15.12 had been provided till July
> 2017{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OFBIZ-9796) Release Notes link on downloads page in OFBiz new website are not working for individual releases
Aditya Sharma created OFBIZ-9796:
Summary: Release Notes link on downloads page in OFBiz new website
are not working for individual releases
Key: OFBIZ-9796
URL: https://issues.apache.org/jira/browse/OFBIZ-9796
Project: OFBiz
Issue Type: Bug
Reporter: Aditya Sharma
Priority: Minor
Steps:
1. Go to http://ofbiz.apache.org/index.html.
2. Select Downloads from the Community
submenu.(http://ofbiz.apache.org/download.html)
"Release Notes" links under individual releases are not working.
Additional improvement should be following lines can be updated under
{quote}Special Notice Regarding Branches 14.12 and 15.12{quote}
{quote}Branches 14.12 and 15.12 will be supported until July 2017 and during
this period bug fixes will be backported to them{quote}
to
{quote}Support for branches 14.12 and 15.12 had been provided till July
2017{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-9791) builds in git fail quickly
[ https://issues.apache.org/jira/browse/OFBIZ-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181364#comment-16181364 ] Jacques Le Roux commented on OFBIZ-9791: I see no reasons why you commit access would have stopped to work. > builds in git fail quickly > -- > > Key: OFBIZ-9791 > URL: https://issues.apache.org/jira/browse/OFBIZ-9791 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath > > Empty folders in git are not stored. Please make the build.gradle handle > missing folders. > The correct fix is to *NOT* store a README or something in the plugins/ > folder. > == > 10:43:01 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ > ./gradlew build > FAILURE: Build failed with an exception. > * Where: > Script '/srv/development/ofbiz/ofbiz-github/common.gradle' line: 37 > * What went wrong: > A problem occurred evaluating settings 'ofbiz'. > > /srv/development/ofbiz/ofbiz-github/plugins > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > BUILD FAILED > Total time: 0.415 secs > == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9791) builds in git fail quickly
[ https://issues.apache.org/jira/browse/OFBIZ-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181271#comment-16181271 ] Adam Heath commented on OFBIZ-9791: --- I have it fixed as I've suggested, but I'm also working on other integration changes. I also don't know if my commit access still works. I've since gotten a big fast new machine, so might have to configure some things again. > builds in git fail quickly > -- > > Key: OFBIZ-9791 > URL: https://issues.apache.org/jira/browse/OFBIZ-9791 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath > > Empty folders in git are not stored. Please make the build.gradle handle > missing folders. > The correct fix is to *NOT* store a README or something in the plugins/ > folder. > == > 10:43:01 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ > ./gradlew build > FAILURE: Build failed with an exception. > * Where: > Script '/srv/development/ofbiz/ofbiz-github/common.gradle' line: 37 > * What went wrong: > A problem occurred evaluating settings 'ofbiz'. > > /srv/development/ofbiz/ofbiz-github/plugins > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > BUILD FAILED > Total time: 0.415 secs > == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9791) builds in git fail quickly
[ https://issues.apache.org/jira/browse/OFBIZ-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181257#comment-16181257 ] Adam Heath commented on OFBIZ-9791: --- Basically, let's stop checking in empty folders into SVN. Let's stop checking in folders that only contain a single README or some such, that explains what goes in there. Then fix the build system and runtime to deal with that. > builds in git fail quickly > -- > > Key: OFBIZ-9791 > URL: https://issues.apache.org/jira/browse/OFBIZ-9791 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath > > Empty folders in git are not stored. Please make the build.gradle handle > missing folders. > The correct fix is to *NOT* store a README or something in the plugins/ > folder. > == > 10:43:01 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ > ./gradlew build > FAILURE: Build failed with an exception. > * Where: > Script '/srv/development/ofbiz/ofbiz-github/common.gradle' line: 37 > * What went wrong: > A problem occurred evaluating settings 'ofbiz'. > > /srv/development/ofbiz/ofbiz-github/plugins > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > BUILD FAILED > Total time: 0.415 secs > == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9791) builds in git fail quickly
[ https://issues.apache.org/jira/browse/OFBIZ-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181255#comment-16181255 ] Jacques Le Roux commented on OFBIZ-9791: Ah sorry, you spoke about inexisting folders, not empty folders. Seems even harder... > builds in git fail quickly > -- > > Key: OFBIZ-9791 > URL: https://issues.apache.org/jira/browse/OFBIZ-9791 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath > > Empty folders in git are not stored. Please make the build.gradle handle > missing folders. > The correct fix is to *NOT* store a README or something in the plugins/ > folder. > == > 10:43:01 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ > ./gradlew build > FAILURE: Build failed with an exception. > * Where: > Script '/srv/development/ofbiz/ofbiz-github/common.gradle' line: 37 > * What went wrong: > A problem occurred evaluating settings 'ofbiz'. > > /srv/development/ofbiz/ofbiz-github/plugins > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > BUILD FAILED > Total time: 0.415 secs > == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9791) builds in git fail quickly
[ https://issues.apache.org/jira/browse/OFBIZ-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181250#comment-16181250 ] Adam Heath commented on OFBIZ-9791: --- That's not the bug. common.gradle has *custom* code that attempts to do file.eachDir against a file that does not exist. That then throws an exception. It's easy to replicate. Do an svn checkout, then rm -rf plugins. > builds in git fail quickly > -- > > Key: OFBIZ-9791 > URL: https://issues.apache.org/jira/browse/OFBIZ-9791 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath > > Empty folders in git are not stored. Please make the build.gradle handle > missing folders. > The correct fix is to *NOT* store a README or something in the plugins/ > folder. > == > 10:43:01 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ > ./gradlew build > FAILURE: Build failed with an exception. > * Where: > Script '/srv/development/ofbiz/ofbiz-github/common.gradle' line: 37 > * What went wrong: > A problem occurred evaluating settings 'ofbiz'. > > /srv/development/ofbiz/ofbiz-github/plugins > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > BUILD FAILED > Total time: 0.415 secs > == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9791) builds in git fail quickly
[ https://issues.apache.org/jira/browse/OFBIZ-9791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181236#comment-16181236 ] Jacques Le Roux commented on OFBIZ-9791: Hi Adam, Found this only (I guess you did so) https://discuss.gradle.org/t/build-cache-issue-how-to-exclude-empty-directories-from-compile/22820 not sure how to do it... > builds in git fail quickly > -- > > Key: OFBIZ-9791 > URL: https://issues.apache.org/jira/browse/OFBIZ-9791 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath > > Empty folders in git are not stored. Please make the build.gradle handle > missing folders. > The correct fix is to *NOT* store a README or something in the plugins/ > folder. > == > 10:43:01 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ > ./gradlew build > FAILURE: Build failed with an exception. > * Where: > Script '/srv/development/ofbiz/ofbiz-github/common.gradle' line: 37 > * What went wrong: > A problem occurred evaluating settings 'ofbiz'. > > /srv/development/ofbiz/ofbiz-github/plugins > * Try: > Run with --stacktrace option to get the stack trace. Run with --info or > --debug option to get more log output. > BUILD FAILED > Total time: 0.415 secs > == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OFBIZ-9795) common.gradle doesn't support infinitely component-load.xml depth
[ https://issues.apache.org/jira/browse/OFBIZ-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Heath updated OFBIZ-9795: -- Description: ComponentContainer.java can look at component-load.xml in each and every component directory, and do that to infinite recursion. If a plugin is installed into ofbiz, it may also contain other nested components/plugins, but common.gradle doesn't handle that. (was: ComponentConfig.java can look at component-load.xml in each and every component directory, and do that to infinite recursion. If a plugin is installed into ofbiz, it may also contain other nested components/plugins, but common.gradle doesn't handle that.) > common.gradle doesn't support infinitely component-load.xml depth > - > > Key: OFBIZ-9795 > URL: https://issues.apache.org/jira/browse/OFBIZ-9795 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath >Priority: Minor > > ComponentContainer.java can look at component-load.xml in each and every > component directory, and do that to infinite recursion. If a plugin is > installed into ofbiz, it may also contain other nested components/plugins, > but common.gradle doesn't handle that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9795) common.gradle doesn't support infinitely component-load.xml depth
[ https://issues.apache.org/jira/browse/OFBIZ-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181081#comment-16181081 ] Adam Heath commented on OFBIZ-9795: --- The best fix for this, would be to have a start-of-day compile phase, that compiles framework/base. Then, using bits of code from there, parse the baseline files. This might require a refactor to allow for external access to ComponentContainer files. > common.gradle doesn't support infinitely component-load.xml depth > - > > Key: OFBIZ-9795 > URL: https://issues.apache.org/jira/browse/OFBIZ-9795 > Project: OFBiz > Issue Type: Bug > Components: Gradle >Affects Versions: Trunk >Reporter: Adam Heath >Priority: Minor > > ComponentConfig.java can look at component-load.xml in each and every > component directory, and do that to infinite recursion. If a plugin is > installed into ofbiz, it may also contain other nested components/plugins, > but common.gradle doesn't handle that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9794) Unable to run the MRP
[
https://issues.apache.org/jira/browse/OFBIZ-9794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181080#comment-16181080
]
Swapnil M Mane commented on OFBIZ-9794:
---
Firstly, thank you [~soledad] and team for the work we have done in creating a
common theme under https://issues.apache.org/jira/browse/OFBIZ-9138
It is highly appreciated!!
I suspect this VisualTheme Exception might be related to this.
Here is the Pony Mail link for this discussion -
https://lists.apache.org/thread.html/3d3ff409dea4947f5621e34cc5bec00f96fcfd1a491d9d16e5405bcd@%3Cdev.ofbiz.apache.org%3E
> Unable to run the MRP
> -
>
> Key: OFBIZ-9794
> URL: https://issues.apache.org/jira/browse/OFBIZ-9794
> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
>Affects Versions: Trunk
>Reporter: Swapnil M Mane
>
> I am facing some Exception related to VisualTheme while running the MRP.
> https://demo-trunk.ofbiz.apache.org/manufacturing/control/RunMrp
> {code}
> [[ASync service failed...- total:0.012,since last(ASync service
> sta...):0.012]] - 'manufacturing / executeMrp'
> 2017-09-23 11:44:24,458 |jsse-nio-8443-exec-6 |ServiceDispatcher
> |E| Service [executeMrp] threw an unexpected exception/error
> org.apache.ofbiz.service.GenericServiceException: Problem serializing service
> attributes (Cannot serialize object of class
> org.apache.ofbiz.widget.renderer.VisualTheme)
> at
> org.apache.ofbiz.service.engine.GenericAsyncEngine.runAsync(GenericAsyncEngine.java:124)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.service.engine.GenericAsyncEngine.runAsync(GenericAsyncEngine.java:70)
> ~[ofbiz.jar:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runAsync(ServiceDispatcher.java:715)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.ServiceDispatcher.runAsync(ServiceDispatcher.java:780)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runAsync(GenericDispatcherFactory.java:181)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runAsync(GenericDispatcherFactory.java:191)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.event.ServiceEventHandler.invoke(ServiceEventHandler.java:348)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.runEvent(RequestHandler.java:730)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:454)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
> [ofbiz.jar:?]
> at
> org.apache.ofbiz.webapp.control.ControlServlet.doPost(ControlServlet.java:87)
> [ofbiz.jar:?]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> [javax.servlet-api-3.1.0.jar:3.1.0]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> [javax.servlet-api-3.1.0.jar:3.1.0]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> [tomcat-embed-websocket-8.0.39.jar:8.0.39]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:196)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:157)
> [ofbiz.jar:?]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
> [tomcat-catalina-8.5.16.jar:8.5.16]
> at
>
[jira] [Created] (OFBIZ-9795) common.gradle doesn't support infinitely component-load.xml depth
Adam Heath created OFBIZ-9795: - Summary: common.gradle doesn't support infinitely component-load.xml depth Key: OFBIZ-9795 URL: https://issues.apache.org/jira/browse/OFBIZ-9795 Project: OFBiz Issue Type: Bug Components: Gradle Affects Versions: Trunk Reporter: Adam Heath Priority: Minor ComponentConfig.java can look at component-load.xml in each and every component directory, and do that to infinite recursion. If a plugin is installed into ofbiz, it may also contain other nested components/plugins, but common.gradle doesn't handle that. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OFBIZ-9794) Unable to run the MRP
Swapnil M Mane created OFBIZ-9794:
-
Summary: Unable to run the MRP
Key: OFBIZ-9794
URL: https://issues.apache.org/jira/browse/OFBIZ-9794
Project: OFBiz
Issue Type: Bug
Components: manufacturing
Affects Versions: Trunk
Reporter: Swapnil M Mane
I am facing some Exception related to VisualTheme while running the MRP.
https://demo-trunk.ofbiz.apache.org/manufacturing/control/RunMrp
{code}
[[ASync service failed...- total:0.012,since last(ASync service sta...):0.012]]
- 'manufacturing / executeMrp'
2017-09-23 11:44:24,458 |jsse-nio-8443-exec-6 |ServiceDispatcher
|E| Service [executeMrp] threw an unexpected exception/error
org.apache.ofbiz.service.GenericServiceException: Problem serializing service
attributes (Cannot serialize object of class
org.apache.ofbiz.widget.renderer.VisualTheme)
at
org.apache.ofbiz.service.engine.GenericAsyncEngine.runAsync(GenericAsyncEngine.java:124)
~[ofbiz.jar:?]
at
org.apache.ofbiz.service.engine.GenericAsyncEngine.runAsync(GenericAsyncEngine.java:70)
~[ofbiz.jar:?]
at
org.apache.ofbiz.service.ServiceDispatcher.runAsync(ServiceDispatcher.java:715)
[ofbiz.jar:?]
at
org.apache.ofbiz.service.ServiceDispatcher.runAsync(ServiceDispatcher.java:780)
[ofbiz.jar:?]
at
org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runAsync(GenericDispatcherFactory.java:181)
[ofbiz.jar:?]
at
org.apache.ofbiz.service.GenericDispatcherFactory$GenericDispatcher.runAsync(GenericDispatcherFactory.java:191)
[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.event.ServiceEventHandler.invoke(ServiceEventHandler.java:348)
[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.RequestHandler.runEvent(RequestHandler.java:730)
[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.RequestHandler.doRequest(RequestHandler.java:454)
[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.doGet(ControlServlet.java:212)
[ofbiz.jar:?]
at
org.apache.ofbiz.webapp.control.ControlServlet.doPost(ControlServlet.java:87)
[ofbiz.jar:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
[javax.servlet-api-3.1.0.jar:3.1.0]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
[javax.servlet-api-3.1.0.jar:3.1.0]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
[tomcat-embed-websocket-8.0.39.jar:8.0.39]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.ofbiz.webapp.control.ContextFilter.doFilter(ContextFilter.java:196)
[ofbiz.jar:?]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.ofbiz.webapp.control.ControlFilter.doFilter(ControlFilter.java:157)
[ofbiz.jar:?]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:624)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
[tomcat-catalina-8.5.16.jar:8.5.16]
at
[jira] [Created] (OFBIZ-9792) order services.xml references bi entities
Adam Heath created OFBIZ-9792: - Summary: order services.xml references bi entities Key: OFBIZ-9792 URL: https://issues.apache.org/jira/browse/OFBIZ-9792 Project: OFBiz Issue Type: Bug Components: bi, order Reporter: Adam Heath Priority: Minor Do a fresh checkout. No plugins(which uses to be specialpurpose). ofbiz/services.xml defines entity-auto services for entities that only exist in the bi plugin. == 10:55:15 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ ./gradlew loadDefault 2>&1 | tee loadDefault.log 10:55:38 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ less loadDefault.log 10:55:54 -0500 adam@tooz(trunk):/srv/development/ofbiz/ofbiz-github$ grep SalesOrderItemFact loadDefault.log org.apache.ofbiz.entity.GenericModelException: Could not find definition for entity name SalesOrderItemFact 2017-09-26 10:54:13,708 |kJoinPool-1-worker-7 |ModelServiceReader |E| Cannot load auto-attributes : Could not find entity with name [SalesOrderItemFact] for createSalesOrderItemFact org.apache.ofbiz.base.util.GeneralException: Could not find entity with name [SalesOrderItemFact] org.apache.ofbiz.entity.GenericModelException: Could not find definition for entity name SalesOrderItemFact == -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-9647) Missing Relationship from OrderHeader to WebSite
[ https://issues.apache.org/jira/browse/OFBIZ-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180859#comment-16180859 ] Rishi Solanki commented on OFBIZ-9647: -- [~upadhyay.ratnesh]: Thanks for your contribution, your patch has been committed in trunk revision 1809749. > Missing Relationship from OrderHeader to WebSite > > > Key: OFBIZ-9647 > URL: https://issues.apache.org/jira/browse/OFBIZ-9647 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: Rishi Solanki > Fix For: Upcoming Release > > Attachments: OFBIZ-9647.patch > > > OrderHeader entity have webSiteId field but there is no relationship defined > for it with WebSite entity. It must have FK constraint from > OrderHeader.webSiteId to WebSite.webSiteId. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OFBIZ-9647) Missing Relationship from OrderHeader to WebSite
[ https://issues.apache.org/jira/browse/OFBIZ-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rishi Solanki resolved OFBIZ-9647. -- Resolution: Fixed Fix Version/s: Upcoming Release > Missing Relationship from OrderHeader to WebSite > > > Key: OFBIZ-9647 > URL: https://issues.apache.org/jira/browse/OFBIZ-9647 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk >Reporter: Ratnesh Upadhyay >Assignee: Rishi Solanki > Fix For: Upcoming Release > > Attachments: OFBIZ-9647.patch > > > OrderHeader entity have webSiteId field but there is no relationship defined > for it with WebSite entity. It must have FK constraint from > OrderHeader.webSiteId to WebSite.webSiteId. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OFBIZ-6655) Add session tracking mode and make cookie secure
[
https://issues.apache.org/jira/browse/OFBIZ-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180818#comment-16180818
]
Jacques Le Roux commented on OFBIZ-6655:
I'll commit these patches in a week, please review, thanks
> Add session tracking mode and make cookie secure
>
>
> Key: OFBIZ-6655
> URL: https://issues.apache.org/jira/browse/OFBIZ-6655
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk, 14.12.01
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIA-6655.applications.patch,
> OFBIZ-6655.framework_themes.patch,
> OFBIZ-6655-programmatically-session-cookies-plugins.patch,
> OFBIZ-6655-programmatically-session-cookies-trunk.patch,
> OFBIZ-6655_specialpurpose_leftover.patch, sessionConifg_ecommerce.patch
>
>
> Need to enhance security at web-app level.
> As per current implementation:
> - The cookie containing the session identifier is not secure
> - The session identifier is transmitted in the query string of the URL
> To fix these issue we have to add following session config otpions in web.xml
> {code}
>
>
> true
> true
>
> COOKIE
>
> {code}
> Also we need to update the web-app servlet specification from 2.3 to 3.0
> {code}
> xmlns="http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;>
> {code}
> https://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OFBIZ-6655) Add session tracking mode and make cookie secure
[
https://issues.apache.org/jira/browse/OFBIZ-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180789#comment-16180789
]
Jacques Le Roux commented on OFBIZ-6655:
Thanks for your review Pradhan (and not Yash as I used in dev ML, sorry)
> Add session tracking mode and make cookie secure
>
>
> Key: OFBIZ-6655
> URL: https://issues.apache.org/jira/browse/OFBIZ-6655
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk, 14.12.01
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIA-6655.applications.patch,
> OFBIZ-6655.framework_themes.patch,
> OFBIZ-6655-programmatically-session-cookies-plugins.patch,
> OFBIZ-6655-programmatically-session-cookies-trunk.patch,
> OFBIZ-6655_specialpurpose_leftover.patch, sessionConifg_ecommerce.patch
>
>
> Need to enhance security at web-app level.
> As per current implementation:
> - The cookie containing the session identifier is not secure
> - The session identifier is transmitted in the query string of the URL
> To fix these issue we have to add following session config otpions in web.xml
> {code}
>
>
> true
> true
>
> COOKIE
>
> {code}
> Also we need to update the web-app servlet specification from 2.3 to 3.0
> {code}
> xmlns="http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;>
> {code}
> https://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OFBIZ-9725) Transaction Timeout in JavaEventHandler
[
https://issues.apache.org/jira/browse/OFBIZ-9725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-9725.
--
Resolution: Fixed
Fix Version/s: 16.11.04
Thanks for your detailled report Jeffrey,
I have fixed the issue (more a quiproquo) in trunk at revision: 1809741 by
adding an indication of the limited duration for services run this way. For
longer services, as you did, sheduling a job is the way. Sorry, I have no
intent of prodiving a way to shedule them using a Temporal Expression. But I'll
provide the enhanced way in OFBIZ-9726
Tough it could be done in older releases, I only backported in R16.11 at
r1809742
> Transaction Timeout in JavaEventHandler
> ---
>
> Key: OFBIZ-9725
> URL: https://issues.apache.org/jira/browse/OFBIZ-9725
> Project: OFBiz
> Issue Type: Bug
> Components: framework/webtools
>Affects Versions: Release Branch 14.12, Release Branch 16.11
> Environment: Red Hat Enterprise Linux, release branch 14.12
> Ubuntu 17.04, release branch 16.11.03
>Reporter: Jeffrey Breault
>Assignee: Jacques Le Roux
> Fix For: 16.11.04
>
> Attachments: management-trunk.zip, management.zip, ofbiz.log,
> shortLog.log, TestingServices.java
>
>
> I have a service that is scheduled using the webtools scheduler.
> I am attempting to use the following service definition
> {noformat}
> require-new-transaction="true"
> location="my.package" invoke="myCustomService" auth="true">
> Run this very long function
>
> {noformat}
> The function in question is getting data from an oracle database and
> sanitizing the records and then inserting them into a postgresql database.
> There are millions of records in the oracle database and I am grabbing the
> records in batches of 200, sanitizing them then committing them using a
> GenericValue.create() method. This continues for 100 iterations.
> Using verbose logging we have the following log messages to indicate that the
> transaction timeout is being used...
> {noformat}
> 2017-09-15 06:30:48,372 |http-bio-8443-exec-8 |ServiceDispatcher
> |D| [ServiceDispatcher.runSync] : invoking service myCustomService
> [my.package/myCustomService] (java)
> 2017-09-15 06:30:48,372 |http-bio-8443-exec-8 |TransactionUtil
> |D| Current status : No Transaction (6)
> 2017-09-15 06:30:48,372 |http-bio-8443-exec-8 |TransactionUtil
> |D| Set transaction timeout to : 36000 seconds
> 2017-09-15 06:30:48,372 |http-bio-8443-exec-8 |TransactionUtil
> |D| Transaction begun
> {noformat}
> {noformat}
> 2017-09-15 06:49:36,444 |http-bio-8443-exec-4 |MigrationServices
> |I| Ending myCustomService ::: 2017-09-15T06:49:36.444
> 2017-09-15 06:49:36,444 |http-bio-8443-exec-4 |ModelService
> |D| [ModelService.validate] : {myCustomService} : Validating context -
> {responseMessage=success}
> 2017-09-15 06:49:36,444 |http-bio-8443-exec-4 |ModelService
> |D| [ModelService.validate] : required fields -
> 2017-09-15 06:49:36,444 |http-bio-8443-exec-4 |ModelService
> |D| [ModelService.validate] : {myCustomService} : (OUT) Required - 0 / 0
> 2017-09-15 06:49:36,444 |http-bio-8443-exec-4 |ModelService
> |D| [ModelService.validate] : {myCustomService} : (OUT) Optional - 1 / 8
> 2017-09-15 06:49:36,444 |http-bio-8443-exec-4 |TransactionUtil
> |D| Current status : Transaction Active (0)
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |TransactionUtil
> |D| Transaction committed
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |Converters
> |D| Getting converter: java.lang.String->java.lang.Long
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |Converters
> |D| Getting converter: java.lang.String->java.lang.Long
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |ServiceDispatcher
> |T| Sync service [webtools/myCustomService] finished in [552515] milliseconds
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |ServiceDispatcher
> |D| Sync service [webtools/myCustomService] finished with response
> [{responseMessage=success}]
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |JavaEventHandler
> |D| [Event Return]: sync_success
> 2017-09-15 06:49:36,482 |http-bio-8443-exec-4 |TransactionUtil
> |D| Current status : Transaction Active (0)
> 2017-09-15 06:49:36,491 |http-bio-8443-exec-4 |TransactionUtil
> |W| In getSetRollbackOnlyCause no stack placeholder was in place, here is the
> current location:
> java.lang.Exception: Current Stack Trace
> at
> org.ofbiz.entity.transaction.TransactionUtil.getSetRollbackOnlyCause(TransactionUtil.java:840)
>
[jira] [Created] (OFBIZ-9790) Billing account entity does not have support to manage the history of contact mech
Vaibhav Jain created OFBIZ-9790: --- Summary: Billing account entity does not have support to manage the history of contact mech Key: OFBIZ-9790 URL: https://issues.apache.org/jira/browse/OFBIZ-9790 Project: OFBiz Issue Type: Improvement Reporter: Vaibhav Jain Billing account entity has a field named "contactMechId". Actual: 1. We can update the postal address of billing account but we do not have the history of a postal address. 2. If contact mech of billing account is updated then we do not have the history of last billing account contact mech. Expected : 1. We should have the history of billing account. 2. we can introduce new entity "BillingAccountContactMech" where we can manage the history of billing account contact mech. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OFBIZ-6655) Add session tracking mode and make cookie secure
[
https://issues.apache.org/jira/browse/OFBIZ-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180420#comment-16180420
]
Jacques Le Roux edited comment on OFBIZ-6655 at 9/26/17 8:43 AM:
-
Thanks Jacques,
was (Author: deepak.dixit):
Thanks Jaacques,
> Add session tracking mode and make cookie secure
>
>
> Key: OFBIZ-6655
> URL: https://issues.apache.org/jira/browse/OFBIZ-6655
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk, 14.12.01
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIA-6655.applications.patch,
> OFBIZ-6655.framework_themes.patch,
> OFBIZ-6655-programmatically-session-cookies-plugins.patch,
> OFBIZ-6655-programmatically-session-cookies-trunk.patch,
> OFBIZ-6655_specialpurpose_leftover.patch, sessionConifg_ecommerce.patch
>
>
> Need to enhance security at web-app level.
> As per current implementation:
> - The cookie containing the session identifier is not secure
> - The session identifier is transmitted in the query string of the URL
> To fix these issue we have to add following session config otpions in web.xml
> {code}
>
>
> true
> true
>
> COOKIE
>
> {code}
> Also we need to update the web-app servlet specification from 2.3 to 3.0
> {code}
> xmlns="http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;>
> {code}
> https://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OFBIZ-6655) Add session tracking mode and make cookie secure
[
https://issues.apache.org/jira/browse/OFBIZ-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-6655:
---
Attachment: OFBIZ-6655-programmatically-session-cookies-plugins.patch
OFBIZ-6655-programmatically-session-cookies-trunk.patch
I have attached 2 patches (trunk and plugin) to programmatically replaces the
web.xml declarations and uses the @WebListener annotation to
start the process. This avoid to duplicates things everywhere in web.xml files.
Since the web.xml files have precedence on annotations, the setting can be
easily overriden when necessary.
Now that we also use HTTPS in ecommerce the ecommerce session cookie is also
secured.
I also noted that we have 8 weird declarations:
* in solr component: 2
* in themes: 1
Does somebody know why?
Also in Rainbowstone we lack the and
declarations. I think it's not good.
We can easily resolve these points by simply removing the in
web.xml files of themes and Solr. Without answers that's what I'll do.
> Add session tracking mode and make cookie secure
>
>
> Key: OFBIZ-6655
> URL: https://issues.apache.org/jira/browse/OFBIZ-6655
> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL COMPONENTS
>Affects Versions: Trunk, 14.12.01
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: 14.12.01, 15.12.01
>
> Attachments: OFBIA-6655.applications.patch,
> OFBIZ-6655.framework_themes.patch,
> OFBIZ-6655-programmatically-session-cookies-plugins.patch,
> OFBIZ-6655-programmatically-session-cookies-trunk.patch,
> OFBIZ-6655_specialpurpose_leftover.patch, sessionConifg_ecommerce.patch
>
>
> Need to enhance security at web-app level.
> As per current implementation:
> - The cookie containing the session identifier is not secure
> - The session identifier is transmitted in the query string of the URL
> To fix these issue we have to add following session config otpions in web.xml
> {code}
>
>
> true
> true
>
> COOKIE
>
> {code}
> Also we need to update the web-app servlet specification from 2.3 to 3.0
> {code}
> xmlns="http://java.sun.com/xml/ns/javaee;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>
> http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;>
> {code}
> https://tomcat.apache.org/whichversion.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
