Re: [Discussion] documentation framework for OFBiz

[Paul Foxworthy]

On 9 November 2017 at 18:26, Taher Alkhateeb 
wrote:


> Anyway I don't see a reason so far to use pandoc to publish to pdf.
> Asciidoctor can publish to html, docbook, pdf and others.


Thanks Taher. That's fine by me.

Cheers

Paul Foxworthy

-- 
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Australia

Phone: +61 3 9585 6788
Web: http://www.coherentsoftware.com.au/
Email: i...@coherentsoftware.com.au

Re: Clarification about Jira version named "16.11.02"

[Deepak Dixit]

Thanks Jacopo for detail,

I found some some issues that have Trunk as fix version, I think it should
be "Upcoming Release"

And if fixes backported to older release it should set as described by
Jacopo in this thread.

Please correct me if I am missing something :)

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

On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxsystems.com> wrote:

> Hi all,
>
> whenever a Jira ticket is resolved and the fix is back-ported to the 16.11
> branch, please add the version "16.11.02" to the "Fix Version/s" field: in
> fact 16.11.02 is the first release of the 16.11 branch in which the fix
> will be published.
>
> As a side note, when you report a bug that affects the 16.11 branch you can
> set:
> "Affects Version/s" = "Release Branch 16.11"
> However it would be nice to know if the same bug affects also the release
> 16.11.01; if this is the case then please set:
> "Affects Version/s" = "16.11.01"
> In this case it is not necessary to specify "Release Branch 16.11" because
> it is implied that if the bug affects the "16.11.01" release then it also
> affected the 16.11 branch.
> In short: "Release Branch 16.11" should only be used when the bug was
> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
> or if you don't know if the bug affects the 16.11.01 release.
>
> Regards,
>
> Jacopo
>

Re: Handle service response effectively

[Aditya Sharma]

Indeed +1

Thanks and Regards,

*Aditya Sharma* | Enterprise Software Engineer
HotWax Systems 


On Thu, Nov 9, 2017 at 1:43 PM, Akash Jain 
wrote:

> +1
>
> Thanks and Regards
> --
> Akash Jain
>
> On Tue, Nov 7, 2017 at 4:43 PM, Suraj Khurana <
> suraj.khur...@hotwaxsystems.com> wrote:
>
> > Hello,
> >
> > I noticed many occurrences where service response is not handled properly
> > and it leads to taking more time while debugging issues.
> > IMO, every service calling from java/groovy must handle errors by service
> > util methods such as *isError*, *reutrnError *etc. and similarly in case
> of
> > XML <*call-service*, there should be <*check-error*/> to make sure
> service
> > was executed successfully.
> >
> > Apart from this, one suggestion is to include *Debug.logError *in
> > *ServiceUtil.returnProblem *so that in case of any error occurred and
> > handled, it will always be logged on the console.
> >
> > Please let me know your thoughts on this.
> >
> > --
> > Thanks and Regards,
> > *Suraj Khurana* | Sr. Enterprise Software Engineer
> > *HotWax Commerce*  by  *HotWax Systems*
> > Plot no. 80, Scheme no. 78, Vijay Nagar, Indore, M.P. India 452010
> >
>

Re: Handle service response effectively

[Akash Jain]

+1

Thanks and Regards
--
Akash Jain

On Tue, Nov 7, 2017 at 4:43 PM, Suraj Khurana <
suraj.khur...@hotwaxsystems.com> wrote:

> Hello,
>
> I noticed many occurrences where service response is not handled properly
> and it leads to taking more time while debugging issues.
> IMO, every service calling from java/groovy must handle errors by service
> util methods such as *isError*, *reutrnError *etc. and similarly in case of
> XML <*call-service*, there should be <*check-error*/> to make sure service
> was executed successfully.
>
> Apart from this, one suggestion is to include *Debug.logError *in
> *ServiceUtil.returnProblem *so that in case of any error occurred and
> handled, it will always be logged on the console.
>
> Please let me know your thoughts on this.
>
> --
> Thanks and Regards,
> *Suraj Khurana* | Sr. Enterprise Software Engineer
> *HotWax Commerce*  by  *HotWax Systems*
> Plot no. 80, Scheme no. 78, Vijay Nagar, Indore, M.P. India 452010
>