[jira] [Updated] (OFBIZ-9418) Static resources for theme in unreasonable file/folder structure

[JIRA]

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

Đỗ Như Vý updated OFBIZ-9418:
-
Description: 
For example

{code:xml}


{code}
or

{code:xml}

{code}

JS file put inside images folder. And this is own theme file, but put in common 
directory.
We should change file/folder structure in a reasonable way.

Attachment: 
https://user-images.githubusercontent.com/1328316/27249120-1c89fb58-5338-11e7-8390-e09c6ab2c7a6.png



  was:
For example

{code:xml}


{code}
or

{code:xml}

{code}

JS file put inside images folder. And this is own theme file, but put in common 
directory.
We should change file/folder structure in a reasonable way.

!https://user-images.githubusercontent.com/1328316/27249120-1c89fb58-5338-11e7-8390-e09c6ab2c7a6.png!




> Static resources for theme in unreasonable file/folder structure
> 
>
> Key: OFBIZ-9418
> URL: https://issues.apache.org/jira/browse/OFBIZ-9418
> Project: OFBiz
>  Issue Type: Improvement
>  Components: themes
>Affects Versions: 16.11.02
>Reporter: Đỗ Như Vý
>Priority: Minor
>
> For example
> {code:xml}
>  resourceTypeEnumId="VT_STYLESHEET" 
> resourceValue="/images/jquery/plugins/asmselect/jquery.asmselect-1.0.4a-beta.css"
>  sequenceId="02"/>
> {code}
> or
> {code:xml}
>  resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/images/OfbizUtil.js" 
> sequenceId="15"/>
> {code}
> JS file put inside images folder. And this is own theme file, but put in 
> common directory.
> We should change file/folder structure in a reasonable way.
> Attachment: 
> https://user-images.githubusercontent.com/1328316/27249120-1c89fb58-5338-11e7-8390-e09c6ab2c7a6.png



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9418) Static resources for theme in unreasonable file/folder structure

[JIRA]

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

Đỗ Như Vý updated OFBIZ-9418:
-
Description: 
For example

{code:xml}


{code}
or

{code:xml}

{code}

JS file put inside images folder. And this is own theme file, but put in common 
directory.
We should change file/folder structure in a reasonable way.

!https://user-images.githubusercontent.com/1328316/27249120-1c89fb58-5338-11e7-8390-e09c6ab2c7a6.png!



  was:
For example

{code:xml}


{code}
or

{code:xml}

{code}

JS file put inside images folder. And this is own theme file, but put in common 
directory.
We should change file/folder structure in a reasonable way.






> Static resources for theme in unreasonable file/folder structure
> 
>
> Key: OFBIZ-9418
> URL: https://issues.apache.org/jira/browse/OFBIZ-9418
> Project: OFBiz
>  Issue Type: Improvement
>  Components: themes
>Affects Versions: 16.11.02
>Reporter: Đỗ Như Vý
>Priority: Minor
>
> For example
> {code:xml}
>  resourceTypeEnumId="VT_STYLESHEET" 
> resourceValue="/images/jquery/plugins/asmselect/jquery.asmselect-1.0.4a-beta.css"
>  sequenceId="02"/>
> {code}
> or
> {code:xml}
>  resourceTypeEnumId="VT_HDR_JAVASCRIPT" resourceValue="/images/OfbizUtil.js" 
> sequenceId="15"/>
> {code}
> JS file put inside images folder. And this is own theme file, but put in 
> common directory.
> We should change file/folder structure in a reasonable way.
> !https://user-images.githubusercontent.com/1328316/27249120-1c89fb58-5338-11e7-8390-e09c6ab2c7a6.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OFBIZ-9418) Static resources for theme in unreasonable file/folder structure

[JIRA]

Đỗ Như Vý created OFBIZ-9418:


 Summary: Static resources for theme in unreasonable file/folder 
structure
 Key: OFBIZ-9418
 URL: https://issues.apache.org/jira/browse/OFBIZ-9418
 Project: OFBiz
  Issue Type: Improvement
  Components: themes
Affects Versions: 16.11.02
Reporter: Đỗ Như Vý
Priority: Minor


For example

{code:xml}


{code}
or

{code:xml}

{code}

JS file put inside images folder. And this is own theme file, but put in common 
directory.
We should change file/folder structure in a reasonable way.







--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9417) Remove OFBADMIN, OFBREQDES and OFBTECH spaces

[Michael Brohl (JIRA)]

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

Michael Brohl updated OFBIZ-9417:
-
Summary: Remove OFBADMIN, OFBREQDES and OFBTECH spaces  (was: Remove 
OFBADMIN and OFBREQDES spaces)

> Remove OFBADMIN, OFBREQDES and OFBTECH spaces
> -
>
> Key: OFBIZ-9417
> URL: https://issues.apache.org/jira/browse/OFBIZ-9417
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: Confluence
>Reporter: Michael Brohl
>Assignee: Michael Brohl
>Priority: Trivial
>
> The contents are moved. The spaces should be removed if there are no 
> objections against it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OFBIZ-9417) Remove OFBADMIN and OFBREQDES spaces

[Michael Brohl (JIRA)]

Michael Brohl created OFBIZ-9417:


 Summary: Remove OFBADMIN and OFBREQDES spaces
 Key: OFBIZ-9417
 URL: https://issues.apache.org/jira/browse/OFBIZ-9417
 Project: OFBiz
  Issue Type: Sub-task
  Components: Confluence
Reporter: Michael Brohl
Assignee: Michael Brohl
Priority: Trivial


The contents are moved. The spaces should be removed if there are no objections 
against it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9171) Check and restructure the OFBiz wiki

[Michael Brohl (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052422#comment-16052422
 ] 

Michael Brohl commented on OFBIZ-9171:
--

Moved the contents of the OFBADMIN and the OFBREQDES spaces to the OFBiz space 
and put them in the right places (I think).

They can now be found under 
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Project+Administration 
and 
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Requirements+and+Designs.

Also did some cleanup and editing.

> Check and restructure the OFBiz wiki
> 
>
> Key: OFBIZ-9171
> URL: https://issues.apache.org/jira/browse/OFBIZ-9171
> Project: OFBiz
>  Issue Type: Improvement
>  Components: Confluence
>Reporter: Michael Brohl
>Assignee: Michael Brohl
> Attachments: OFBiz Wiki Restructure.pdf
>
>
> Our current wiki layout is lacking an intuitive structure. Without knowledge 
> about the contents and confluence search options, it is very difficult to 
> find informations.
> I'll try to workout a general structure as a proposal. Once this is agreed, 
> we can build up this structure and reassign the wiki contents step by step.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9392) Refactor CatalinaContainer

[Taher Alkhateeb (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052387#comment-16052387
 ] 

Taher Alkhateeb commented on OFBIZ-9392:


I figured out that it might be possible to unify the webapps with a little bit 
of work using the [DirResourceSet | 
https://tomcat.apache.org/tomcat-8.0-doc/api/org/apache/catalina/webresources/DirResourceSet.html]
 class. I need to do some extra homework on this, but keeping this note in JIRA 
as a reference for the future.

> Refactor CatalinaContainer
> --
>
> Key: OFBIZ-9392
> URL: https://issues.apache.org/jira/browse/OFBIZ-9392
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Reporter: Taher Alkhateeb
>Assignee: Taher Alkhateeb
>Priority: Minor
> Attachments: OFBIZ-9392.patch, OFBIZ-9392.patch, OFBIZ-9392.patch
>
>
> The implementation of CatalinaContainer.java is currently very verbose, has 
> replicated code, and is difficult to navigate.
> The objective of this JIRA is to breakup the logic into smaller manageable 
> functions to allow for further enhancements in the future.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OFBIZ-9416) Wiki restructure issues

[Michael Brohl (JIRA)]

Michael Brohl created OFBIZ-9416:


 Summary: Wiki restructure issues
 Key: OFBIZ-9416
 URL: https://issues.apache.org/jira/browse/OFBIZ-9416
 Project: OFBiz
  Issue Type: Sub-task
  Components: Confluence
Reporter: Michael Brohl
Assignee: Michael Brohl
Priority: Minor


This issue should be used to report issues which are caused by the wiki 
restructuring. Please report dead links, wrong external references and other 
problems here by adding a comment.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9415) Refactor list related form widgets in various WorkEffort screens

[Pierre Smits (JIRA)]

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

Pierre Smits updated OFBIZ-9415:

Attachment: OFBIZ-9414-WorkEffort-widget.patch

This patch partly addresses the issue.

> Refactor list related form widgets in various WorkEffort screens
> 
>
> Key: OFBIZ-9415
> URL: https://issues.apache.org/jira/browse/OFBIZ-9415
> Project: OFBiz
>  Issue Type: Improvement
>  Components: workeffort
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Pierre Smits
>  Labels: refactor, widgets
> Attachments: OFBIZ-9414-WorkEffort-widget.patch
>
>
> Refactoring various list forms into grids
> Refactoring various list form references in screens



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OFBIZ-9415) Refactor list related form widgets in various WorkEffort screens

[Pierre Smits (JIRA)]

Pierre Smits created OFBIZ-9415:
---

 Summary: Refactor list related form widgets in various WorkEffort 
screens
 Key: OFBIZ-9415
 URL: https://issues.apache.org/jira/browse/OFBIZ-9415
 Project: OFBiz
  Issue Type: Improvement
  Components: workeffort
Affects Versions: Trunk
Reporter: Pierre Smits
Assignee: Pierre Smits


Refactoring various list forms into grids
Refactoring various list form references in screens




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9413) Update Currency Uom data

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051819#comment-16051819
 ] 

Deepak Dixit commented on OFBIZ-9413:
-

Yes Jacques, I am working on it, I'll upload patch for review. 

> Update Currency Uom data 
> -
>
> Key: OFBIZ-9413
> URL: https://issues.apache.org/jira/browse/OFBIZ-9413
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: list_three.xls
>
>
> While adding numericCode to currency UOM, I found that we need to update  
> some old currency UOM, as uomId has been updated. 
> https://www.currency-iso.org/en/home/tables/table-a1.html
> https://www.currency-iso.org/en/home/amendments.html
> Here is the short summary 
> *Following UomId not found*
> * Santo Domiongo(CDP)
> * Brazil (BRR)
> * Argentinian Austral(ARA)
> * Andoran peseta(ADP)
> * Maltese Lira (MTL)
> * Mexican Peso (old)(MXP)
> * Peruvian Inti(PEI)
> * Peruvian Sol(PES)
> * Tadzhikistani Ruble(TJR)
> *Following UOM using other currency * 
> Used Other
> * ANDORRA == Euro
> * Cyprus Pound(CYP) == Euro
> * Ecuador Sucre(ECS) =  USD
> * Estonian Krone(EEK) = EURO
> * Lithuanian Lita(LTL) == EURO
> * Latvian Lat(LVL) == EURO
> * Timor Escudo(TPE) == US Dollor
> *Following UOM has been changed*
> ||Old||New||
> |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)|
> |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)|
> |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)|
> |Angolan Kwanza (AOK)|Kwanza (AOA)|
> |Afghani (AFA)|Afghani(AFN)|
> |Dominican Republic Peso(DRP)|Dominican Peso (DOP)|
> |Ghanian Cedi(GHC)|Ghana Cedi(GHS)|
> |Guinea Peso(GWP)| Guinean Franc(GNF)|
> |Kirghizstan Som(KIS)|KYRGYZSTAN  Som (KGS)|
> |Madagascan Franc(MGF)|Malagasy Ariary(MGA)|
> |Mozambique Metical(MZM)|Mozambique Metical(MZN)|
> |Nicaragua (NIC)|Cordoba Oro (NIO)|
> |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)|
> |Poland(PLZ)|Zloty (PLN)|
> |Romanian Leu(ROL)|Romanian Leu(RON)|
> |Russian Rouble(RUR)|Russian Ruble(RUB)|
> |Sudanese Pound(SDP)|Sudanese Pound(SDG)|
> |Peru (SOL)|Sol (PEN)|
> |Surinam Guilder(SRG)|Surinam Dollar (SRD)|
> |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)|
> |Uganda Shilling(UGS)|Uganda Shilling(UGX)|
> |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)|
> |Venezuelan Bolivar(VEB)|Bolívar(VEF)|
> |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)|
> |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)|
> |Georgian Kupon (GEK)|GEORGIA Lari (GEL)|
> Some currency codes moved to historic denominations, we can remove them from 
> data.
> https://www.currency-iso.org/en/home/tables/table-a3.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9414) Adds 30 sec sleep after "ofbizBackground --shutdown" to allow time for OFBiz to stop

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051820#comment-16051820
 ] 

Jacques Le Roux commented on OFBIZ-9414:


Done at r1798912

Just thought that if we don't use terminateOfbiz in trunk-manual-only.sh we 
then also need to put a 30 sec sleep into stable-manual.sh, done at r1798919  



> Adds 30 sec sleep after "ofbizBackground --shutdown" to allow time for OFBiz 
> to stop
> 
>
> Key: OFBIZ-9414
> URL: https://issues.apache.org/jira/browse/OFBIZ-9414
> Project: OFBiz
>  Issue Type: Improvement
>  Components: Demo
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
>
> For a moment, I was wondering why 
> bq. ./gradlew "ofbizBackground --shutdown"
> did not work with demos
> While fixing trunk-manual.sh on the VM (forgot to change for loadAll) I then 
> realized that it could be because you can't chain another Gradle task just 
> after "ofbizBackground --shutdown". 
> So I added a 30 sec sleep to trunk-manual-only.sh and it worked manually. I 
> have now chained trunk-manual-only.sh in all-manual.sh (indirectly called by 
> cron) and if it works tonight I will replace trunk-manual.sh content by 
> trunk-manual-only.sh content and remove trunk-manual-only.sh



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9414) Adds 30 sec sleep after "ofbizBackground --shutdown" to allow time for OFBiz to stop

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051821#comment-16051821
 ] 

Jacques Le Roux commented on OFBIZ-9414:


Of course the commits are only for backup, the changes are also done in the 
demo VM itself

> Adds 30 sec sleep after "ofbizBackground --shutdown" to allow time for OFBiz 
> to stop
> 
>
> Key: OFBIZ-9414
> URL: https://issues.apache.org/jira/browse/OFBIZ-9414
> Project: OFBiz
>  Issue Type: Improvement
>  Components: Demo
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
>
> For a moment, I was wondering why 
> bq. ./gradlew "ofbizBackground --shutdown"
> did not work with demos
> While fixing trunk-manual.sh on the VM (forgot to change for loadAll) I then 
> realized that it could be because you can't chain another Gradle task just 
> after "ofbizBackground --shutdown". 
> So I added a 30 sec sleep to trunk-manual-only.sh and it worked manually. I 
> have now chained trunk-manual-only.sh in all-manual.sh (indirectly called by 
> cron) and if it works tonight I will replace trunk-manual.sh content by 
> trunk-manual-only.sh content and remove trunk-manual-only.sh



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9413) Update Currency Uom data

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051803#comment-16051803
 ] 

Jacques Le Roux commented on OFBIZ-9413:


Thanks for the effor Deepak,

Will you provide a patch?

> Update Currency Uom data 
> -
>
> Key: OFBIZ-9413
> URL: https://issues.apache.org/jira/browse/OFBIZ-9413
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: list_three.xls
>
>
> While adding numericCode to currency UOM, I found that we need to update  
> some old currency UOM, as uomId has been updated. 
> https://www.currency-iso.org/en/home/tables/table-a1.html
> https://www.currency-iso.org/en/home/amendments.html
> Here is the short summary 
> *Following UomId not found*
> * Santo Domiongo(CDP)
> * Brazil (BRR)
> * Argentinian Austral(ARA)
> * Andoran peseta(ADP)
> * Maltese Lira (MTL)
> * Mexican Peso (old)(MXP)
> * Peruvian Inti(PEI)
> * Peruvian Sol(PES)
> * Tadzhikistani Ruble(TJR)
> *Following UOM using other currency * 
> Used Other
> * ANDORRA == Euro
> * Cyprus Pound(CYP) == Euro
> * Ecuador Sucre(ECS) =  USD
> * Estonian Krone(EEK) = EURO
> * Lithuanian Lita(LTL) == EURO
> * Latvian Lat(LVL) == EURO
> * Timor Escudo(TPE) == US Dollor
> *Following UOM has been changed*
> ||Old||New||
> |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)|
> |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)|
> |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)|
> |Angolan Kwanza (AOK)|Kwanza (AOA)|
> |Afghani (AFA)|Afghani(AFN)|
> |Dominican Republic Peso(DRP)|Dominican Peso (DOP)|
> |Ghanian Cedi(GHC)|Ghana Cedi(GHS)|
> |Guinea Peso(GWP)| Guinean Franc(GNF)|
> |Kirghizstan Som(KIS)|KYRGYZSTAN  Som (KGS)|
> |Madagascan Franc(MGF)|Malagasy Ariary(MGA)|
> |Mozambique Metical(MZM)|Mozambique Metical(MZN)|
> |Nicaragua (NIC)|Cordoba Oro (NIO)|
> |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)|
> |Poland(PLZ)|Zloty (PLN)|
> |Romanian Leu(ROL)|Romanian Leu(RON)|
> |Russian Rouble(RUR)|Russian Ruble(RUB)|
> |Sudanese Pound(SDP)|Sudanese Pound(SDG)|
> |Peru (SOL)|Sol (PEN)|
> |Surinam Guilder(SRG)|Surinam Dollar (SRD)|
> |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)|
> |Uganda Shilling(UGS)|Uganda Shilling(UGX)|
> |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)|
> |Venezuelan Bolivar(VEB)|Bolívar(VEF)|
> |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)|
> |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)|
> |Georgian Kupon (GEK)|GEORGIA Lari (GEL)|
> Some currency codes moved to historic denominations, we can remove them from 
> data.
> https://www.currency-iso.org/en/home/tables/table-a3.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OFBIZ-9414) Adds 30 sec sleep after "ofbizBackground --shutdown" to allow time for OFBiz to stop

[Jacques Le Roux (JIRA)]

Jacques Le Roux created OFBIZ-9414:
--

 Summary: Adds 30 sec sleep after "ofbizBackground --shutdown" to 
allow time for OFBiz to stop
 Key: OFBIZ-9414
 URL: https://issues.apache.org/jira/browse/OFBIZ-9414
 Project: OFBiz
  Issue Type: Improvement
  Components: Demo
Affects Versions: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor


For a moment, I was wondering why 
bq. ./gradlew "ofbizBackground --shutdown"
did not work with demos

While fixing trunk-manual.sh on the VM (forgot to change for loadAll) I then 
realized that it could be because you can't chain another Gradle task just 
after "ofbizBackground --shutdown". 

So I added a 30 sec sleep to trunk-manual-only.sh and it worked manually. I 
have now chained trunk-manual-only.sh in all-manual.sh (indirectly called by 
cron) and if it works tonight I will replace trunk-manual.sh content by 
trunk-manual-only.sh content and remove trunk-manual-only.sh




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9413) Update Currency Uom data

[Deepak Dixit (JIRA)]

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

Deepak Dixit updated OFBIZ-9413:

Attachment: list_three.xls

Attaching file for codes for historic denominations of currencies



> Update Currency Uom data 
> -
>
> Key: OFBIZ-9413
> URL: https://issues.apache.org/jira/browse/OFBIZ-9413
> Project: OFBiz
>  Issue Type: Improvement
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: list_three.xls
>
>
> While adding numericCode to currency UOM, I found that we need to update  
> some old currency UOM, as uomId has been updated. 
> https://www.currency-iso.org/en/home/tables/table-a1.html
> https://www.currency-iso.org/en/home/amendments.html
> Here is the short summary 
> *Following UomId not found*
> * Santo Domiongo(CDP)
> * Brazil (BRR)
> * Argentinian Austral(ARA)
> * Andoran peseta(ADP)
> * Maltese Lira (MTL)
> * Mexican Peso (old)(MXP)
> * Peruvian Inti(PEI)
> * Peruvian Sol(PES)
> * Tadzhikistani Ruble(TJR)
> *Following UOM using other currency * 
> Used Other
> * ANDORRA == Euro
> * Cyprus Pound(CYP) == Euro
> * Ecuador Sucre(ECS) =  USD
> * Estonian Krone(EEK) = EURO
> * Lithuanian Lita(LTL) == EURO
> * Latvian Lat(LVL) == EURO
> * Timor Escudo(TPE) == US Dollor
> *Following UOM has been changed*
> ||Old||New||
> |Belorussian Ruble(BYR)|Belarusian Ruble(BYN)|
> |Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)|
> |Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)|
> |Angolan Kwanza (AOK)|Kwanza (AOA)|
> |Afghani (AFA)|Afghani(AFN)|
> |Dominican Republic Peso(DRP)|Dominican Peso (DOP)|
> |Ghanian Cedi(GHC)|Ghana Cedi(GHS)|
> |Guinea Peso(GWP)| Guinean Franc(GNF)|
> |Kirghizstan Som(KIS)|KYRGYZSTAN  Som (KGS)|
> |Madagascan Franc(MGF)|Malagasy Ariary(MGA)|
> |Mozambique Metical(MZM)|Mozambique Metical(MZN)|
> |Nicaragua (NIC)|Cordoba Oro (NIO)|
> |New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)|
> |Poland(PLZ)|Zloty (PLN)|
> |Romanian Leu(ROL)|Romanian Leu(RON)|
> |Russian Rouble(RUR)|Russian Ruble(RUB)|
> |Sudanese Pound(SDP)|Sudanese Pound(SDG)|
> |Peru (SOL)|Sol (PEN)|
> |Surinam Guilder(SRG)|Surinam Dollar (SRD)|
> |Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)|
> |Uganda Shilling(UGS)|Uganda Shilling(UGX)|
> |Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)|
> |Venezuelan Bolivar(VEB)|Bolívar(VEF)|
> |Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)|
> |Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)|
> |Georgian Kupon (GEK)|GEORGIA Lari (GEL)|
> Some currency codes moved to historic denominations, we can remove them from 
> data.
> https://www.currency-iso.org/en/home/tables/table-a3.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051750#comment-16051750
 ] 

Deepak Dixit commented on OFBIZ-9409:
-

Created OFBIZ-9413 for currency uom update.

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9409.patch, OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (OFBIZ-9413) Update Currency Uom data

[Deepak Dixit (JIRA)]

Deepak Dixit created OFBIZ-9413:
---

 Summary: Update Currency Uom data 
 Key: OFBIZ-9413
 URL: https://issues.apache.org/jira/browse/OFBIZ-9413
 Project: OFBiz
  Issue Type: Improvement
Reporter: Deepak Dixit
Assignee: Deepak Dixit


While adding numericCode to currency UOM, I found that we need to update  some 
old currency UOM, as uomId has been updated. 
https://www.currency-iso.org/en/home/tables/table-a1.html
https://www.currency-iso.org/en/home/amendments.html

Here is the short summary 
*Following UomId not found*
* Santo Domiongo(CDP)
* Brazil (BRR)
* Argentinian Austral(ARA)
* Andoran peseta(ADP)
* Maltese Lira (MTL)
* Mexican Peso (old)(MXP)
* Peruvian Inti(PEI)
* Peruvian Sol(PES)
* Tadzhikistani Ruble(TJR)

*Following UOM using other currency * 
Used Other
* ANDORRA == Euro
* Cyprus Pound(CYP) == Euro
* Ecuador Sucre(ECS) =  USD
* Estonian Krone(EEK) = EURO
* Lithuanian Lita(LTL) == EURO
* Latvian Lat(LVL) == EURO
* Timor Escudo(TPE) == US Dollor

*Following UOM has been changed*

||Old||New||
|Belorussian Ruble(BYR)|Belarusian Ruble(BYN)|
|Bosnia-Herzogovinian Dinar(BAD)|Convertible Mark(BAM)|
|Azerbaijan Manat (AZM)|Azerbaijan Manat(AZN)|
|Angolan Kwanza (AOK)|Kwanza (AOA)|
|Afghani (AFA)|Afghani(AFN)|
|Dominican Republic Peso(DRP)|Dominican Peso (DOP)|
|Ghanian Cedi(GHC)|Ghana Cedi(GHS)|
|Guinea Peso(GWP)| Guinean Franc(GNF)|
|Kirghizstan Som(KIS)|KYRGYZSTANSom (KGS)|
|Madagascan Franc(MGF)|Malagasy Ariary(MGA)|
|Mozambique Metical(MZM)|Mozambique Metical(MZN)|
|Nicaragua (NIC)|Cordoba Oro (NIO)|
|New Israeli Shekel(NIS)|New Israeli Sheqel (ILS)|
|Poland(PLZ)|Zloty (PLN)|
|Romanian Leu(ROL)|Romanian Leu(RON)|
|Russian Rouble(RUR)|Russian Ruble(RUB)|
|Sudanese Pound(SDP)|Sudanese Pound(SDG)|
|Peru (SOL)|Sol (PEN)|
|Surinam Guilder(SRG)|Surinam Dollar (SRD)|
|Turkmenistani Manat(TMM)|Turkmenistan New Manat(TMT)|
|Uganda Shilling(UGS)|Uganda Shilling(UGX)|
|Uruguayan New Peso(UYP)|Uruguay Peso en Unidades Indexadas (URUIURUI)(UYI)|
|Venezuelan Bolivar(VEB)|Bolívar(VEF)|
|Zambian Kwacha(ZMK)|Zambian Kwacha(ZMW)|
|Zimbabwean Dollar(ZWD)|Zimbabwe Dollar(ZWL)|
|Georgian Kupon (GEK)|GEORGIA Lari (GEL)|

Some currency codes moved to historic denominations, we can remove them from 
data.
https://www.currency-iso.org/en/home/tables/table-a3.html






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051741#comment-16051741
 ] 

Deepak Dixit commented on OFBIZ-9409:
-

Thanks [~mbrohl] and [~jacques.le.roux] for review and suggestion. 

This has been committed at ofbiz-framework trunk r#1798907


> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9409.patch, OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (OFBIZ-9409) Add numeric code for Currency UOM

[Deepak Dixit (JIRA)]

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

Deepak Dixit closed OFBIZ-9409.
---
   Resolution: Done
Fix Version/s: Upcoming Release

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9409.patch, OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9409) Add numeric code for Currency UOM

[Deepak Dixit (JIRA)]

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

Deepak Dixit updated OFBIZ-9409:

Attachment: OFBIZ-9409.patch

Here is the patch with fieldtype update for numeericCode, 

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch, OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051728#comment-16051728
 ] 

Jacques Le Roux commented on OFBIZ-9409:


Hi Michael,

Ah, indeed, I did not look down to the end of the patch, and thought the 
numericCode field type was already numeric
 + 1 for numeric type for numericCode field

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9362) Screen rendering error on ViewForumMessage page

[Aditya Sharma (JIRA)]

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

Aditya Sharma updated OFBIZ-9362:
-
Description: 
Steps to reproduce:
1. Go to Ecommerce component 
(https://demo-trunk.ofbiz.apache.org/ecommerce/control/main)
2. Click on Gizmos from Browse Forum 
section.(https://demo-trunk.ofbiz.apache.org/ecommerce/control/showforum?forumId=GIZMOS)
3. Click on View button 
(https://demo-trunk.ofbiz.apache.org/ecommerce/control/ViewForumMessage?forumId=GIZMOS=thread10021=thread10021),
 the message box shows an error message with ScreenRendererException.

  was:
Steps to reproduce:
1. Go to Ecommerce component 
(https://demo-trunk-ofbiz.apache.org:8443/ecommerce/control/main)
2. Click on Gizmos from Browse Forum 
section.(https://demo-trunk-ofbiz.apache.org:8443/ecommerce/control/showforum?forumId=GIZMOS)
3. Click on View button 
(https://demo-trunk-ofbiz.apache.org:8443/ecommerce/control/ViewForumMessage?forumId=GIZMOS=thread10021=thread10021),
 the message box shows an error message with ScreenRendererException.


> Screen rendering error on ViewForumMessage page
> ---
>
> Key: OFBIZ-9362
> URL: https://issues.apache.org/jira/browse/OFBIZ-9362
> Project: OFBiz
>  Issue Type: Bug
>  Components: ecommerce
>Reporter: Aditya Sharma
>Priority: Trivial
>
> Steps to reproduce:
> 1. Go to Ecommerce component 
> (https://demo-trunk.ofbiz.apache.org/ecommerce/control/main)
> 2. Click on Gizmos from Browse Forum 
> section.(https://demo-trunk.ofbiz.apache.org/ecommerce/control/showforum?forumId=GIZMOS)
> 3. Click on View button 
> (https://demo-trunk.ofbiz.apache.org/ecommerce/control/ViewForumMessage?forumId=GIZMOS=thread10021=thread10021),
>  the message box shows an error message with ScreenRendererException.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9361) Newsletter can be subscribed with same email address multiple times

[Aditya Sharma (JIRA)]

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

Aditya Sharma updated OFBIZ-9361:
-
Description: 
Steps to regenerate:
1. Go to Ecommerce component 
(https://demo-trunk.ofbiz.apache.org/ecommerce/control/main)
2. In Sign Up For Contact List section from the left panel, select contactList 
for Newsletter.
3. Fill out the email address and Click on Subscribe button.
Try subscribing with the same email address for the newsletter. Email is again 
added to Newsletter subscription list even if it is already subscribed for it. 
Email address with pending and accepted status can be again added to the list 
with pending status.
Multiple entries are created in ContactListParty entity for the same 
preferredContactMechId.
At Service level, it should check if already an entry in pending or accepted 
status exists.

  was:
Steps to regenerate:
1. Go to Ecommerce component 
(https://demo-trunk-ofbiz.apache.org:8443/ecommerce/control/main)
2. In Sign Up For Contact List section from the left panel, select contactList 
for Newsletter.
3. Fill out the email address and Click on subscribe button.
Try subscribing with the same email address for the newsletter. Email is again 
added to Newsletter subscription list even if it is already subscribed for it. 
Email address with pending and accepted status can be again added to the list 
with pending status.
Multiple entries are created in ContactListParty entity for the same 
preferredContactMechId.
At Service level, it should check if already an entry in pending or accepted 
status exists.


> Newsletter can be subscribed with same email address multiple times
> ---
>
> Key: OFBIZ-9361
> URL: https://issues.apache.org/jira/browse/OFBIZ-9361
> Project: OFBiz
>  Issue Type: Bug
>  Components: ecommerce
>Reporter: Aditya Sharma
>Assignee: Aditya Sharma
>Priority: Trivial
>
> Steps to regenerate:
> 1. Go to Ecommerce component 
> (https://demo-trunk.ofbiz.apache.org/ecommerce/control/main)
> 2. In Sign Up For Contact List section from the left panel, select 
> contactList for Newsletter.
> 3. Fill out the email address and Click on Subscribe button.
> Try subscribing with the same email address for the newsletter. Email is 
> again added to Newsletter subscription list even if it is already subscribed 
> for it. Email address with pending and accepted status can be again added to 
> the list with pending status.
> Multiple entries are created in ContactListParty entity for the same 
> preferredContactMechId.
> At Service level, it should check if already an entry in pending or accepted 
> status exists.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9368) OEM Party Id field should have lookup on Edit Product page

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-9368:
---
Description: 
Steps to reproduce:
1. Go to Catalog component 
(https://demo-trunk.ofbiz.apache.org/catalog/control/main)
2. Click on Products from 
submenu.(https://demo-trunk.ofbiz.apache.org/catalog/control/FindProduct)
3. Provide search preference and click on Find button.
4. Click on any Product Id link 
(https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=WG-9943).
 
OEM Party Id is a text field with no look up. A user needs to know the correct 
partyId else it will give an error due to the violation of "Referential 
Integrity".

  was:
Steps to reproduce:
1. Go to Catalog component 
(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/main)
2. Click on Products from 
submenu.(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/FindProduct)
3. Provide search preference and click on Find button.
4. Click on any Product Id link 
(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/EditProduct?productId=WG-9943).
 
OEM Party Id is a text field with no look up. A user needs to know the correct 
partyId else it will give an error due to the violation of "Referential 
Integrity".


> OEM Party Id field should have lookup on Edit Product page
> --
>
> Key: OFBIZ-9368
> URL: https://issues.apache.org/jira/browse/OFBIZ-9368
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Reporter: Aditya Sharma
>Assignee: Aditya Sharma
>Priority: Trivial
> Attachments: OFBIZ-9368.patch
>
>
> Steps to reproduce:
> 1. Go to Catalog component 
> (https://demo-trunk.ofbiz.apache.org/catalog/control/main)
> 2. Click on Products from 
> submenu.(https://demo-trunk.ofbiz.apache.org/catalog/control/FindProduct)
> 3. Provide search preference and click on Find button.
> 4. Click on any Product Id link 
> (https://demo-trunk.ofbiz.apache.org/catalog/control/EditProduct?productId=WG-9943).
>  
> OEM Party Id is a text field with no look up. A user needs to know the 
> correct partyId else it will give an error due to the violation of 
> "Referential Integrity".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Michael Brohl (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051675#comment-16051675
 ] 

Michael Brohl commented on OFBIZ-9409:
--

Jacques, seems to be a misunderstanding: the patch already contains 
short-varchar as type for the numeric field, I think Pierre suggested to change 
this to a field type which only allows numbers.
I second this.

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Michael Brohl (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051676#comment-16051676
 ] 

Michael Brohl commented on OFBIZ-9409:
--

Hi [~deepak.dixit],

+1 for your patch with a change to use numeric field type for the numericCode 
field.

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9368) OEM Party Id field should have lookup on Edit Product page

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-9368:
---
Description: 
Steps to reproduce:
1. Go to Catalog component 
(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/main)
2. Click on Products from 
submenu.(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/FindProduct)
3. Provide search preference and click on Find button.
4. Click on any Product Id link 
(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/EditProduct?productId=WG-9943).
 
OEM Party Id is a text field with no look up. A user needs to know the correct 
partyId else it will give an error due to the violation of "Referential 
Integrity".

  was:
Steps to reproduce:
1. Go to Catalog component 
(https://demo-trunk-ofbiz.apache.org:8443/catalog/control/main)
2. Click on Products from 
submenu.(https://demo-trunk-ofbiz.apache.org:8443/catalog/control/FindProduct)
3. Provide search preference and click on Find button.
4. Click on any Product Id link 
(https://demo-trunk-ofbiz.apache.org:8443/catalog/control/EditProduct?productId=WG-9943).
 
OEM Party Id is a text field with no look up. A user needs to know the correct 
partyId else it will give an error due to the violation of "Referential 
Integrity".


> OEM Party Id field should have lookup on Edit Product page
> --
>
> Key: OFBIZ-9368
> URL: https://issues.apache.org/jira/browse/OFBIZ-9368
> Project: OFBiz
>  Issue Type: Improvement
>  Components: product
>Reporter: Aditya Sharma
>Assignee: Aditya Sharma
>Priority: Trivial
> Attachments: OFBIZ-9368.patch
>
>
> Steps to reproduce:
> 1. Go to Catalog component 
> (https://demo-trunk.ofbiz.apache.org:8443/catalog/control/main)
> 2. Click on Products from 
> submenu.(https://demo-trunk.ofbiz.apache.org:8443/catalog/control/FindProduct)
> 3. Provide search preference and click on Find button.
> 4. Click on any Product Id link 
> (https://demo-trunk.ofbiz.apache.org:8443/catalog/control/EditProduct?productId=WG-9943).
>  
> OEM Party Id is a text field with no look up. A user needs to know the 
> correct partyId else it will give an error due to the violation of 
> "Referential Integrity".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051656#comment-16051656
 ] 

Jacques Le Roux commented on OFBIZ-9409:


Hi Pierre,

Why would you want to use the 'short-varchar' field type when it's only a 3 
digits code?

> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (OFBIZ-9409) Add numeric code for Currency UOM

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051599#comment-16051599
 ] 

Deepak Dixit edited comment on OFBIZ-9409 at 6/16/17 8:41 AM:
--

Thanks Pierre for review, I  took reference from geo.geoSecCode that store 
numericCode value for Geo

I think we can use numeric as field type for this case. 



was (Author: deepak.dixit):
Thanks Pierre for review, I simply took reference from geo.geoSecCode that used 
to store numericCode value for Geo

I think we can use numeric as field type for this case. 


> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9409) Add numeric code for Currency UOM

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051599#comment-16051599
 ] 

Deepak Dixit commented on OFBIZ-9409:
-

Thanks Pierre for review, I simply took reference from geo.geoSecCode that used 
to store numericCode value for Geo

I think we can use numeric as field type for this case. 


> Add numeric code for Currency UOM
> -
>
> Key: OFBIZ-9409
> URL: https://issues.apache.org/jira/browse/OFBIZ-9409
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Deepak Dixit
>Assignee: Deepak Dixit
> Attachments: OFBIZ-9409.patch
>
>
> The three-digit numeric code is useful when currency codes need to be 
> understood in countries that do not use Latin scripts and for computerised 
> systems. Where possible the 3 digit numeric code is the same as the numeric 
> country code.
> https://www.iso.org/iso-4217-currency-codes.html
> https://www.currency-iso.org/en/home/tables/table-a1.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9410) Software not usable all standard installs failed

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-9410:
---
Description: 
{code}
Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at 
DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. 
HTTP method names must be tokens
at 
org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at 
DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. 
HTTP method names must be tokens
at 
org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at 
DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. 
HTTP method names must be tokens
at 
org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
{code}

  was:
Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at 
DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. 
HTTP method names must be tokens
at 
org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor process
INFO: Error parsing HTTP request 

[jira] [Reopened] (OFBIZ-9410) Software not usable all standard installs failed

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux reopened OFBIZ-9410:

  Assignee: Jacques Le Roux

I reopen to clarify the status of R13.07

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
>Assignee: Jacques Le Roux
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9410.patch
>
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (OFBIZ-9410) Software not usable all standard installs failed

[Jacques Le Roux (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051531#comment-16051531
 ] 

Jacques Le Roux edited comment on OFBIZ-9410 at 6/16/17 7:51 AM:
-

Hi Scott,

I'm very sorry for this error in our 16.11.02 release, thank you for your 
report!

This was in broken by OFBIZ-8202 with r1787949 and fixed in the same issue with 
r1798179, thank you Deepak!

I think I missed to attach a patch for easier fix. I will do here and in 
OFBIZ-8202.

Now I'm surprised that you encouter the same issue in R13.07. I guess it's 
another one, could you please check and report? Thanks!


was (Author: jacques.le.roux):
Hi Scott,

I'm very sorry for this error in our 16.01.02 release, thank you for your 
report!

This was in broken by OFBIZ-8202 with r1787949 and fixed in the same issue with 
r1798179, thank you Deepak!

I think I missed to attach a patch for easier fix. I will do here and in 
OFBIZ-8202.

Now I'm surprised that you encouter the same issue in R13.07. I guess it's 
another one, could you please check and report? Thanks!

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9410.patch
>
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> 

[jira] [Updated] (OFBIZ-8202) Use try-with-resources statement wherever it's possible

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-8202:
---
Fix Version/s: 16.11.03

> Use try-with-resources statement wherever it's possible
> ---
>
> Key: OFBIZ-8202
> URL: https://issues.apache.org/jira/browse/OFBIZ-8202
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Upcoming Release, 16.11.03
>
> Attachments: OFBIZ-9410.patch
>
>
> This is a non functional change task.
> I have already commited some such changes for OFBIZ-8115 and at r1759082



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-8202) Use try-with-resources statement wherever it's possible

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-8202:
---
Attachment: OFBIZ-9410.patch

The OFBIZ-9410.patch should be used to fix the issue introduced by r1787949 
[reported by Daniel Coric on user ML|https://s.apache.org/vFYA] It concerns 
only the 16.11.02 release.

> Use try-with-resources statement wherever it's possible
> ---
>
> Key: OFBIZ-8202
> URL: https://issues.apache.org/jira/browse/OFBIZ-8202
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Upcoming Release, 16.11.03
>
> Attachments: OFBIZ-9410.patch
>
>
> This is a non functional change task.
> I have already commited some such changes for OFBIZ-8115 and at r1759082



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (OFBIZ-9410) Software not usable all standard installs failed

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux updated OFBIZ-9410:
---
Attachment: OFBIZ-9410.patch

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9410.patch
>
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

[Hans Bakker (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051469#comment-16051469
 ] 

Hans Bakker commented on OFBIZ-9410:


Thank you Scott, we always welcome new people to improve our product.

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
> Fix For: Upcoming Release
>
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (OFBIZ-9410) Software not usable all standard installs failed

[Scott Provost (JIRA)]

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

Scott Provost resolved OFBIZ-9410.
--
   Resolution: Fixed
Fix Version/s: Upcoming Release

I will write a more tolerant testing script and attempt to independently verify 
for Debian 8 and Centos 7  

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
> Fix For: Upcoming Release
>
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051452#comment-16051452
 ] 

Deepak Dixit commented on OFBIZ-9410:
-

Hi Hans, 

EntityListIterator with no transaction error has been fix at 
http://svn.apache.org/viewvc?rev=1798179=rev

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

[Hans Bakker (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051446#comment-16051446
 ] 

Hans Bakker commented on OFBIZ-9410:


As I said, sure this problem needs to be solved,  it looks like there is an 
error in the automatic extension of order subscriptions.

However you can use the system even after three errors.

Thank you for reporting!

Regards,
Hans

> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051444#comment-16051444
 ] 

Deepak Dixit commented on OFBIZ-9410:
-

>>It may reject after 3 stack traces
Let me check for multiple hit using incorrect port.

>>What does you automated testing system do?
I am asking that are you using any automated script that access ofbiz? 
It might possible that it access ofbiz using incorrect url (https protocol with 
8080 port)

>> Should special instruction be added to the install instruction to ignore
errors?
There is an entry in README.md file 
{code}
### Visit OFBiz through your browser:

[Order Back Office](https://localhost:8443/ordermgr)

[Accounting Back Office](https://localhost:8443/accounting)

[Administrator interface](https://localhost:8443/webtools)

You can log in with the user __admin__ and password __ofbiz__.

{code}


> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at 

[jira] [Commented] (OFBIZ-9410) Software not usable all standard installs failed

[Scott Provost (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-9410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051434#comment-16051434
 ] 

Scott Provost commented on OFBIZ-9410:
--

It may reject after 3 stack traces. What does you automated testing system
do?
Should special instruction be added to the install instruction to ignore
errors?

On Fri, Jun 16, 2017 at 12:59 AM, Deepak Dixit (JIRA) 



> Software not usable all standard installs failed 
> -
>
> Key: OFBIZ-9410
> URL: https://issues.apache.org/jira/browse/OFBIZ-9410
> Project: OFBiz
>  Issue Type: Bug
>  Components: ALL COMPONENTS
>Affects Versions: Release Branch 13.07, 16.11.02
> Environment: Several Linux Versions all Java 1.8
> 1.3 and 1.6 OFBiz
>Reporter: Scott Provost
>
> Jun 15, 2017 8:50:03 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:26 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)
> Jun 15, 2017 8:50:50 AM org.apache.coyote.http11.AbstractHttp11Processor 
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at 
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in method name. 
> HTTP method names must be tokens
>   at 
> org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:233)
>   at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1017)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1519)
>   at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1475)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)