date:20170415

Re: svn commit: r1791513 - /ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz /base/start/Config.java

2017-04-15 Thread Jacques Le Roux


Thanks a lot for that Taher

Jacques


Le 15/04/2017 à 16:51, ta...@apache.org a écrit :

Author: taher
Date: Sat Apr 15 14:51:13 2017
New Revision: 1791513

URL: http://svn.apache.org/viewvc?rev=1791513=rev
Log:
Fixed: a bug related admin port blocking on contexts other than "start"

This commit has reference to issue OFBIZ-9196, commit r1787627 and the
discussion thread mentioned below. The fix was already applied for trunk
in the above mentioned commit but cannot be ported due to incompatible
code bases, hence the need for this commit.

Hopefully this commit will end all buildbot fail messages that occur
randomly due to port conflict on multiple running instances

https://s.apache.org/xfxS

Modified:
 
ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz/base/start/Config.java

Modified: 
ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz/base/start/Config.java
URL: 
http://svn.apache.org/viewvc/ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz/base/start/Config.java?rev=1791513=1791512=1791513=diff
==
--- 
ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz/base/start/Config.java
 (original)
+++ 
ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz/base/start/Config.java
 Sat Apr 15 14:51:13 2017
@@ -225,8 +225,7 @@ public final class Config {
  int calculatedAdminPort;
  try {
  calculatedAdminPort = Integer.parseInt(adminPortStr);
-calculatedAdminPort = calculatedAdminPort != 0 ? 
calculatedAdminPort : 10523; // This is necessary because the ASF machines 
don't allow ports 1 to 3, see  INFRA-6790
-calculatedAdminPort += portOffsetValue;
+calculatedAdminPort = calculatedAdminPort != 0 ? 
calculatedAdminPort + portOffsetValue : 0;
  } catch (Exception e) {
  System.out.println("Error while parsing admin port number (so default 
to 10523) = " + e);
  calculatedAdminPort = 10523;

Re: User Acceptance Test Cases For Ecommerce 14.12

2017-04-15 Thread Taher Alkhateeb

Great work Rishi, keep them coming!

I wonder if you can also create some selenium scripts to automate some of
these tests and add them to the wiki?

On Sat, Apr 15, 2017 at 6:30 PM, Rishi Solanki 
wrote:

> Folks,
>
> We have completed the first draft of the document for the Ecommerce
> Component
>  and
> added UATs for all the user stories. Also we have follow the pattern to use
> h4 h5 and h6 headings in the documents so that user can easily navigate to
> the user story/ user acceptance test she wants.
>
> As a first draft we tried to cover all known possible tests, but it might
> be possible we missed something. We would like to get feedback from
> community so that we can make it better in terms of usability, readability
> and number of items we have tested.
>
> Please review and share your feedback on each item, like language we use,
> document formation, use cases we covered etc. We would try to cover them in
> our next draft and improve the document. And once finalize we would start
> using that pattern going forward for all such documents.
>
> Thanks!
>
>
> Rishi Solanki
> Sr. Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki 
> wrote:
>
> > Folks,
> >
> > Added two more UAT as Category Navigation and Product Search
> > . I
> > observe some scope of improvements like UAT writing aren't following
> common
> > patterns, I'll review and fix them soon.
> >
> > Soon we would add remaining in the ecommerce area, looking for your
> > feedback and suggestions on it.
> >
> >
> > Rishi Solanki
> > Sr. Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
> > On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> >> Thanks Rishi,
> >>
> >> Indeed I needed a clarification, sorry for that.
> >>
> >> It's a great initiative, OFBiz will then really be at professional
> >> standards, and that's great!
> >>
> >> I agree that we have first to create and document these UAT and then
> >> think about a tool to run them.
> >> Cucumber seems the best tool for that to me.  I also know that Gil
> >> (Portenseigne) from Néréide has begun to use Cucumber for a custom
> project,
> >> hence my haste :)
> >>
> >> Jacques
> >>
> >>
> >>
> >> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
> >>
> >>> Thanks Jacques for your reply and raising concerns. It seems that, I
> was
> >>> not clear enough. Let me try to rephrase what we are doing. If you
> >>> observe
> >>> then Pranay has created new hierachy for each release like 14.12, 15.12
> >>> ...
> >>> so on.
> >>>
> >>> For each release we have the user stories, and we are adding UATs for
> >>> each
> >>> user story. For each user story we are discussing the cases we should
> >>> test
> >>> manually and also try them to dicuss on the mailing list (user/dev).
> Once
> >>> we are sure, we document and test the cases (manually) and put the
> >>> results
> >>> in the Actual results and Pass/Fail.
> >>>
> >>> Please note that, before documenting anything as Pass or Fail we are
> >>> really
> >>> running that scenario. The intention of doing this, we can say that the
> >>> released branches of OFBiz are tested on certain scenarios and all get
> >>> passed. After completing this activity, we as a community can say 14.12
> >>> branch tested for say 1000 user acceptance test cases and out of them
> 950
> >>> get passed and 50 are reported and fail for that branch. Once we
> complete
> >>> this activity, we could start fixing them.
> >>>
> >>> For the same we have started multiple email threads to get the feedback
> >>> from community, so that we could get more cases for the user stories.
> In
> >>> other words, we have automated tests with us, but this time we are
> trying
> >>> to add documents for the manual tests user could see and increase in
> >>> faith
> >>> on each relase.
> >>>
> >>> I hope I'm clear this time :-). And yes I agree on the fact that we
> >>> should
> >>> think on automating these tests to run them frequently. And I think for
> >>> that we again need what to tests get documented. We can assume it as
> >>> first
> >>> step towards automation.
> >>>
> >>> PS: Team, please add more details if I miss something.
> >>>
> >>>
> >>> Rishi Solanki
> >>> Manager, Enterprise Software Development
> >>> HotWax Systems Pvt. Ltd.
> >>> Direct: +91-9893287847
> >>> http://www.hotwaxsystems.com
> >>>
> >>> On Sun, Jan 22, 2017 at 5:00 PM, Jacques Le Roux <
> >>> jacques.le.r...@les7arts.com> wrote:
> >>>
> >>> Thanks Rishi,
> 
>  This is interesting, do you envision a mean to automate these tests
> and
>  run them frequently?
> 
>  Say

Re: User Acceptance Test Cases For Ecommerce 14.12

2017-04-15 Thread Rishi Solanki

Folks,

We have completed the first draft of the document for the Ecommerce
Component
 and
added UATs for all the user stories. Also we have follow the pattern to use
h4 h5 and h6 headings in the documents so that user can easily navigate to
the user story/ user acceptance test she wants.

As a first draft we tried to cover all known possible tests, but it might
be possible we missed something. We would like to get feedback from
community so that we can make it better in terms of usability, readability
and number of items we have tested.

Please review and share your feedback on each item, like language we use,
document formation, use cases we covered etc. We would try to cover them in
our next draft and improve the document. And once finalize we would start
using that pattern going forward for all such documents.

Thanks!


Rishi Solanki
Sr. Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Sat, Feb 18, 2017 at 9:49 PM, Rishi Solanki 
wrote:

> Folks,
>
> Added two more UAT as Category Navigation and Product Search
> . I
> observe some scope of improvements like UAT writing aren't following common
> patterns, I'll review and fix them soon.
>
> Soon we would add remaining in the ecommerce area, looking for your
> feedback and suggestions on it.
>
>
> Rishi Solanki
> Sr. Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Tue, Jan 24, 2017 at 7:01 PM, Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
>> Thanks Rishi,
>>
>> Indeed I needed a clarification, sorry for that.
>>
>> It's a great initiative, OFBiz will then really be at professional
>> standards, and that's great!
>>
>> I agree that we have first to create and document these UAT and then
>> think about a tool to run them.
>> Cucumber seems the best tool for that to me.  I also know that Gil
>> (Portenseigne) from Néréide has begun to use Cucumber for a custom project,
>> hence my haste :)
>>
>> Jacques
>>
>>
>>
>> Le 23/01/2017 à 08:05, Rishi Solanki a écrit :
>>
>>> Thanks Jacques for your reply and raising concerns. It seems that, I was
>>> not clear enough. Let me try to rephrase what we are doing. If you
>>> observe
>>> then Pranay has created new hierachy for each release like 14.12, 15.12
>>> ...
>>> so on.
>>>
>>> For each release we have the user stories, and we are adding UATs for
>>> each
>>> user story. For each user story we are discussing the cases we should
>>> test
>>> manually and also try them to dicuss on the mailing list (user/dev). Once
>>> we are sure, we document and test the cases (manually) and put the
>>> results
>>> in the Actual results and Pass/Fail.
>>>
>>> Please note that, before documenting anything as Pass or Fail we are
>>> really
>>> running that scenario. The intention of doing this, we can say that the
>>> released branches of OFBiz are tested on certain scenarios and all get
>>> passed. After completing this activity, we as a community can say 14.12
>>> branch tested for say 1000 user acceptance test cases and out of them 950
>>> get passed and 50 are reported and fail for that branch. Once we complete
>>> this activity, we could start fixing them.
>>>
>>> For the same we have started multiple email threads to get the feedback
>>> from community, so that we could get more cases for the user stories. In
>>> other words, we have automated tests with us, but this time we are trying
>>> to add documents for the manual tests user could see and increase in
>>> faith
>>> on each relase.
>>>
>>> I hope I'm clear this time :-). And yes I agree on the fact that we
>>> should
>>> think on automating these tests to run them frequently. And I think for
>>> that we again need what to tests get documented. We can assume it as
>>> first
>>> step towards automation.
>>>
>>> PS: Team, please add more details if I miss something.
>>>
>>>
>>> Rishi Solanki
>>> Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>> On Sun, Jan 22, 2017 at 5:00 PM, Jacques Le Roux <
>>> jacques.le.r...@les7arts.com> wrote:
>>>
>>> Thanks Rishi,

 This is interesting, do you envision a mean to automate these tests and
 run them frequently?

 Say either on each build (using BuildBot for instance), or on another
 frequency if they happens to be at term longer than our commit frequency
 would support.

 So the question is do you plan to use a tool for that? I say that
 because
 it seems to me that Cucumber (MIT license) could be used for that...

 Jacques


 Le 21/01/2017 à 16:51, Rishi Solanki a écrit :

 Devs,
>
> We have started working on few user stories mentioned at
>

buildbot failure in on ofbiz-branch16

2017-04-15 Thread buildbot

The Buildbot has detected a new failure on builder ofbiz-branch16 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch16/builds/38

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release16.11] 1791513
Blamelist: taher

BUILD FAILED: failed shell_2

Sincerely,
 -The Buildbot

buildbot success in on ofbiz-branch16

2017-04-15 Thread buildbot

The Buildbot has detected a restored build on builder ofbiz-branch16 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch16/builds/37

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release16.11] 1791497
Blamelist: deepak

Build succeeded!

Sincerely,
 -The Buildbot

buildbot failure in on ofbiz-branch16

2017-04-15 Thread buildbot

The Buildbot has detected a new failure on builder ofbiz-branch16 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch16/builds/36

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release16.11] 1791492
Blamelist: deepak

BUILD FAILED: failed shell_2

Sincerely,
 -The Buildbot

buildbot success in on ofbiz-branch16

2017-04-15 Thread buildbot

The Buildbot has detected a restored build on builder ofbiz-branch16 while 
building . Full details are available at:
https://ci.apache.org/builders/ofbiz-branch16/builds/35

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz16-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release16.11] 1791476
Blamelist: deepak

Build succeeded!

Sincerely,
 -The Buildbot

Re: Validating telecom numbers

2017-04-15 Thread Pierre Smits

I suggest to open a 'New Feature' (or otherwise an Improvement) issue in
JIRA.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Sat, Apr 15, 2017 at 11:00 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Sounds great, apart that in demo I was surprised to have to pass FR
> instead of 33 for France "CLDR two-letter region code" seems a new (and
> better) std
>
> https://www.google.fr/search?q=CLDR+two-letter+region+code)=UTF-8
>
> Jacques
>
>
>
> Le 15/04/2017 à 09:39, Deepak Dixit a écrit :
>
>> +1 for the idea.
>>
>> Thanks Scott, I think here is the google phone number library
>> https://github.com/googlei18n/libphonenumber
>> Demo: http://libphonenumber.appspot.com/
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>>
>> On Sat, Apr 15, 2017 at 5:28 AM, Scott Gray > >
>> wrote:
>>
>> I think Google has a phone number library that could be put to use to take
>>> the heavy lifting off our shoulders.
>>>
>>> Regards
>>> Scott
>>>
>>> On 15/04/2017 00:53, "Pierre Smits"  wrote:
>>>
>>> For (to be) OFBiz definitions, I suggest to review ITU and country

>>> policies
>>>
 regarding the various kinds of telephone definitions and numbering

>>> schemas.
>>>
 Best regards,

 Pierre Smits

 ORRTIZ.COM 
 OFBiz based solutions & services

 OFBiz Extensions Marketplace
 http://oem.ofbizci.net/oci-2/

 On Fri, Apr 14, 2017 at 2:41 PM, Jacques Le Roux <
 jacques.le.r...@les7arts.com> wrote:

 +1, for consistency we should follow the way CountryAddressFormat works
>
> Jacques
>
>
>
> Le 14/04/2017 à 14:24, Taher Alkhateeb a écrit :
>
> +1 very cool idea. We might need a Type entity or just place it in
>> enumeration or something like that.
>>
>> On Apr 14, 2017 2:22 PM, "Suraj Khurana" >
> com

> wrote:
>>
>> Hi devs,
>>
>> I was wondering for some sort of data mechanism that could validate
>>
> if a
>>>
 phone belongs to a particular country/geo.
>> Digging deeper, found that we have already some entities which can
>>
> handle

> these scenarios like *CountryTeleCode.*
>>
>> There should be some sort of mechanism to validate the country
>>
> telephone
>>>
 number formats
>> In real time scenarios, there are many mechanisms by which you can get
>> telephone number info such as a CSV or any XML data file etc.
>>
>> We already have *CountryAddressFormat* to check address format which
>>
> has
>>>
 *postalCodeRegex* field.
>>
>> *Proposal*:
>> There can be an entity which can have a similar mechanism (regex
>>
> pattern,

> telephone number length etc.) for validating telephone numbers as
>>
> well.
>>>
 If it looks good, I will create a Jira ticket and start working on it.
>>
>> --
>> Thanks and Regards,
>> Suraj Khurana
>> Sr. Enterprise Software Engineer
>> HotWax Systems  - *The global leader
>>
> in
>>>
 innovative enterprise commerce solutions **powered by Apache OFBiz.*
>> 
>>
>>
>>
>

Re: Validating telecom numbers

2017-04-15 Thread Jacques Le Roux


Sounds great, apart that in demo I was surprised to have to pass FR instead of 33 for 
France "CLDR two-letter region code" seems a new (and better) std

https://www.google.fr/search?q=CLDR+two-letter+region+code)=UTF-8

Jacques


Le 15/04/2017 à 09:39, Deepak Dixit a écrit :

+1 for the idea.

Thanks Scott, I think here is the google phone number library
https://github.com/googlei18n/libphonenumber
Demo: http://libphonenumber.appspot.com/

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sat, Apr 15, 2017 at 5:28 AM, Scott Gray 
wrote:


I think Google has a phone number library that could be put to use to take
the heavy lifting off our shoulders.

Regards
Scott

On 15/04/2017 00:53, "Pierre Smits"  wrote:


For (to be) OFBiz definitions, I suggest to review ITU and country

policies

regarding the various kinds of telephone definitions and numbering

schemas.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Fri, Apr 14, 2017 at 2:41 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


+1, for consistency we should follow the way CountryAddressFormat works

Jacques



Le 14/04/2017 à 14:24, Taher Alkhateeb a écrit :


+1 very cool idea. We might need a Type entity or just place it in
enumeration or something like that.

On Apr 14, 2017 2:22 PM, "Suraj Khurana"  - *The global leader

in

innovative enterprise commerce solutions **powered by Apache OFBiz.*

Re: Validating telecom numbers

2017-04-15 Thread Pierre Smits

Thanks, Deepak.

And fortunately that has a good license too.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Sat, Apr 15, 2017 at 9:39 AM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:

> +1 for the idea.
>
> Thanks Scott, I think here is the google phone number library
> https://github.com/googlei18n/libphonenumber
> Demo: http://libphonenumber.appspot.com/
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
>
> On Sat, Apr 15, 2017 at 5:28 AM, Scott Gray 
> wrote:
>
> > I think Google has a phone number library that could be put to use to
> take
> > the heavy lifting off our shoulders.
> >
> > Regards
> > Scott
> >
> > On 15/04/2017 00:53, "Pierre Smits"  wrote:
> >
> > > For (to be) OFBiz definitions, I suggest to review ITU and country
> > policies
> > > regarding the various kinds of telephone definitions and numbering
> > schemas.
> > >
> > > Best regards,
> > >
> > > Pierre Smits
> > >
> > > ORRTIZ.COM 
> > > OFBiz based solutions & services
> > >
> > > OFBiz Extensions Marketplace
> > > http://oem.ofbizci.net/oci-2/
> > >
> > > On Fri, Apr 14, 2017 at 2:41 PM, Jacques Le Roux <
> > > jacques.le.r...@les7arts.com> wrote:
> > >
> > > > +1, for consistency we should follow the way CountryAddressFormat
> works
> > > >
> > > > Jacques
> > > >
> > > >
> > > >
> > > > Le 14/04/2017 à 14:24, Taher Alkhateeb a écrit :
> > > >
> > > >> +1 very cool idea. We might need a Type entity or just place it in
> > > >> enumeration or something like that.
> > > >>
> > > >> On Apr 14, 2017 2:22 PM, "Suraj Khurana"
>  > > com
> > > >> >
> > > >> wrote:
> > > >>
> > > >> Hi devs,
> > > >>
> > > >> I was wondering for some sort of data mechanism that could validate
> > if a
> > > >> phone belongs to a particular country/geo.
> > > >> Digging deeper, found that we have already some entities which can
> > > handle
> > > >> these scenarios like *CountryTeleCode.*
> > > >>
> > > >> There should be some sort of mechanism to validate the country
> > telephone
> > > >> number formats
> > > >> In real time scenarios, there are many mechanisms by which you can
> get
> > > >> telephone number info such as a CSV or any XML data file etc.
> > > >>
> > > >> We already have *CountryAddressFormat* to check address format which
> > has
> > > >> *postalCodeRegex* field.
> > > >>
> > > >> *Proposal*:
> > > >> There can be an entity which can have a similar mechanism (regex
> > > pattern,
> > > >> telephone number length etc.) for validating telephone numbers as
> > well.
> > > >>
> > > >> If it looks good, I will create a Jira ticket and start working on
> it.
> > > >>
> > > >> --
> > > >> Thanks and Regards,
> > > >> Suraj Khurana
> > > >> Sr. Enterprise Software Engineer
> > > >> HotWax Systems  - *The global leader
> > in
> > > >> innovative enterprise commerce solutions **powered by Apache OFBiz.*
> > > >> 
> > > >>
> > > >>
> > > >
> > >
> >
>

Re: Validating telecom numbers

2017-04-15 Thread Deepak Dixit

+1 for the idea.

Thanks Scott, I think here is the google phone number library
https://github.com/googlei18n/libphonenumber
Demo: http://libphonenumber.appspot.com/

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Sat, Apr 15, 2017 at 5:28 AM, Scott Gray 
wrote:

> I think Google has a phone number library that could be put to use to take
> the heavy lifting off our shoulders.
>
> Regards
> Scott
>
> On 15/04/2017 00:53, "Pierre Smits"  wrote:
>
> > For (to be) OFBiz definitions, I suggest to review ITU and country
> policies
> > regarding the various kinds of telephone definitions and numbering
> schemas.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Fri, Apr 14, 2017 at 2:41 PM, Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> > > +1, for consistency we should follow the way CountryAddressFormat works
> > >
> > > Jacques
> > >
> > >
> > >
> > > Le 14/04/2017 à 14:24, Taher Alkhateeb a écrit :
> > >
> > >> +1 very cool idea. We might need a Type entity or just place it in
> > >> enumeration or something like that.
> > >>
> > >> On Apr 14, 2017 2:22 PM, "Suraj Khurana"  > com
> > >> >
> > >> wrote:
> > >>
> > >> Hi devs,
> > >>
> > >> I was wondering for some sort of data mechanism that could validate
> if a
> > >> phone belongs to a particular country/geo.
> > >> Digging deeper, found that we have already some entities which can
> > handle
> > >> these scenarios like *CountryTeleCode.*
> > >>
> > >> There should be some sort of mechanism to validate the country
> telephone
> > >> number formats
> > >> In real time scenarios, there are many mechanisms by which you can get
> > >> telephone number info such as a CSV or any XML data file etc.
> > >>
> > >> We already have *CountryAddressFormat* to check address format which
> has
> > >> *postalCodeRegex* field.
> > >>
> > >> *Proposal*:
> > >> There can be an entity which can have a similar mechanism (regex
> > pattern,
> > >> telephone number length etc.) for validating telephone numbers as
> well.
> > >>
> > >> If it looks good, I will create a Jira ticket and start working on it.
> > >>
> > >> --
> > >> Thanks and Regards,
> > >> Suraj Khurana
> > >> Sr. Enterprise Software Engineer
> > >> HotWax Systems  - *The global leader
> in
> > >> innovative enterprise commerce solutions **powered by Apache OFBiz.*
> > >> 
> > >>
> > >>
> > >
> >
>

Re: svn commit: r1791513 - /ofbiz/branches/release16.11/framework/start/src/main/java/org/apache/ofbiz /base/start/Config.java

Re: User Acceptance Test Cases For Ecommerce 14.12

Re: User Acceptance Test Cases For Ecommerce 14.12

buildbot failure in on ofbiz-branch16

buildbot success in on ofbiz-branch16

buildbot failure in on ofbiz-branch16

buildbot success in on ofbiz-branch16

Re: Validating telecom numbers

Re: Validating telecom numbers

Re: Validating telecom numbers

Re: Validating telecom numbers

11 matches

Site Navigation

Mail list logo

Footer information