[jira] [Commented] (OFBIZ-6915) Upgrade Tomcat to 8.0.33
[
https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244096#comment-15244096
]
Chatree Srichart commented on OFBIZ-6915:
-
I see that these classes are in tomcat-8.0.33-tomcat-util-scan.jar :
{quote}
org.apache.tomcat.util.descriptor.web.FilterDef
org.apache.tomcat.util.descriptor.web.FilterMap
org.apache.tomcat.util.scan.StandardJarScanner
{quote}
so we need it.
I see that tomcat-8.0.33-tomcat-jni.jar is also needed, otherwise this
exception will be occurred :
{quote}
[java] Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/tomcat/jni/LibraryNotFoundError
[java] at
org.apache.catalina.connector.Connector.setProtocol(Connector.java:564)
[java] at org.apache.catalina.connector.Connector.(Connector.java:66)
[java] at
org.ofbiz.catalina.container.CatalinaContainer.createConnector(CatalinaContainer.java:442)
{quote}
I see that tomcat-util.jar of Tomcat 7 is also not in extras.
https://archive.apache.org/dist/tomcat/tomcat-7/v7.0.65/bin/extras/
It is a default library.
https://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html
also in version 8
https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html
https://archive.apache.org/dist/tomcat/tomcat-8/v8.0.33/bin/extras/
> Upgrade Tomcat to 8.0.33
>
>
> Key: OFBIZ-6915
> URL: https://issues.apache.org/jira/browse/OFBIZ-6915
> Project: OFBiz
> Issue Type: Sub-task
> Components: framework
>Affects Versions: Trunk
> Environment: Ubuntu 14.04
>Reporter: Chatree Srichart
>Assignee: Jacques Le Roux
> Fix For: 15.12.01
>
> Attachments: tomcat-8.0.32-libs.zip, tomcat-8.0.33-libs.zip,
> upgrade_tomcat_to_8.0.32.patch, upgrade_tomcat_to_8.0.33.patch,
> upgrade_tomcat_to_8.0.33.status
>
>
> I am working on a library which requires Tomcat 8 but it cannot work on the
> current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat
> to version 8? I also provides a patch and libraries for Tomcat 8.0.32.
> Migrating from 7.0.x to 8.0.x
> https://tomcat.apache.org/migration-8.html
> Tomcat 8 Security
> https://tomcat.apache.org/security-8.html
> Tomcat 8 Changelog
> http://tomcat.apache.org/tomcat-8.0-doc/changelog.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238831#comment-15238831 ] Chatree Srichart commented on OFBIZ-6915: - Thanks Jacques :) > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart >Assignee: Jacques Le Roux > Fix For: Upcoming Branch, 15.12.01 > > Attachments: tomcat-8.0.32-libs.zip, tomcat-8.0.33-libs.zip, > upgrade_tomcat_to_8.0.32.patch, upgrade_tomcat_to_8.0.33.patch, > upgrade_tomcat_to_8.0.33.status > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. > Migrating from 7.0.x to 8.0.x > https://tomcat.apache.org/migration-8.html > Tomcat 8 Security > https://tomcat.apache.org/security-8.html > Tomcat 8 Changelog > http://tomcat.apache.org/tomcat-8.0-doc/changelog.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-6915: Attachment: tomcat-8.0.33-libs.zip upgrade_tomcat_to_8.0.33.status upgrade_tomcat_to_8.0.33.patch Hi Jacques, The issue "StringIndexOutOfBoundsException: String index out of range: 3" is a bug reported to Tomcat 8.0.32. [Bug 58999] - StringIndexOutOfBoundsException WebAppClassLoaderBase.filter() https://bz.apache.org/bugzilla/show_bug.cgi?id=58999 [Bug 59013] - In 8.0.32, WebappClassLoaderBase.filter throws StringIndexOutOfBoundsException for "org" https://bz.apache.org/bugzilla/show_bug.cgi?id=59013 Fortunately, it has already been fixed in Tomcat 8.0.33. http://tomcat.apache.org/tomcat-8.0-doc/changelog.html So, I provides a patch and libraries (attached) again for upgrading to Tomcat 8.0.33 which passed the 2 tests (testTextMacroLibrary and testCsvMacroLibrary) already. > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart >Assignee: Jacques Le Roux > Attachments: tomcat-8.0.32-libs.zip, tomcat-8.0.33-libs.zip, > upgrade_tomcat_to_8.0.32.patch, upgrade_tomcat_to_8.0.33.patch, > upgrade_tomcat_to_8.0.33.status > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. > Migrating from 7.0.x to 8.0.x > https://tomcat.apache.org/migration-8.html > Tomcat 8 Security > https://tomcat.apache.org/security-8.html > Tomcat 8 Changelog > http://tomcat.apache.org/tomcat-8.0-doc/changelog.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200052#comment-15200052 ] Chatree Srichart commented on OFBIZ-6915: - Hi Jacques, I also get those issues. I will find out more. Thanks! > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart >Assignee: Jacques Le Roux > Attachments: tomcat-8.0.32-libs.zip, upgrade_tomcat_to_8.0.32.patch > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. > Migrating from 7.0.x to 8.0.x > https://tomcat.apache.org/migration-8.html > Tomcat 8 Security > https://tomcat.apache.org/security-8.html > Tomcat 8 Changelog > http://tomcat.apache.org/tomcat-8.0-doc/changelog.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-6915: Description: I am working on a library which requires Tomcat 8 but it cannot work on the current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat to version 8? I also provides a patch and libraries for Tomcat 8.0.32. Migrating from 7.0.x to 8.0.x https://tomcat.apache.org/migration-8.html Tomcat 8 Security https://tomcat.apache.org/security-8.html Tomcat 8 Changelog http://tomcat.apache.org/tomcat-8.0-doc/changelog.html was:I am working on a library which requires Tomcat 8 but it cannot work on the current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat to version 8? I also provides a patch and libraries for Tomcat 8.0.32. > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Wish > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart > Attachments: tomcat-8.0.32-libs.zip, upgrade_tomcat_to_8.0.32.patch > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. > Migrating from 7.0.x to 8.0.x > https://tomcat.apache.org/migration-8.html > Tomcat 8 Security > https://tomcat.apache.org/security-8.html > Tomcat 8 Changelog > http://tomcat.apache.org/tomcat-8.0-doc/changelog.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159300#comment-15159300 ] Chatree Srichart edited comment on OFBIZ-6915 at 2/23/16 5:56 PM: -- This zip file contains Tomcat 8.0.32 libraries which would be used to replace existing Tomcat 7.0.65 libraries. D framework/base/lib/j2eespecs/servlet-api-3.0.jar A framework/base/lib/j2eespecs/servlet-api-3.1.jar D framework/catalina/lib/tomcat-7.0.65-catalina-ha.jar D framework/catalina/lib/tomcat-7.0.65-catalina-tribes.jar D framework/catalina/lib/tomcat-7.0.65-catalina.jar D framework/catalina/lib/tomcat-7.0.65-jasper.jar D framework/catalina/lib/tomcat-7.0.65-tomcat-api.jar D framework/catalina/lib/tomcat-7.0.65-tomcat-coyote.jar D framework/catalina/lib/tomcat-7.0.65-tomcat-juli-adapters.jar A framework/catalina/lib/tomcat-8.0.32-catalina-ha.jar A framework/catalina/lib/tomcat-8.0.32-catalina-tribes.jar A framework/catalina/lib/tomcat-8.0.32-catalina.jar A framework/catalina/lib/tomcat-8.0.32-jasper.jar A framework/catalina/lib/tomcat-8.0.32-tomcat-api.jar A framework/catalina/lib/tomcat-8.0.32-tomcat-coyote.jar A framework/catalina/lib/tomcat-8.0.32-tomcat-jni.jar A framework/catalina/lib/tomcat-8.0.32-tomcat-util-scan.jar A framework/catalina/lib/tomcat-8.0.32-tomcat-util.jar D framework/catalina/lib/tomcat-extras-7.0.65-tomcat-juli.jar D framework/catalina/lib/tomcat-extras-7.0.65-tomcat-util.jar A framework/catalina/lib/tomcat-extras-8.0.32-tomcat-juli-adapters.jar A framework/catalina/lib/tomcat-extras-8.0.32-tomcat-juli.jar was (Author: chatree): This zip file contains Tomcat 8.0.32 libraries. > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Wish > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart > Attachments: tomcat-8.0.32-libs.zip, upgrade_tomcat_to_8.0.32.patch > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-6915: Attachment: tomcat-8.0.32-libs.zip This zip file contains Tomcat 8.0.32 libraries. > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Wish > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart > Attachments: tomcat-8.0.32-libs.zip, upgrade_tomcat_to_8.0.32.patch > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
[ https://issues.apache.org/jira/browse/OFBIZ-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-6915: Attachment: upgrade_tomcat_to_8.0.32.patch This is a patch to upgrade Tomcat to 8.0.32. > Upgrade Tomcat to 8.0.32 > > > Key: OFBIZ-6915 > URL: https://issues.apache.org/jira/browse/OFBIZ-6915 > Project: OFBiz > Issue Type: Wish > Components: framework >Affects Versions: Trunk > Environment: Ubuntu 14.04 >Reporter: Chatree Srichart > Attachments: upgrade_tomcat_to_8.0.32.patch > > > I am working on a library which requires Tomcat 8 but it cannot work on the > current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat > to version 8? I also provides a patch and libraries for Tomcat 8.0.32. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6915) Upgrade Tomcat to 8.0.32
Chatree Srichart created OFBIZ-6915: --- Summary: Upgrade Tomcat to 8.0.32 Key: OFBIZ-6915 URL: https://issues.apache.org/jira/browse/OFBIZ-6915 Project: OFBiz Issue Type: Wish Components: framework Affects Versions: Trunk Environment: Ubuntu 14.04 Reporter: Chatree Srichart I am working on a library which requires Tomcat 8 but it cannot work on the current trunk which is using Tomcat 7. Would it be possible to upgrade Tomcat to version 8? I also provides a patch and libraries for Tomcat 8.0.32. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5876) 404 error with birt previews.
[ https://issues.apache.org/jira/browse/OFBIZ-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14229146#comment-14229146 ] Chatree Srichart commented on OFBIZ-5876: - Hi Jacques, I see that there are some Jira issues already mentioned about this problem, OFBIZ-4849 and OFBIZ-5070 . The problem is R12.04 still has yuicompressor library which conflict with BIRT. REL-12.04.05/framework/base/lib/yuicompressor-2.4.6.jar Just remove yuicompressor library, the problem will be sovled. Best Regards, Chatree Srichart 404 error with birt previews. - Key: OFBIZ-5876 URL: https://issues.apache.org/jira/browse/OFBIZ-5876 Project: OFBiz Issue Type: Bug Components: specialpurpose/birt Affects Versions: Trunk Reporter: Francis Douet Assignee: Jacques Le Roux Labels: birt Fix For: Upcoming Branch Attachments: LICENSE.patch, commons-discovery-0.5.jar When trying to display birt previews, a 404 error is displayed. Example can be found here: http://demo-trunk-ofbiz.apache.org/scrum/control/ViewProduct?productId=DEMO-PRODUCT-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5876) 404 error with birt previews.
[ https://issues.apache.org/jira/browse/OFBIZ-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-5876: Attachment: LICENSE.patch Update LICENSE file by adding commons-discovery-0.5.jar to birt component. 404 error with birt previews. - Key: OFBIZ-5876 URL: https://issues.apache.org/jira/browse/OFBIZ-5876 Project: OFBiz Issue Type: Bug Components: specialpurpose/birt Affects Versions: Trunk Reporter: Francis Douet Labels: birt Attachments: LICENSE.patch When trying to display birt previews, a 404 error is displayed. Example can be found here: http://demo-trunk-ofbiz.apache.org/scrum/control/ViewProduct?productId=DEMO-PRODUCT-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-5876) 404 error with birt previews.
[ https://issues.apache.org/jira/browse/OFBIZ-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-5876: Attachment: commons-discovery-0.5.jar Commons Discovery component, commons-discovery-0.5.jar, need to be added to [OFBIZ_HOME]/specialpurpose/birt/lib/ directory. 404 error with birt previews. - Key: OFBIZ-5876 URL: https://issues.apache.org/jira/browse/OFBIZ-5876 Project: OFBiz Issue Type: Bug Components: specialpurpose/birt Affects Versions: Trunk Reporter: Francis Douet Labels: birt Attachments: LICENSE.patch, commons-discovery-0.5.jar When trying to display birt previews, a 404 error is displayed. Example can be found here: http://demo-trunk-ofbiz.apache.org/scrum/control/ViewProduct?productId=DEMO-PRODUCT-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-5876) 404 error with birt previews.
[ https://issues.apache.org/jira/browse/OFBIZ-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221849#comment-14221849 ] Chatree Srichart commented on OFBIZ-5876: - Hi Jacques, It seems BIRT view servlet requires commons-discovery library which has been removed at r1623042. Is it possible to get it back or download commons-discovery version 0.5 which directly depends on BIRT runtime version 4.3.1. http://mvnrepository.com/artifact/org.eclipse.birt.runtime/viewservlets/4.3.1 http://mvnrepository.com/artifact/commons-discovery/commons-discovery/0.5 Best Regards, Chatree Srichart 404 error with birt previews. - Key: OFBIZ-5876 URL: https://issues.apache.org/jira/browse/OFBIZ-5876 Project: OFBiz Issue Type: Bug Components: specialpurpose/birt Affects Versions: Trunk Reporter: Francis Douet Labels: birt When trying to display birt previews, a 404 error is displayed. Example can be found here: http://demo-trunk-ofbiz.apache.org/scrum/control/ViewProduct?productId=DEMO-PRODUCT-1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13941611#comment-13941611 ] Chatree Srichart commented on OFBIZ-4952: - Thanks Jacques, Enjoy on BIRT! Best Regards, BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937930#comment-13937930 ] Chatree Srichart commented on OFBIZ-4952: - Hi Jacques, I have already written on wiki. https://cwiki.apache.org/confluence/display/OFBIZ/Using+BIRT+with+OFBiz Could you please verify if it correct? Please let me know if I missed something. Best Regards, BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936151#comment-13936151 ] Chatree Srichart commented on OFBIZ-4952: - Sure! Could I write on this page? https://cwiki.apache.org/confluence/display/OFBIZ/Using+BIRT+with+OFBiz BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936162#comment-13936162 ] Chatree Srichart commented on OFBIZ-4952: - Well, my information is: Name: Chatree Srichart email: chatree.srich...@gmail.com Company: - Location: Chiang Mai, Thailand Wiki username: chatree Thanks! Best Regards, BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936181#comment-13936181 ] Chatree Srichart commented on OFBIZ-4952: - Thank You Best Regards, BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894389#comment-13894389 ] Chatree Srichart commented on OFBIZ-4952: - Thanks Jacques! BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (OFBIZ-5530) Upgrade BIRT Runtime to 4.3.1
Chatree Srichart created OFBIZ-5530: --- Summary: Upgrade BIRT Runtime to 4.3.1 Key: OFBIZ-5530 URL: https://issues.apache.org/jira/browse/OFBIZ-5530 Project: OFBiz Issue Type: Improvement Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Upgrade BIRT runtime libraries to version 4.3.1 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (OFBIZ-5530) Upgrade BIRT Runtime to 4.3.1
[ https://issues.apache.org/jira/browse/OFBIZ-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-5530: Attachment: birt.patch I provide patch to update classpath and license files. Actually I have one more zip file with size 45.81 MB. Unfortunately, it is too big to upload. Upgrade BIRT Runtime to 4.3.1 - Key: OFBIZ-5530 URL: https://issues.apache.org/jira/browse/OFBIZ-5530 Project: OFBiz Issue Type: Improvement Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt Attachments: birt.patch Upgrade BIRT runtime libraries to version 4.3.1 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (OFBIZ-5530) Upgrade BIRT Runtime to 4.3.1
[ https://issues.apache.org/jira/browse/OFBIZ-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13893431#comment-13893431 ] Chatree Srichart commented on OFBIZ-5530: - Please download a zip file of [OFBIZ_PATH]/specialpurpose/birt/lib directory here. http://www.mediafire.com/download/yiz3539db7i22vo/lib.zip Upgrade BIRT Runtime to 4.3.1 - Key: OFBIZ-5530 URL: https://issues.apache.org/jira/browse/OFBIZ-5530 Project: OFBiz Issue Type: Improvement Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt Attachments: birt.patch Upgrade BIRT runtime libraries to version 4.3.1 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892274#comment-13892274 ] Chatree Srichart commented on OFBIZ-4952: - Hi Jacques, In my experience, some of jar files are related. If we update some of them, they might conflict to others. What I did was I updated all jar files which were from the same version of BIRT runtime . I don't know whether the files you want to update are related to others or not. So, the save way is to update all files which are from the same version of BIRT runtime . I am glad to know you would be interested to continue on BIRT. Best Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892274#comment-13892274 ] Chatree Srichart edited comment on OFBIZ-4952 at 2/5/14 4:21 PM: - Hi Jacques, In my experience, some of jar files are related. If we update some of them, they might conflict to others. What I did was I updated all jar files which were from the same version of BIRT runtime . I don't know whether the files you want to update are related to others or not. So, the safe way is to update all files which are from the same version of BIRT runtime . I am glad to know you would be interested to continue on BIRT. Best Regards, Chatree Srichart was (Author: chatree): Hi Jacques, In my experience, some of jar files are related. If we update some of them, they might conflict to others. What I did was I updated all jar files which were from the same version of BIRT runtime . I don't know whether the files you want to update are related to others or not. So, the save way is to update all files which are from the same version of BIRT runtime . I am glad to know you would be interested to continue on BIRT. Best Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892292#comment-13892292 ] Chatree Srichart commented on OFBIZ-4952: - Sure. I will take care of that. BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: OFBIZ-4952 error stack.log, birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4952: Attachment: birt_viewer.jpg Hi Jacques, I am sorry for the late reply. Could you have a look at the attached image which is what I am thinking about? I don't think this is a good design but it might be easier for user to view the report file. Best Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772962#comment-13772962 ] Chatree Srichart commented on OFBIZ-4952: - Users can type a report location in a text box then press a view button. Then BIRT Viewer page will be displayed as iframe at the bottom. BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772970#comment-13772970 ] Chatree Srichart commented on OFBIZ-4952: - Hi Jacques, I haven't implemented it yet. I think opening a new browser tab or window might bring a user out of perception. If you think it would be better then fine. I am quite busy at the moment. I will fine out a change to implement it. Best Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772983#comment-13772983 ] Chatree Srichart commented on OFBIZ-4952: - The BIRT online help is not up to date. I used to show an example BIRT report within iframe. However, The HTML report is a HTML page by itself. BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_viewer.jpg, birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761247#comment-13761247 ] Chatree Srichart commented on OFBIZ-4952: - Hi Jacques, For the user point of view, BIRT Web Viewer provides many options to play over the report: - Showing table of content - Changing report's parameters over AJAX dialog - Exporting data by selecting required columns - Exporting report with many options - Printing report - AJAX pagination For the developer point if view, they can test the report that they are working on by just specify report's path on the address bar, don't need to create request map, view map, screen for testing. For testing, they might change values of parameters often, so that they don't need to wait the whole page reloaded anytime they change the parameter's values. Sure, these features could be done by OFBiz screen but there is no one implement it yet. If so, he/she might need to spend so much of power to do to get it work the same as BIRT Web Viewer works. Best Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749351#comment-13749351 ] Chatree Srichart commented on OFBIZ-4952: - As I mention in the description, after you unzip birt-runtime-3_7_2.zip file, you will have webcontent directory in birt-runtime-3_7_2/WebViewerExample. Then, you copy the webcontent directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/birt/webapp/birt). So, you can now use the BIRT viewer. http://localhost:8080/birt/frameset?__report=component://birt/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://birt/webapp/birt/report/chart.rptdesign I am not sure if the patch will solve other problems. This path is just helpful if a user want to use BIRT web viwer. Best Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749316#comment-13749316 ] Chatree Srichart commented on OFBIZ-4952: - Hi Jacques, I have just tested my patch again and it still works fine. I used BIRT Runtime 3.7.2 which contains FramesetFragment.jsp file. You can download the birt rumtime here. http://www.eclipse.org/downloads/download.php?file=/birt/downloads/drops/R-R1-3_7_2-201202141408/birt-runtime-3_7_2.zip I tested these URLs: http://localhost:8080/birt/frameset?__report=component://birt/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://birt/webapp/birt/report/chart.rptdesign Best Regards, Chatree Sricharat BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4952: Attachment: birt_web_content.png Screenshot to show that FramesetFragment.jsp is in the webcontent directory. BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Assignee: Jacques Le Roux Labels: birt, viewer Fix For: SVN trunk Attachments: birt_web_content.png, birt_web_viewer.patch, birt_web_viewer.patch, OFBIZ-4952 error stack.log Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-5135) services_quote.xml#quoteSequence-enforced method is not facet-valid with respect to pattern
Chatree Srichart created OFBIZ-5135: --- Summary: services_quote.xml#quoteSequence-enforced method is not facet-valid with respect to pattern Key: OFBIZ-5135 URL: https://issues.apache.org/jira/browse/OFBIZ-5135 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Environment: Ubuntu 11.04 Reporter: Chatree Srichart Fix For: SVN trunk Hi all, I got an error message: Error message: cvc-attribute.3: The value 'quoteSequence-enforced' of attribute 'method-name' on element 'simple-method' is not valid with respect to its type, 'javaClassName'. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-5135) services_quote.xml#quoteSequence-enforced method is not facet-valid with respect to pattern
[ https://issues.apache.org/jira/browse/OFBIZ-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-5135: Attachment: quoteSequence-enforced.patch services_quote.xml#quoteSequence-enforced method is not facet-valid with respect to pattern --- Key: OFBIZ-5135 URL: https://issues.apache.org/jira/browse/OFBIZ-5135 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Environment: Ubuntu 11.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: quoteSequence-enforced.patch Original Estimate: 24h Remaining Estimate: 24h Hi all, I got an error message: Error message: cvc-attribute.3: The value 'quoteSequence-enforced' of attribute 'method-name' on element 'simple-method' is not valid with respect to its type, 'javaClassName'. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-5133) The createDataResourceRole service does not check if partyId exists
Chatree Srichart created OFBIZ-5133: --- Summary: The createDataResourceRole service does not check if partyId exists Key: OFBIZ-5133 URL: https://issues.apache.org/jira/browse/OFBIZ-5133 Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Hi all, The createDataResourceRole service has a partyId attribute as optional but its implementation method does not check if the partyId exists before creating a DataResourceRole value. The ensurePartyRole service also has a partyId attribute as optional but its implementation method does not check if the partyId exists before creating a PartyRole value. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-5133) The createDataResourceRole service does not check if partyId exists
[ https://issues.apache.org/jira/browse/OFBIZ-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-5133: Attachment: party_role_problem.patch The createDataResourceRole service does not check if partyId exists --- Key: OFBIZ-5133 URL: https://issues.apache.org/jira/browse/OFBIZ-5133 Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Attachments: party_role_problem.patch Original Estimate: 24h Remaining Estimate: 24h Hi all, The createDataResourceRole service has a partyId attribute as optional but its implementation method does not check if the partyId exists before creating a DataResourceRole value. The ensurePartyRole service also has a partyId attribute as optional but its implementation method does not check if the partyId exists before creating a PartyRole value. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-5066) Upgrade PDFBox to 1.7.1
Chatree Srichart created OFBIZ-5066: --- Summary: Upgrade PDFBox to 1.7.1 Key: OFBIZ-5066 URL: https://issues.apache.org/jira/browse/OFBIZ-5066 Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Fix For: SVN trunk Hi All, I have got a problem about missing image in reader/image output which relate to PDFBOX-1416 issue. However, the problem will be solved by upgrading PDFBox to 1.7.1. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-5044) The loadDateDimension service is loading incorrect weekOfYear field.
Chatree Srichart created OFBIZ-5044: --- Summary: The loadDateDimension service is loading incorrect weekOfYear field. Key: OFBIZ-5044 URL: https://issues.apache.org/jira/browse/OFBIZ-5044 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Hi all, When I ran the loadDateDimension service with these dates: - fromDate = 25 Dec 2010 - thruDate = 05 Jan 2011 I got: - 25 Dec 2010 has the week of year as 52. - 26 Dec 2010 has the week of year as 1. Actually 26 Dec 2010 should has the week of year as 53. I think the problem is 26 Dec 2010 is in the same week of 1 Jan 2011. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4844) Fields in extended entity do not override attribute enable-audit-log
[
https://issues.apache.org/jira/browse/OFBIZ-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chatree Srichart updated OFBIZ-4844:
Attachment: audit_log.patch
I attached a patch file to enable the extended entity to be able to override
the enable-audit-log field.
Fields in extended entity do not override attribute enable-audit-log
Key: OFBIZ-4844
URL: https://issues.apache.org/jira/browse/OFBIZ-4844
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: SVN trunk
Environment: n/a
Reporter: Adam Kozak
Assignee: Jacques Le Roux
Attachments: audit_log.patch
Original Estimate: 10m
Remaining Estimate: 10m
When extending existing entity and overriding fields attribute
'enable-audit-log' is not overriden. Suggested patch in ModelEntity.java:
if (UtilValidate.isNotEmpty(field.getDescription())) {
existingField.setDescription(field.getDescription());
}
+ existingField.enableAuditLog =
UtilXml.checkBoolean(fieldElement.getAttribute(enable-audit-log),
existingField.enableAuditLog);
} else {
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-5018) LoginWorker does not check a base permission for the root mount point
Chatree Srichart created OFBIZ-5018: --- Summary: LoginWorker does not check a base permission for the root mount point Key: OFBIZ-5018 URL: https://issues.apache.org/jira/browse/OFBIZ-5018 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Hi, I get a problem with webapp's base permission defined in an ofbiz-component.xml do not work if the webapp uses the root mount point (/). The problem is LoginWorker does not check a base permission from the root mount point. Please find out the attached patch file to solve the problem. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-5018) LoginWorker does not check a base permission for the root mount point
[ https://issues.apache.org/jira/browse/OFBIZ-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-5018: Attachment: login_base_permission.patch LoginWorker does not check a base permission for the root mount point - Key: OFBIZ-5018 URL: https://issues.apache.org/jira/browse/OFBIZ-5018 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Labels: login, permission Fix For: SVN trunk Attachments: login_base_permission.patch Original Estimate: 48h Remaining Estimate: 48h Hi, I get a problem with webapp's base permission defined in an ofbiz-component.xml do not work if the webapp uses the root mount point (/). The problem is LoginWorker does not check a base permission from the root mount point. Please find out the attached patch file to solve the problem. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4980) Custom Quantity for Product Config Component
Chatree Srichart created OFBIZ-4980: --- Summary: Custom Quantity for Product Config Component Key: OFBIZ-4980 URL: https://issues.apache.org/jira/browse/OFBIZ-4980 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Fix For: SVN trunk Hi all, Would it be better to allow a customer to be able to custom a quantity of selected product config component. For example, Configurable PC, a customer could be able to input a quantity of RAM he/she want. Currently, the quantity of product config component is defined in ProductConfigProduct entity. Could we improve ProductConfigWorker class to get the quantity from parameter as well? Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4952: Attachment: birt_web_viewer.patch Hi Jacques, I have already created a new patch for the birt component in specialpurpose directory. For testing the example URLs will be: http://localhost:8080/birt/frameset?__report=component://birt/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://birt/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_web_viewer.patch, birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4968) compare-field/ does not work with defined default type.
Chatree Srichart created OFBIZ-4968: --- Summary: compare-field/ does not work with defined default type. Key: OFBIZ-4968 URL: https://issues.apache.org/jira/browse/OFBIZ-4968 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Hello, I cannot register into the ecommerce site https://demo-trunk.ofbiz.apache.org:8443/ecommerce I got this error message: 'Type specified for compare not supported.'. I think it is from this line of code: compare-field operator=equals field=PASSWORDfail-property resource=PartyUiLabels property=PartyPasswordMatchError//compare-field There is not the type attribute defined in the compare-field/ which it could be set a default value of simple-methods-v2.xsd but it does not. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4952) BIRT Web Viewer Integration
Chatree Srichart created OFBIZ-4952: --- Summary: BIRT Web Viewer Integration Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: birt_web_viewer.patch Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4952) BIRT Web Viewer Integration
[ https://issues.apache.org/jira/browse/OFBIZ-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4952: Attachment: birt_web_viewer.patch BIRT Web Viewer Integration --- Key: OFBIZ-4952 URL: https://issues.apache.org/jira/browse/OFBIZ-4952 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 12.04 Reporter: Chatree Srichart Labels: birt, viewer Fix For: SVN trunk Attachments: birt_web_viewer.patch Original Estimate: 0.05h Remaining Estimate: 0.05h Hello all, I have created a patch to solve a viewer servlet problem and uncomment the viewer servlet in the birt webapp. To do this will allow a user to use BIRT Web Viewer to render a report by coping a webcontent directory from birt-runtime-x_x_x/WebViewerExample directory and paste into the birt webapp directory ($OFBIZ_HOME/specialpurpose/example/webapp/birt). These are URLs to render example reports using BIRT Web Viewer. http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/example.rptdesign http://localhost:8080/birt/frameset?__report=component://example/webapp/birt/report/chart.rptdesign Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4934) Ignore tenant data files if the multitenant property is N
[ https://issues.apache.org/jira/browse/OFBIZ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4934: Attachment: tenant_reader.diff Update the patch to check if the reader name is tenant and the multitenant property is N then ignore loading the data file. Ignore tenant data files if the multitenant property is N - Key: OFBIZ-4934 URL: https://issues.apache.org/jira/browse/OFBIZ-4934 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Labels: tenant Fix For: SVN trunk Attachments: tenant_reader.diff, tenant_reader.patch Original Estimate: 72h Remaining Estimate: 72h Hello, I think the system does not need to load tenant data files if the multitenant property in general.properties is N. I created a patch to ignore the tenant data files when run ./ant load-demo command. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4934) Ignore tenant data files if the multitenant property is N
[ https://issues.apache.org/jira/browse/OFBIZ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4934: Attachment: tenant_reader.patch Ignore tenant data files if the multitenant property is N - Key: OFBIZ-4934 URL: https://issues.apache.org/jira/browse/OFBIZ-4934 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Labels: tenant Fix For: SVN trunk Attachments: tenant_reader.patch, tenant_reader.patch Original Estimate: 72h Remaining Estimate: 72h Hello, I think the system does not need to load tenant data files if the multitenant property in general.properties is N. I created a patch to ignore the tenant data files when run ./ant load-demo command. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4934) Ignore tenant data files if the multitenant property is N
[ https://issues.apache.org/jira/browse/OFBIZ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4934: Attachment: (was: tenant_reader.diff) Ignore tenant data files if the multitenant property is N - Key: OFBIZ-4934 URL: https://issues.apache.org/jira/browse/OFBIZ-4934 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Labels: tenant Fix For: SVN trunk Attachments: tenant_reader.patch, tenant_reader.patch Original Estimate: 72h Remaining Estimate: 72h Hello, I think the system does not need to load tenant data files if the multitenant property in general.properties is N. I created a patch to ignore the tenant data files when run ./ant load-demo command. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4934) Ignore tenant data files if the multitenant property is N
Chatree Srichart created OFBIZ-4934: --- Summary: Ignore tenant data files if the multitenant property is N Key: OFBIZ-4934 URL: https://issues.apache.org/jira/browse/OFBIZ-4934 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Hello, I think the system does not need to load tenant data files if the multitenant property in general.properties is N. I created a patch to ignore the tenant data files when run ./ant load-demo command. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4934) Ignore tenant data files if the multitenant property is N
[ https://issues.apache.org/jira/browse/OFBIZ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4934: Attachment: tenant_reader.patch Ignore tenant data files if the multitenant property is N - Key: OFBIZ-4934 URL: https://issues.apache.org/jira/browse/OFBIZ-4934 Project: OFBiz Issue Type: Improvement Components: humanres Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Labels: tenant Fix For: SVN trunk Attachments: tenant_reader.patch Original Estimate: 72h Remaining Estimate: 72h Hello, I think the system does not need to load tenant data files if the multitenant property in general.properties is N. I created a patch to ignore the tenant data files when run ./ant load-demo command. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4926) renderLookupField macro: get a form element by ID instead of Name
[ https://issues.apache.org/jira/browse/OFBIZ-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290851#comment-13290851 ] Chatree Srichart commented on OFBIZ-4926: - Better do not commit the patch yet because it will not help for me if the alert() still show. Let me find another solution. However, if you think it will be useful for the framework that is fine. Regards, Chatree Srichart renderLookupField macro: get a form element by ID instead of Name - Key: OFBIZ-4926 URL: https://issues.apache.org/jira/browse/OFBIZ-4926 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: lookup.patch Original Estimate: 168h Remaining Estimate: 168h Hello all, We have a problem to render a lookup field in a form element without a name attribute. We need to improve a lookup field because if we render the field without form or different form then the lookup field doesn't work, so we will change the lookup field by not get a from element by a name attribute but get by an id attribute. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4926) renderLookupField macro: get a form element by ID instead of Name
[
https://issues.apache.org/jira/browse/OFBIZ-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290724#comment-13290724
]
Chatree Srichart commented on OFBIZ-4926:
-
Hello Jacques,
I am sorry to make you confuse. I think I make confusing with my description.
Let me correct myself.
What I would like to change the renderLookupField macro is changing the
reference to the lookup element:
from: document.${formName}.${fieldName}
to: document.getElementById(${id}) which id is an id attribute of the
lookup element.
because sometimes I want to render the lookup field without form element.
To change this will not cause a problem with the lookup fields which already
used in the system because there always be id for the lookup fields.
Regards,
Chatree Srichart
renderLookupField macro: get a form element by ID instead of Name
-
Key: OFBIZ-4926
URL: https://issues.apache.org/jira/browse/OFBIZ-4926
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: SVN trunk
Environment: Ubuntu 10.04
Reporter: Chatree Srichart
Fix For: SVN trunk
Attachments: lookup.patch
Original Estimate: 168h
Remaining Estimate: 168h
Hello all,
We have a problem to render a lookup field in a form element without a name
attribute.
We need to improve a lookup field because if we render the field without form
or different form then the lookup field doesn't work, so we will change the
lookup field by not get a from element by a name attribute but get by an
id attribute.
Regards,
Chatree Srichart
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4926) renderLookupField macro: get a form element by ID instead of Name
Chatree Srichart created OFBIZ-4926: --- Summary: renderLookupField macro: get a form element by ID instead of Name Key: OFBIZ-4926 URL: https://issues.apache.org/jira/browse/OFBIZ-4926 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Hello all, We have a problem to render a lookup field in a form element without a name attribute. We need to improve a lookup field because if we render the field without form or different form then the lookup field doesn't work, so we will change the lookup field by not get a from element by a name attribute but get by an id attribute. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4926) renderLookupField macro: get a form element by ID instead of Name
[ https://issues.apache.org/jira/browse/OFBIZ-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4926: Attachment: lookup.patch renderLookupField macro: get a form element by ID instead of Name - Key: OFBIZ-4926 URL: https://issues.apache.org/jira/browse/OFBIZ-4926 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: lookup.patch Original Estimate: 168h Remaining Estimate: 168h Hello all, We have a problem to render a lookup field in a form element without a name attribute. We need to improve a lookup field because if we render the field without form or different form then the lookup field doesn't work, so we will change the lookup field by not get a from element by a name attribute but get by an id attribute. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4849) YUI Compressor conflict with BIRT
Chatree Srichart created OFBIZ-4849: --- Summary: YUI Compressor conflict with BIRT Key: OFBIZ-4849 URL: https://issues.apache.org/jira/browse/OFBIZ-4849 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart I got a problem when I entered an example report which has been created using BIRT https://demo-trunk.ofbiz.apache.org:8443/example/control/Report I got an error message: Invalid javascript expression: dataSetRow[exampleId] This is a Mozilla JavaScript problem. Actually BIRT has a proper library for that, framework/birt/lib/js.jar, but it is conflicted by YUI Compressor library, framework/base/lib/yuicompressor-2.4.6.jar . If I take the YUI Compressor library out then the example report works fine. I see that in the YUI Compressor library contains org.mozilla.javascript package which duplicate with BIRT but I think it is different version. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4845) Apache Commons Compress is missing for Tika
[ https://issues.apache.org/jira/browse/OFBIZ-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4845: Attachment: commons-compress-1.4.jar Apache Commons Compress is missing for Tika --- Key: OFBIZ-4845 URL: https://issues.apache.org/jira/browse/OFBIZ-4845 Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Attachments: commons-compress-1.4.jar Original Estimate: 3h Remaining Estimate: 3h I got a problem when I called createDataResource service for a zip file. 421240 [http-bio-0.0.0.0-8443-exec-2] ERROR org.ofbiz.service.group.GroupModel - Grouped service [createDataResource] failed. 421240 [http-bio-0.0.0.0-8443-exec-2] ERROR org.ofbiz.service.ServiceDispatcher - Error in Service [createContentFromUploadedFile]: ERROR: Could not complete the Create a Data Resource [file:/path/to/ofbiz/applications/content/script/org/ofbiz/content/data/DataServices.xml#createDataResource] process [Method to execute named getMimeTypeWithByteBuffer threw an exception: java.lang.NoClassDefFoundError: org/apache/commons/compress/archivers/zip/ZipFile] The problem was OFBiz is missing Apache Commons Compress library which is required for Tika. When I added commons-compress-1.4.jar into framework/base/lib/commons directory then it worked. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4845) Apache Commons Compress is missing for Tika
Chatree Srichart created OFBIZ-4845: --- Summary: Apache Commons Compress is missing for Tika Key: OFBIZ-4845 URL: https://issues.apache.org/jira/browse/OFBIZ-4845 Project: OFBiz Issue Type: Bug Components: content Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Attachments: commons-compress-1.4.jar I got a problem when I called createDataResource service for a zip file. 421240 [http-bio-0.0.0.0-8443-exec-2] ERROR org.ofbiz.service.group.GroupModel - Grouped service [createDataResource] failed. 421240 [http-bio-0.0.0.0-8443-exec-2] ERROR org.ofbiz.service.ServiceDispatcher - Error in Service [createContentFromUploadedFile]: ERROR: Could not complete the Create a Data Resource [file:/path/to/ofbiz/applications/content/script/org/ofbiz/content/data/DataServices.xml#createDataResource] process [Method to execute named getMimeTypeWithByteBuffer threw an exception: java.lang.NoClassDefFoundError: org/apache/commons/compress/archivers/zip/ZipFile] The problem was OFBiz is missing Apache Commons Compress library which is required for Tika. When I added commons-compress-1.4.jar into framework/base/lib/commons directory then it worked. Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (OFBIZ-4337) HttpClient does not support UTF-8
HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4337) HttpClient does not support UTF-8
[ https://issues.apache.org/jira/browse/OFBIZ-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4337: Attachment: HttpClient.patch The patch file to encode the stream to UTF-8 before writing out. HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical Attachments: HttpClient.patch, HttpClient.patch Original Estimate: 1h Remaining Estimate: 1h I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4337) HttpClient does not support UTF-8
[ https://issues.apache.org/jira/browse/OFBIZ-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4337: Attachment: HttpClient.patch HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical Attachments: HttpClient.patch, HttpClient.patch Original Estimate: 1h Remaining Estimate: 1h I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OFBIZ-4337) HttpClient does not support UTF-8
[ https://issues.apache.org/jira/browse/OFBIZ-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13063270#comment-13063270 ] Chatree Srichart commented on OFBIZ-4337: - I have tried to encode the stream before posting but it didn't work. This is my code: ... ... Charset charset = Charset.forName(UTF-8); String content = httpClient.post(new String(stream.getBytes(charset))); ... ... Regards, Chatree Srichart HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical Attachments: HttpClient.patch, HttpClient.patch Original Estimate: 1h Remaining Estimate: 1h I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4337) HttpClient does not support UTF-8
[ https://issues.apache.org/jira/browse/OFBIZ-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4337: Attachment: (was: HttpClient.patch) HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical Original Estimate: 1h Remaining Estimate: 1h I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4337) HttpClient does not support UTF-8
[ https://issues.apache.org/jira/browse/OFBIZ-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4337: Attachment: (was: HttpClient.patch) HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical Original Estimate: 1h Remaining Estimate: 1h I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4337) HttpClient does not support UTF-8
[ https://issues.apache.org/jira/browse/OFBIZ-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4337: Attachment: HttpClient.patch Hi Scott, Your approach is work fine for me. I re-attach a patch for that but I changed a bit for the variable's name. I see in the Java Doc for the OutputStreamWriter class use charset as lower case, http://download.oracle.com/javase/6/docs/api/java/io/OutputStreamWriter.html#OutputStreamWriter%28java.io.OutputStream,%20java.lang.String%29 . So, my patch is using streamCharset instead of streamCharSet. Regards, Chatree Srichart HttpClient does not support UTF-8 - Key: OFBIZ-4337 URL: https://issues.apache.org/jira/browse/OFBIZ-4337 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Priority: Critical Attachments: HttpClient.patch Original Estimate: 1h Remaining Estimate: 1h I tried to send XML message includes Thai character using HttpClient.post(stream) method but the receiver got an unexpect character replaced to the Thai character has been sent. If I encode the stream using UTF-8 then it works fine. I have attached the patch file to solve this problem. Please commit the patch if it is useful for OFBiz. Regards, Chatree Srichart -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: (was: webservice.zip) New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker Attachments: webservice.tar.bz2 This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL:
[jira] Created: (OFBIZ-4129) BIRT set output file name
BIRT set output file name - Key: OFBIZ-4129 URL: https://issues.apache.org/jira/browse/OFBIZ-4129 Project: OFBiz Issue Type: Improvement Components: framework Environment: Ubuntu 10.04 Reporter: Chatree Srichart Hi community, I get a request to export a BIRT report as PDF file with custom file name. I attach a patch file for this feature. Could you please check and commit it? Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4129) BIRT set output file name
[ https://issues.apache.org/jira/browse/OFBIZ-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4129: Attachment: birtSetOutputFileName.patch BIRT set output file name - Key: OFBIZ-4129 URL: https://issues.apache.org/jira/browse/OFBIZ-4129 Project: OFBiz Issue Type: Improvement Components: framework Environment: Ubuntu 10.04 Reporter: Chatree Srichart Attachments: birtSetOutputFileName.patch Original Estimate: 2h Remaining Estimate: 2h Hi community, I get a request to export a BIRT report as PDF file with custom file name. I attach a patch file for this feature. Could you please check and commit it? Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4109) Pagination is not working for the Entity Reference
Pagination is not working for the Entity Reference --- Key: OFBIZ-4109 URL: https://issues.apache.org/jira/browse/OFBIZ-4109 Project: OFBiz Issue Type: Bug Components: framework Environment: Ubuntu 10.04 Reporter: Chatree Srichart I got an error when I use a pagination at Webtools Entity Reference. It look like the pagination is not working. I also didn't see an entity name on a title of the entity section when I use the Tomahawk theme. Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-4072) Duplicate _LAST_VIEW_NAME_ query string in renderLookupField macro
Duplicate _LAST_VIEW_NAME_ query string in renderLookupField macro -- Key: OFBIZ-4072 URL: https://issues.apache.org/jira/browse/OFBIZ-4072 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk In the trunk version, I found a problem in renderLookupField macro concerning to duplicating the _LAST_VIEW_NAME_ query string. This problem causes the request handler cannot convert _LAST_VIEW_NAME_ parameter to String because it would be List. You can use FireBug to check it when the main screen of catalog website be loaded for the first time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4072) Duplicate _LAST_VIEW_NAME_ query string in renderLookupField macro
[ https://issues.apache.org/jira/browse/OFBIZ-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4072: Attachment: htmlFormMacroLibrary.diff I created Diff file to solve this problem by checking the _LAST_VIEW_NAME_ query string before append to the ajaxUrl variable Duplicate _LAST_VIEW_NAME_ query string in renderLookupField macro -- Key: OFBIZ-4072 URL: https://issues.apache.org/jira/browse/OFBIZ-4072 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: htmlFormMacroLibrary.diff Original Estimate: 2h Remaining Estimate: 2h In the trunk version, I found a problem in renderLookupField macro concerning to duplicating the _LAST_VIEW_NAME_ query string. This problem causes the request handler cannot convert _LAST_VIEW_NAME_ parameter to String because it would be List. You can use FireBug to check it when the main screen of catalog website be loaded for the first time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4055) Change Contact List Subscription Process
[ https://issues.apache.org/jira/browse/OFBIZ-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4055: Attachment: contactlist.patch I created a email template for contact list's communication event. The email template consists of a subscribe email address and a unsubscribe button. The people who receive email message can know which email address that they subscribed for a contact list and feel easy to unsubscribe the contact list from the email message. Regards, Chatree Srichart Change Contact List Subscription Process Key: OFBIZ-4055 URL: https://issues.apache.org/jira/browse/OFBIZ-4055 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: contactlist.patch, ean.vcf I think the current contact list subscription process is not complete. The current process is when a user enter his/her email address on the e-commerce page for subscribing a contact list. The system will set ContactListParty's status to Accepted. I think that should be set to Pending Acceptance first and wait for a user's confirmation from user's email inbox. Also the system should have a unsubscribe process to expire user's email address from a contact list. I found the unsubscribe statuses in StatusItem entity, Unsubscription pending and Unsubscribed, but they don't be used. I think the processes should following: Subscribe process === 1. The user select a contact list and enter his/her email address 2. The system create a ContactListParty with Pending Acceptance status 3. The system send a verify email message to the user's email address 4. The user confirm the subscribing in his/her email inbox 5. The system change the status of ContactListParty to Accepted Unsubscribe process 1. The use select a contact list and enter his/her email address 2. The system change the status of ContactListParty to Unsubscription pending 3. The system send a verify email message to the user's email address 4. The user confirm the unsubscribing in his/her email inbox 5. The system change the status of ContactListParty to Unsubscribed The both of processes, subscribe and unsubscribe, should also support if the user do not login to the system. I changed following: - create Subscribe Contact List Notification and Unsubscribe Contact List Verify as email type for email settings of product store - create signOutForContactList service for setting a contact list party's status to CLPT_UNSUBS_PENDING - create updateContactListPartyNoUserLogin service to handle updating the contact list party without user login - create sendContactListPartySubscribeEmail service for sending an email message to user after the user confirm the subscription. This email message would contains a button for requesting unsubscribe the contact list - create sendContactListPartyUnSubscribeVerifyEmail service for sending an email message to user after the user request to unscrube. This email message would contains a button for unsubscribing the contact list - add SECA when the createContactListPartyStatus be called with CLPT_ACCEPTED status then call the sendContactListPartySubscribeEmail service to send the subscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBSCRIBED status then call the sendContactListPartyUnSubscribeEmail service to send the unsubscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBS_PENDING status then call the sendContactListPartyUnSubscribeVerifyEmail service to send the email message to verify unscribing. - for starting receive a subscribe, change the contact list party's status from CLPT_ACCEPTED to CLPT_PENDING because the status should be pending before receiving a verify message - create ContactListSubscribeEmail and ContactListUnsubscribeVerifyEmail mail screens - add ProductStoreEmailSetting demo data for productStoreId=9000 with SUB_CONT_LIST_NOT and UNSUB_CONT_LIST_VERI email types - change verifyUrl in the email message's form to updateContactListPartyNoUserLogin because if the user doesn't have a user login then could not view the ecommerce's viewprofile screen. - add preferredContactMechId field to the createContactListPartyStatus and sendContactListPartyUnSubscribeEmail services because I get the contactMechId from ContactListParty instread of UserLogin because these services also be called without authentication. - add Unsubscribe button to Sign Up For Contact List section of the ecommerce's screen for requesting
[jira] Created: (OFBIZ-4055) Change Contact List Subscription Process
Change Contact List Subscription Process Key: OFBIZ-4055 URL: https://issues.apache.org/jira/browse/OFBIZ-4055 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk I think the current contact list subscription process is not complete. The current process is when a user enter his/her email address on the e-commerce page for subscribing a contact list. The system will set ContactListParty's status to Accepted. I think that should be set to Pending Acceptance first and wait for a user's confirmation from user's email inbox. Also the system should have a unsubscribe process to expire user's email address from a contact list. I found the unsubscribe statuses in StatusItem entity, Unsubscription pending and Unsubscribed, but they don't be used. I think the processes should following: Subscribe process === 1. The user select a contact list and enter his/her email address 2. The system create a ContactListParty with Pending Acceptance status 3. The system send a verify email message to the user's email address 4. The user confirm the subscribing in his/her email inbox 5. The system change the status of ContactListParty to Accepted Unsubscribe process 1. The use select a contact list and enter his/her email address 2. The system change the status of ContactListParty to Unsubscription pending 3. The system send a verify email message to the user's email address 4. The user confirm the unsubscribing in his/her email inbox 5. The system change the status of ContactListParty to Unsubscribed The both of processes, subscribe and unsubscribe, should also support if the user do not login to the system. I changed following: - create Subscribe Contact List Notification and Unsubscribe Contact List Verify as email type for email settings of product store - create signOutForContactList service for setting a contact list party's status to CLPT_UNSUBS_PENDING - create updateContactListPartyNoUserLogin service to handle updating the contact list party without user login - create sendContactListPartySubscribeEmail service for sending an email message to user after the user confirm the subscription. This email message would contains a button for requesting unsubscribe the contact list - create sendContactListPartyUnSubscribeVerifyEmail service for sending an email message to user after the user request to unscrube. This email message would contains a button for unsubscribing the contact list - add SECA when the createContactListPartyStatus be called with CLPT_ACCEPTED status then call the sendContactListPartySubscribeEmail service to send the subscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBSCRIBED status then call the sendContactListPartyUnSubscribeEmail service to send the unsubscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBS_PENDING status then call the sendContactListPartyUnSubscribeVerifyEmail service to send the email message to verify unscribing. - for starting receive a subscribe, change the contact list party's status from CLPT_ACCEPTED to CLPT_PENDING because the status should be pending before receiving a verify message - create ContactListSubscribeEmail and ContactListUnsubscribeVerifyEmail mail screens - add ProductStoreEmailSetting demo data for productStoreId=9000 with SUB_CONT_LIST_NOT and UNSUB_CONT_LIST_VERI email types - change verifyUrl in the email message's form to updateContactListPartyNoUserLogin because if the user doesn't have a user login then could not view the ecommerce's viewprofile screen. - add preferredContactMechId field to the createContactListPartyStatus and sendContactListPartyUnSubscribeEmail services because I get the contactMechId from ContactListParty instread of UserLogin because these services also be called without authentication. - add Unsubscribe button to Sign Up For Contact List section of the ecommerce's screen for requesting unsubscribing Thank you Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4055) Change Contact List Subscription Process
[ https://issues.apache.org/jira/browse/OFBIZ-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4055: Attachment: contactlist.patch Changing patch file Change Contact List Subscription Process Key: OFBIZ-4055 URL: https://issues.apache.org/jira/browse/OFBIZ-4055 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: contactlist.patch I think the current contact list subscription process is not complete. The current process is when a user enter his/her email address on the e-commerce page for subscribing a contact list. The system will set ContactListParty's status to Accepted. I think that should be set to Pending Acceptance first and wait for a user's confirmation from user's email inbox. Also the system should have a unsubscribe process to expire user's email address from a contact list. I found the unsubscribe statuses in StatusItem entity, Unsubscription pending and Unsubscribed, but they don't be used. I think the processes should following: Subscribe process === 1. The user select a contact list and enter his/her email address 2. The system create a ContactListParty with Pending Acceptance status 3. The system send a verify email message to the user's email address 4. The user confirm the subscribing in his/her email inbox 5. The system change the status of ContactListParty to Accepted Unsubscribe process 1. The use select a contact list and enter his/her email address 2. The system change the status of ContactListParty to Unsubscription pending 3. The system send a verify email message to the user's email address 4. The user confirm the unsubscribing in his/her email inbox 5. The system change the status of ContactListParty to Unsubscribed The both of processes, subscribe and unsubscribe, should also support if the user do not login to the system. I changed following: - create Subscribe Contact List Notification and Unsubscribe Contact List Verify as email type for email settings of product store - create signOutForContactList service for setting a contact list party's status to CLPT_UNSUBS_PENDING - create updateContactListPartyNoUserLogin service to handle updating the contact list party without user login - create sendContactListPartySubscribeEmail service for sending an email message to user after the user confirm the subscription. This email message would contains a button for requesting unsubscribe the contact list - create sendContactListPartyUnSubscribeVerifyEmail service for sending an email message to user after the user request to unscrube. This email message would contains a button for unsubscribing the contact list - add SECA when the createContactListPartyStatus be called with CLPT_ACCEPTED status then call the sendContactListPartySubscribeEmail service to send the subscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBSCRIBED status then call the sendContactListPartyUnSubscribeEmail service to send the unsubscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBS_PENDING status then call the sendContactListPartyUnSubscribeVerifyEmail service to send the email message to verify unscribing. - for starting receive a subscribe, change the contact list party's status from CLPT_ACCEPTED to CLPT_PENDING because the status should be pending before receiving a verify message - create ContactListSubscribeEmail and ContactListUnsubscribeVerifyEmail mail screens - add ProductStoreEmailSetting demo data for productStoreId=9000 with SUB_CONT_LIST_NOT and UNSUB_CONT_LIST_VERI email types - change verifyUrl in the email message's form to updateContactListPartyNoUserLogin because if the user doesn't have a user login then could not view the ecommerce's viewprofile screen. - add preferredContactMechId field to the createContactListPartyStatus and sendContactListPartyUnSubscribeEmail services because I get the contactMechId from ContactListParty instread of UserLogin because these services also be called without authentication. - add Unsubscribe button to Sign Up For Contact List section of the ecommerce's screen for requesting unsubscribing Thank you Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4055) Change Contact List Subscription Process
[ https://issues.apache.org/jira/browse/OFBIZ-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4055: Attachment: (was: contactlist.patch) Change Contact List Subscription Process Key: OFBIZ-4055 URL: https://issues.apache.org/jira/browse/OFBIZ-4055 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: ean.vcf I think the current contact list subscription process is not complete. The current process is when a user enter his/her email address on the e-commerce page for subscribing a contact list. The system will set ContactListParty's status to Accepted. I think that should be set to Pending Acceptance first and wait for a user's confirmation from user's email inbox. Also the system should have a unsubscribe process to expire user's email address from a contact list. I found the unsubscribe statuses in StatusItem entity, Unsubscription pending and Unsubscribed, but they don't be used. I think the processes should following: Subscribe process === 1. The user select a contact list and enter his/her email address 2. The system create a ContactListParty with Pending Acceptance status 3. The system send a verify email message to the user's email address 4. The user confirm the subscribing in his/her email inbox 5. The system change the status of ContactListParty to Accepted Unsubscribe process 1. The use select a contact list and enter his/her email address 2. The system change the status of ContactListParty to Unsubscription pending 3. The system send a verify email message to the user's email address 4. The user confirm the unsubscribing in his/her email inbox 5. The system change the status of ContactListParty to Unsubscribed The both of processes, subscribe and unsubscribe, should also support if the user do not login to the system. I changed following: - create Subscribe Contact List Notification and Unsubscribe Contact List Verify as email type for email settings of product store - create signOutForContactList service for setting a contact list party's status to CLPT_UNSUBS_PENDING - create updateContactListPartyNoUserLogin service to handle updating the contact list party without user login - create sendContactListPartySubscribeEmail service for sending an email message to user after the user confirm the subscription. This email message would contains a button for requesting unsubscribe the contact list - create sendContactListPartyUnSubscribeVerifyEmail service for sending an email message to user after the user request to unscrube. This email message would contains a button for unsubscribing the contact list - add SECA when the createContactListPartyStatus be called with CLPT_ACCEPTED status then call the sendContactListPartySubscribeEmail service to send the subscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBSCRIBED status then call the sendContactListPartyUnSubscribeEmail service to send the unsubscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBS_PENDING status then call the sendContactListPartyUnSubscribeVerifyEmail service to send the email message to verify unscribing. - for starting receive a subscribe, change the contact list party's status from CLPT_ACCEPTED to CLPT_PENDING because the status should be pending before receiving a verify message - create ContactListSubscribeEmail and ContactListUnsubscribeVerifyEmail mail screens - add ProductStoreEmailSetting demo data for productStoreId=9000 with SUB_CONT_LIST_NOT and UNSUB_CONT_LIST_VERI email types - change verifyUrl in the email message's form to updateContactListPartyNoUserLogin because if the user doesn't have a user login then could not view the ecommerce's viewprofile screen. - add preferredContactMechId field to the createContactListPartyStatus and sendContactListPartyUnSubscribeEmail services because I get the contactMechId from ContactListParty instread of UserLogin because these services also be called without authentication. - add Unsubscribe button to Sign Up For Contact List section of the ecommerce's screen for requesting unsubscribing Thank you Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-4055) Change Contact List Subscription Process
[ https://issues.apache.org/jira/browse/OFBIZ-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-4055: Attachment: contactlist.patch Hi, Ean Schuessler Thank you for your suggestion. I have re-attach the contactlist.patch file follow by your suggestion, change signOutForContactList to unsubscribeContactListParty word. Regards, Chatree Srichart Change Contact List Subscription Process Key: OFBIZ-4055 URL: https://issues.apache.org/jira/browse/OFBIZ-4055 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: Ubuntu 10.04 Reporter: Chatree Srichart Fix For: SVN trunk Attachments: contactlist.patch, ean.vcf I think the current contact list subscription process is not complete. The current process is when a user enter his/her email address on the e-commerce page for subscribing a contact list. The system will set ContactListParty's status to Accepted. I think that should be set to Pending Acceptance first and wait for a user's confirmation from user's email inbox. Also the system should have a unsubscribe process to expire user's email address from a contact list. I found the unsubscribe statuses in StatusItem entity, Unsubscription pending and Unsubscribed, but they don't be used. I think the processes should following: Subscribe process === 1. The user select a contact list and enter his/her email address 2. The system create a ContactListParty with Pending Acceptance status 3. The system send a verify email message to the user's email address 4. The user confirm the subscribing in his/her email inbox 5. The system change the status of ContactListParty to Accepted Unsubscribe process 1. The use select a contact list and enter his/her email address 2. The system change the status of ContactListParty to Unsubscription pending 3. The system send a verify email message to the user's email address 4. The user confirm the unsubscribing in his/her email inbox 5. The system change the status of ContactListParty to Unsubscribed The both of processes, subscribe and unsubscribe, should also support if the user do not login to the system. I changed following: - create Subscribe Contact List Notification and Unsubscribe Contact List Verify as email type for email settings of product store - create signOutForContactList service for setting a contact list party's status to CLPT_UNSUBS_PENDING - create updateContactListPartyNoUserLogin service to handle updating the contact list party without user login - create sendContactListPartySubscribeEmail service for sending an email message to user after the user confirm the subscription. This email message would contains a button for requesting unsubscribe the contact list - create sendContactListPartyUnSubscribeVerifyEmail service for sending an email message to user after the user request to unscrube. This email message would contains a button for unsubscribing the contact list - add SECA when the createContactListPartyStatus be called with CLPT_ACCEPTED status then call the sendContactListPartySubscribeEmail service to send the subscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBSCRIBED status then call the sendContactListPartyUnSubscribeEmail service to send the unsubscribe email message. - add SECA when the createContactListPartyStatus be called with CLPT_UNSUBS_PENDING status then call the sendContactListPartyUnSubscribeVerifyEmail service to send the email message to verify unscribing. - for starting receive a subscribe, change the contact list party's status from CLPT_ACCEPTED to CLPT_PENDING because the status should be pending before receiving a verify message - create ContactListSubscribeEmail and ContactListUnsubscribeVerifyEmail mail screens - add ProductStoreEmailSetting demo data for productStoreId=9000 with SUB_CONT_LIST_NOT and UNSUB_CONT_LIST_VERI email types - change verifyUrl in the email message's form to updateContactListPartyNoUserLogin because if the user doesn't have a user login then could not view the ecommerce's viewprofile screen. - add preferredContactMechId field to the createContactListPartyStatus and sendContactListPartyUnSubscribeEmail services because I get the contactMechId from ContactListParty instread of UserLogin because these services also be called without authentication. - add Unsubscribe button to Sign Up For Contact List section of the ecommerce's screen for requesting unsubscribing Thank you Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Description: This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no service name is added to URL. Operation name in request message specifies the service name. List of links to all WADL-documents can be requested with URL: /webtools/control/WebService?wadl Specific WADL-document is requested with URL: /webtools/control/WebService/service name here?wadl REST web service is called with URL: /webtools/control/WebService/service name here[?parameter=value...] REST web service with JSON-format is called with
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: (was: webservice.zip) New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: webservice.zip I got an updated message from Joonas Keturi: handling of list type attributes is changed to more general way, it was not very flexible in last version. also ^M-characters (carriage returns) are removed from patch-files, they came from windows by accident. So I update webservice.zip file for that and re-attach in the issue. New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker Attachments: webservice.zip This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT,
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: (was: webservice.zip) New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: webservice.zip Joonas Keturi asked me to update attached file. in this update are many mistakes fixed, and also web service client is improved and tested against complex external web service. i think there will no be updates for some time after this. Regards, Chatree Srichart New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker Attachments: webservice.zip This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update
[jira] Commented: (OFBIZ-3901) Birt charts and PDF generation
[ https://issues.apache.org/jira/browse/OFBIZ-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902747#action_12902747 ] Chatree Srichart commented on OFBIZ-3901: - This problem is only SVG problem. You can change the output format to other format. To solve the SVG problem is you have to remove these Batik bundle from framework/birt/lib/platform/plugins directory: - org.apache.batik.bridge - org.apache.batik.css - org.apache.batik.dom - org.apache.batik.dom.svg - org.apache.batik.transcoder - org.apache.batik.util and put these files (attached files) to the directory: - org.apache.batik.bridge_1.6.0.v200912221622.jar - org.apache.batik.css_1.6.0.v200912221622.jar - org.apache.batik.dom.svg_1.6.0.v200805290154.jar - org.apache.batik.dom_1.6.0.v200912221622.jar - org.apache.batik.transcoder_1.6.0.v200805290154.jar - org.apache.batik.util_1.6.0.v200805290154.jar I don't know what the exactly problem is because the current Batik bundles already use the same Apache Batik version of new Batik bundles. I will figure out the exactly problem later. Regards, Chatree Srichart Birt charts and PDF generation -- Key: OFBIZ-3901 URL: https://issues.apache.org/jira/browse/OFBIZ-3901 Project: OFBiz Issue Type: Sub-task Reporter: Erwan de FERRIERES Got to https://localhost:8443/example/control/chartViewHandler Here is the beginning of the stacktrace, if anyone has an idea... WARNING: loader constraint violation in interface itable initialization: when resolving method org.apache.batik.dom.AbstractDocument.createEvent(Ljava/lang/String;)Lorg/w3c/dom/events/Event; the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/apache/batik/dom/svg/SVGOMDocument, and the class loader (instance of bootloader) for interface org/w3c/dom/events/DocumentEvent have different Class objects for the type org/w3c/dom/events/Event used in the signature java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method org.apache.batik.dom.AbstractDocument.createEvent(Ljava/lang/String;)Lorg/w3c/dom/events/Event; the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/apache/batik/dom/svg/SVGOMDocument, and the class loader (instance of bootloader) for interface org/w3c/dom/events/DocumentEvent have different Class objects for the type org/w3c/dom/events/Event used in the signature at org.apache.batik.dom.svg.SVGDOMImplementation.createDocument(Unknown Source) at org.apache.batik.dom.util.SAXDocumentFactory.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3901) Birt charts and PDF generation
[ https://issues.apache.org/jira/browse/OFBIZ-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3901: Attachment: birt_bundles.zip Batik bundle files Birt charts and PDF generation -- Key: OFBIZ-3901 URL: https://issues.apache.org/jira/browse/OFBIZ-3901 Project: OFBiz Issue Type: Sub-task Reporter: Erwan de FERRIERES Attachments: birt_bundles.zip Got to https://localhost:8443/example/control/chartViewHandler Here is the beginning of the stacktrace, if anyone has an idea... WARNING: loader constraint violation in interface itable initialization: when resolving method org.apache.batik.dom.AbstractDocument.createEvent(Ljava/lang/String;)Lorg/w3c/dom/events/Event; the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/apache/batik/dom/svg/SVGOMDocument, and the class loader (instance of bootloader) for interface org/w3c/dom/events/DocumentEvent have different Class objects for the type org/w3c/dom/events/Event used in the signature java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method org.apache.batik.dom.AbstractDocument.createEvent(Ljava/lang/String;)Lorg/w3c/dom/events/Event; the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/apache/batik/dom/svg/SVGOMDocument, and the class loader (instance of bootloader) for interface org/w3c/dom/events/DocumentEvent have different Class objects for the type org/w3c/dom/events/Event used in the signature at org.apache.batik.dom.svg.SVGDOMImplementation.createDocument(Unknown Source) at org.apache.batik.dom.util.SAXDocumentFactory.startElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3896) BIRT Problems Issue
BIRT Problems Issue --- Key: OFBIZ-3896 URL: https://issues.apache.org/jira/browse/OFBIZ-3896 Project: OFBiz Issue Type: Bug Components: framework Environment: Ubuntu 10.04 Reporter: Chatree Srichart I create this issue for get BIRT problem report. If anyone found problem about BIRT component, please add comment here. Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3896) BIRT Problems Issue
[ https://issues.apache.org/jira/browse/OFBIZ-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3896: Attachment: org.eclipse.birt.chart.reportitem_2.6.0.v20100604.jar To fix BIRT chart problem, just replace framework/birt/lib/platform/plugins/org.eclipse.birt.chart.reportitem_2.5.1.v20090902a.jar file with org.eclipse.birt.chart.reportitem_2.6.0.v20100604.jar file (attached file). I have already updated this file's name in LICENSE file but I missed to replace it. Regards, Chatree Srichart BIRT Problems Issue --- Key: OFBIZ-3896 URL: https://issues.apache.org/jira/browse/OFBIZ-3896 Project: OFBiz Issue Type: Bug Components: framework Environment: Ubuntu 10.04 Reporter: Chatree Srichart Attachments: org.eclipse.birt.chart.reportitem_2.6.0.v20100604.jar I create this issue for get BIRT problem report. If anyone found problem about BIRT component, please add comment here. Regards, Chatree Srichart -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: (was: webservice.zip) New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: webservice.zip I re-attach webservice.zip file from Joonas Keturi updated: I took out mode-parameter choices ERROR and OUTERROR and made it simpler. modes are again as previously OUT, IN, INOUT. error messages are handled in other way (with attribute fault). Regards, Chatree Srichart New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker Attachments: webservice.zip This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Description: This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no service name is added to URL. Operation name in request message specifies the service name. List of links to all WADL-documents can be requested with URL: /webtools/control/WebService?wadl Specific WADL-document is requested with URL: /webtools/control/WebService/service name here?wadl REST web service is called with
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: webservice.zip New web service patch for service parameters are checked against service definitions nested attributes when calling services locally and added web service client, which can call document style web services. New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker Attachments: webservice.zip, webservice.zip This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: (was: webservice.zip) New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Assignee: Hans Bakker Attachments: webservice.zip This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.service.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ There is another new important class org.ofbiz.service.webservice.engine.WebServiceClientEngine which corresponds to earlier org.ofbiz.service.engine.SOAPClientEngine but tries to support document style web services using SOAP with XML-format. Web services can be called using their WSDL-document or messages can be specified in services.xml without using WSDL-document. engine-attribute in services description is set to webservice. Location of WSDL-document is given in attribute wsdlLocation or it can be left out if messages are described with attribute- definitions. Name of service in WSDL is given in attribute webServiceName and name of operation to be invoked in attribute invoke. One service-definition is needed for one web service-operation pair. Example of web service definitions are in file: framework/common/servicedef/services_test.xml This engine class uses other class: org.ofbiz.service.webservice.WebServiceClientModel which extends org.ofbiz.service.webservice.WebServiceModel and contains support for filling attribute definitions in org.ofbiz.service.ModelService from WSDL-document. 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL:
[jira] Created: (OFBIZ-3877) New Web Service Style
New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.webapp.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no service name is added to URL. Operation name in request message specifies the service name. List of links to all WADL-documents can be requested with URL: /webtools/control/WebService?wadl Specific WADL-document is requested with URL: /webtools/control/WebService/service name here?wadl REST web service is called with URL: /webtools/control/WebService/service name here SOAP and REST web service requests are selected by request URL, where REST web service has appended service name in URL. 4.) Unit tests org.ofbiz.webapp.webservice.test.WebServiceTests This has 14 different tests which are: 1. Conversion of XML-object model to Map 2. Conversion of Map to XML-object model 3. Call SOAP-web service 4. Call SOAP-web service which needs authorization 5. Call SOAP-web service with wrong credentials 6. Call SOAP-web service with wrong service name 7. Call REST-web service 8. Call REST-web service which needs authorization 9. Call REST-web service with wrong credentials 10. Call REST-web service with wrong service name 11. Call REST-web service using JSON-format 12. Call REST-web service which needs authorization using JSON-format 13. Call REST-web service with wrong credentials using JSON-format 14. Call REST-web service with wrong service name using JSON-format These unit tests use test service in class org.ofbiz.webapp.webservice.test.WebServiceTestServices Service definitions are in file
[jira] Updated: (OFBIZ-3877) New Web Service Style
[ https://issues.apache.org/jira/browse/OFBIZ-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3877: Attachment: webservice.zip webservice.zip file container patch and additional jar file for web service New Web Service Style - Key: OFBIZ-3877 URL: https://issues.apache.org/jira/browse/OFBIZ-3877 Project: OFBiz Issue Type: New Feature Components: framework Environment: Windows, Ubuntu Linux Reporter: Chatree Srichart Attachments: webservice.zip This is a new stub for new web service style that use a normal style (not hash map [key/value]). [[ Installation ]] - Extract webservice.zip file (attached file) to hot-deploy directory of OFBiz framework - run ant task for apply patch in webservice directory with: ant reapply-ofbiz-patches [[ Features ]] 1.) New classes There is new important class org.ofbiz.webapp.webservice.event.WebServiceEventHandler which corresponds to earlier org.ofbiz.webapp.event.SOAPEventHandler but tries to support document style web services using SOAP with XML-format, or REST with XML and JSON-formats. This handler class uses other class: org.ofbiz.webapp.webservice.WebServiceModel which wraps inside class org.ofbiz.service.ModelService and contains support for WSDL-generation, WADL-generation and conversion between Java Maps and XML-object models. WSDL=Web Service Definition Language for SOAP-interface http://www.w3.org/TR/wsdl WADL=Web Application Description Language for REST-interface http://www.w3.org/Submission/wadl/ 2.) Service definitions Web service interface can be used only if service definition file services.xml is completed with additional definitions. Schema of this file is extended. attribute-elements can have nested attribute elements which describe structure of Java maps and lists. If attribute has type Map, it should have nested attributes which describe contents of this map. If attribute has type List, it should have nested attributes which describe element contents of this list. If List has simple elements, there must be only one nested attribute, which describes element. If List has element which is map or other list, there must be one nested attribute stating that the element is Map or List, and then this attribute should have nested attributes describing structure of Map or structure of list element. There are also two new modes for attributes ERROR which means that attribute is responded as error message OUTERROR which means that attribute is responded as error or as success message These modes are needed for web services to describe which parameters will go to detail-elements of SOAP Fault response or REST error messages. Also in WSDL- and WADL-files will be generated XML-schema for general response messages. File framework\webapp\servicedef\services_test.xml can be used as example of attribute definitions. This file is used in unit tests of web service interface. 3.) Web service requests In REST-services HTTP GET-method is used in services whose name start with words find or get. These services should have input parameters in one level, so that they can be given as query parameters in URL. HTTP DELETE-method is used with services whose name start with word remove. Other services are used with HTTP POST-method and PUT-method. Service must look itself for method name POST or PUT, if it is required to operate differently in insert or update cases. List of links to all WSDL-documents can be requested with URL: /webtools/control/WebService?wsdl Specific WSDL-document is requested with URL: /webtools/control/WebService/service name here?wsdl SOAP web service is called with URL: /webtools/control/WebService Notice that no service name is added to URL. Operation name in request message specifies the service name. List of links to all WADL-documents can be requested with URL: /webtools/control/WebService?wadl Specific WADL-document is requested with URL: /webtools/control/WebService/service name here?wadl REST web service is called with URL: /webtools/control/WebService/service name here SOAP and REST web service requests are selected by request URL, where REST web service has appended service name in URL. 4.) Unit tests org.ofbiz.webapp.webservice.test.WebServiceTests This has 14 different tests which are: 1. Conversion of XML-object model to Map 2. Conversion of Map to XML-object model 3. Call SOAP-web service 4. Call SOAP-web service which needs authorization 5. Call SOAP-web service with wrong credentials 6. Call SOAP-web service with wrong service name 7. Call REST-web service 8. Call REST-web service which needs authorization 9. Call REST-web
[jira] Updated: (OFBIZ-3394) Axis2 SOAP implementation does not have types defined for col-* elements
[
https://issues.apache.org/jira/browse/OFBIZ-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chatree Srichart updated OFBIZ-3394:
Attachment: patch.txt
Hi, Chris Snow
I created a patch for solve your issue but I can not test it because I have a
eclipse problem with Axis2.
May you test it?
Axis2 SOAP implementation does not have types defined for col-* elements
Key: OFBIZ-3394
URL: https://issues.apache.org/jira/browse/OFBIZ-3394
Project: OFBiz
Issue Type: Bug
Components: framework
Affects Versions: SVN trunk
Reporter: chris snow
Attachments: patch.txt
The wsdl generated from the Axis2 soap implementation does not define types
for col-* elements:
{code}
xsd:element name=col-ArrayList/
xsd:element name=col-LinkedList/
xsd:element name=col-Stack/
xsd:element name=col-Vector/
xsd:element name=col-TreeSet/
xsd:element name=col-HashSet/
xsd:element name=col-Collection/
{code}
I would expect to see something like:
{code}
xsd:element name=col-ArrayList type=tns:XXX/
xsd:complexType name=XXX
!-- To be defined --
/xsd:complexType
{code}
Without type defintions, tools (such as wsdl2java) are unable to generate the
appropriate classes for the col-* elements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
[
https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12793469#action_12793469
]
Chatree Srichart commented on OFBIZ-3363:
-
Hi, Chris Snow
Because XmlSerializer of OFBiz use tag's name for serialize/deserialze. So SOAP
xml message don't need prefix for each tag. Can you change your code like
this...
{code}
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:ser=http://ofbiz.apache.org/service/;
soapenv:Header/
soapenv:Body
ser:findPartiesById
map-Map
map-Entry
map-Key
std-String value=idToFind/
/map-Key
map-Value
std-String value=admin/
/map-Value
/map-Entry
/map-Map
/ser:findPartiesById
/soapenv:Body
/soapenv:Envelope
{code}
How do you think about this solution or it should can use prefix in XML message?
Thank you
Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
-
Key: OFBIZ-3363
URL: https://issues.apache.org/jira/browse/OFBIZ-3363
Project: OFBiz
Issue Type: New Feature
Components: framework
Affects Versions: SVN trunk
Reporter: Chatree Srichart
Assignee: Hans Bakker
Fix For: SVN trunk
Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd
Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
I change OFBiz's web service API to Axis2.
==Client Engine==
1. XMLSerializer to serialize parameters Map object to XML.
2. create OMElement from XML stream.
3. ServiceClient send SOAP message.
4. get result OMElement.
5. convert XML content in OMElement to results Map object.
==Event Handler==
1. create OMElement from InputStream
2. get service's name
3. XMLSerializer to deserialize parameters XML to Map object
4. call specific service
5. XMLSerializer to serializer service's results Map object to XML
6. create OMElement for service's results
7. send OMElement to response
==Apply Axis2 in OFBiz==
1. apply patch
2. unzip libraries.zip and copy all jar files to framework/service/lib
directory
==Test SOAP Service==
run unit test:
./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests
This is a test case that demonstrate service engine can sent both of single
type and complex type
==WSDL==
The testSoap.wsdl file is web service definition language of testSoap service.
Every services require map-Map as type of input/output parameter. In map-Map
consist of key/value pair for service's parameters.
In wsdl:part of wsdl:message has wsdl:documentation which state service's
attribute, consist of
1. name
2. type
3. namespace
4. java-class
5. optional
==WSDL Types==
The types.xsd file is xml schema for complex type
WSDL Types be generated by code. If any one has a better solution please
comment this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: Attachment: (was: axis2.diff) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported - Key: OFBIZ-3363 URL: https://issues.apache.org/jira/browse/OFBIZ-3363 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Chatree Srichart Assignee: Hans Bakker Fix For: SVN trunk Attachments: libraries.zip, testSoap.wsdl, types.xsd Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported I change OFBiz's web service API to Axis2. ==Client Engine== 1. XMLSerializer to serialize parameters Map object to XML. 2. create OMElement from XML stream. 3. ServiceClient send SOAP message. 4. get result OMElement. 5. convert XML content in OMElement to results Map object. ==Event Handler== 1. create OMElement from InputStream 2. get service's name 3. XMLSerializer to deserialize parameters XML to Map object 4. call specific service 5. XMLSerializer to serializer service's results Map object to XML 6. create OMElement for service's results 7. send OMElement to response ==Apply Axis2 in OFBiz== 1. apply patch 2. unzip libraries.zip and copy all jar files to framework/service/lib directory ==Test SOAP Service== run unit test: ./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests This is a test case that demonstrate service engine can sent both of single type and complex type ==WSDL== The testSoap.wsdl file is web service definition language of testSoap service. Every services require map-Map as type of input/output parameter. In map-Map consist of key/value pair for service's parameters. In wsdl:part of wsdl:message has wsdl:documentation which state service's attribute, consist of 1. name 2. type 3. namespace 4. java-class 5. optional ==WSDL Types== The types.xsd file is xml schema for complex type WSDL Types be generated by code. If any one has a better solution please comment this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: Attachment: axis2.diff Because old version of diff file required demo data for run test. So I upload new version for diff file. The current diff file create ProductCategory and Product value at runtime for send through web service. Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported - Key: OFBIZ-3363 URL: https://issues.apache.org/jira/browse/OFBIZ-3363 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Chatree Srichart Assignee: Hans Bakker Fix For: SVN trunk Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported I change OFBiz's web service API to Axis2. ==Client Engine== 1. XMLSerializer to serialize parameters Map object to XML. 2. create OMElement from XML stream. 3. ServiceClient send SOAP message. 4. get result OMElement. 5. convert XML content in OMElement to results Map object. ==Event Handler== 1. create OMElement from InputStream 2. get service's name 3. XMLSerializer to deserialize parameters XML to Map object 4. call specific service 5. XMLSerializer to serializer service's results Map object to XML 6. create OMElement for service's results 7. send OMElement to response ==Apply Axis2 in OFBiz== 1. apply patch 2. unzip libraries.zip and copy all jar files to framework/service/lib directory ==Test SOAP Service== run unit test: ./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests This is a test case that demonstrate service engine can sent both of single type and complex type ==WSDL== The testSoap.wsdl file is web service definition language of testSoap service. Every services require map-Map as type of input/output parameter. In map-Map consist of key/value pair for service's parameters. In wsdl:part of wsdl:message has wsdl:documentation which state service's attribute, consist of 1. name 2. type 3. namespace 4. java-class 5. optional ==WSDL Types== The types.xsd file is xml schema for complex type WSDL Types be generated by code. If any one has a better solution please comment this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported - Key: OFBIZ-3363 URL: https://issues.apache.org/jira/browse/OFBIZ-3363 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Chatree Srichart Fix For: SVN trunk Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported I change OFBiz's web service API to Axis2. ==Client Engine== 1. XMLSerializer to serialize parameters Map object to XML. 2. create OMElement from XML stream. 3. ServiceClient send SOAP message. 4. get result OMElement. 5. convert XML content in OMElement to results Map object. ==Event Handler== 1. create OMElement from InputStream 2. get service's name 3. XMLSerializer to deserialize parameters XML to Map object 4. call specific service 5. XMLSerializer to serializer service's results Map object to XML 6. create OMElement for service's results 7. send OMElement to response ==Apply Axis2 in OFBiz== 1. apply patch 2. unzip libraries.zip and copy all jar files to framework/service/lib directory Test SOAP Service run unit test: ./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests This is a test case that demonstrate service engine can sent both of single type and complex type ==WSDL== The testSoap.wsdl file is web service definition language of testSoap service. Every services require map-Map as type of input/output parameter. In map-Map consist of key/value pair for service's parameters. In wsdl:part of wsdl:message has wsdl:documentation which state service's attribute, consist of 1. name 2. type 3. namespace 4. java-class 5. optional ==WSDL Types== The types.xsd file is xml schema for complex type WSDL Types be generated by code. If any one has a better solution please comment this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: Attachment: axis2.diff libraries.zip Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported - Key: OFBIZ-3363 URL: https://issues.apache.org/jira/browse/OFBIZ-3363 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Chatree Srichart Fix For: SVN trunk Attachments: axis2.diff, libraries.zip Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported I change OFBiz's web service API to Axis2. ==Client Engine== 1. XMLSerializer to serialize parameters Map object to XML. 2. create OMElement from XML stream. 3. ServiceClient send SOAP message. 4. get result OMElement. 5. convert XML content in OMElement to results Map object. ==Event Handler== 1. create OMElement from InputStream 2. get service's name 3. XMLSerializer to deserialize parameters XML to Map object 4. call specific service 5. XMLSerializer to serializer service's results Map object to XML 6. create OMElement for service's results 7. send OMElement to response ==Apply Axis2 in OFBiz== 1. apply patch 2. unzip libraries.zip and copy all jar files to framework/service/lib directory Test SOAP Service run unit test: ./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests This is a test case that demonstrate service engine can sent both of single type and complex type ==WSDL== The testSoap.wsdl file is web service definition language of testSoap service. Every services require map-Map as type of input/output parameter. In map-Map consist of key/value pair for service's parameters. In wsdl:part of wsdl:message has wsdl:documentation which state service's attribute, consist of 1. name 2. type 3. namespace 4. java-class 5. optional ==WSDL Types== The types.xsd file is xml schema for complex type WSDL Types be generated by code. If any one has a better solution please comment this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3363) Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported
[ https://issues.apache.org/jira/browse/OFBIZ-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chatree Srichart updated OFBIZ-3363: Attachment: types.xsd testSoap.wsdl Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported - Key: OFBIZ-3363 URL: https://issues.apache.org/jira/browse/OFBIZ-3363 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Chatree Srichart Assignee: Hans Bakker Fix For: SVN trunk Attachments: axis2.diff, libraries.zip, testSoap.wsdl, types.xsd Upgrading Axis V1 to V2 in OFbiz's Web Service and Complex Type Supported I change OFBiz's web service API to Axis2. ==Client Engine== 1. XMLSerializer to serialize parameters Map object to XML. 2. create OMElement from XML stream. 3. ServiceClient send SOAP message. 4. get result OMElement. 5. convert XML content in OMElement to results Map object. ==Event Handler== 1. create OMElement from InputStream 2. get service's name 3. XMLSerializer to deserialize parameters XML to Map object 4. call specific service 5. XMLSerializer to serializer service's results Map object to XML 6. create OMElement for service's results 7. send OMElement to response ==Apply Axis2 in OFBiz== 1. apply patch 2. unzip libraries.zip and copy all jar files to framework/service/lib directory Test SOAP Service run unit test: ./ant run-single-test -Dtest.component=service -Dtest.case=service-soap-tests This is a test case that demonstrate service engine can sent both of single type and complex type ==WSDL== The testSoap.wsdl file is web service definition language of testSoap service. Every services require map-Map as type of input/output parameter. In map-Map consist of key/value pair for service's parameters. In wsdl:part of wsdl:message has wsdl:documentation which state service's attribute, consist of 1. name 2. type 3. namespace 4. java-class 5. optional ==WSDL Types== The types.xsd file is xml schema for complex type WSDL Types be generated by code. If any one has a better solution please comment this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
