OFBiz › OFBiz - Dev

/framework/example

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

11 messages Options

BJ Freeman

/framework/example

I am sometime, a slow dumb witted learner.
I have to have examples, and most importantly something that ties things
to gather step by step, from a code point on view.

I have been looking for a way to put this down for others that have a
hard time figuring things out.

here is an example.

in the /framework/example/webapp/example/WEB-INF/web.xml

I would like to see





<context-param>
<param-name>localDispatcherName</param-name><param-value>example</param-value>
<description>A unique name used to identify/recognize the local
dispatcher for the Service Engine</description>
</context-param>


<param-name>entityDelegatorName</param-name><param-value>default</param-value>
<description>The Name of the Entity Delegator to use, defined in
entityengine.xml</description>
</context-param>

I am willing to add what I have learned this way into the example.
Hopefully others will do the same

SkipDever

RE: /framework/example

BJ

You are not alone here. Ofbiz is a great huge beast that unless you have
lived with it for years, you cannot possibly comprehend it all. Sadly,
comments, and examples are fairly minimal. Fortunately, documentation is
slowly improving. Now if everyone would just comment the heck out of their
work, over time, things will improve.

The biggest problem I see is in the use of SECAs. Things happen with these
bad boys that have you have no idea of unless you happened to write the
thing.

Skip

-----Original Message-----
From: BJ Freeman [mailto:[hidden email]]
Sent: Friday, November 02, 2007 7:07 PM
To: [hidden email]
Subject: /framework/example

I am sometime, a slow dumb witted learner.
I have to have examples, and most importantly something that ties things
to gather step by step, from a code point on view.

I have been looking for a way to put this down for others that have a
hard time figuring things out.

here is an example.

in the /framework/example/webapp/example/WEB-INF/web.xml

I would like to see





<context-param>
<param-name>localDispatcherName</param-name><param-value>example</param-valu
e>
<description>A unique name used to identify/recognize the local
dispatcher for the Service Engine</description>
</context-param>


<param-name>entityDelegatorName</param-name><param-value>default</param-valu
e>
<description>The Name of the Entity Delegator to use, defined in
entityengine.xml</description>
</context-param>

I am willing to add what I have learned this way into the example.
Hopefully others will do the same

BJ Freeman

Re: /framework/example

there was some discussion when I brought this up a few years ago.
My impression it was not received well. As can be seen by the code
changes and not many comments.

I believe I saw a jira that someone is adding it to the Webtools so you
look up a service and the associated SECAS's

should not be hard if you follow the code that loads the SECAS and
figures out which one to use.

skip@theDevers sent the following on 11/2/2007 5:34 PM:

> BJ
>
> You are not alone here. Ofbiz is a great huge beast that unless you have
> lived with it for years, you cannot possibly comprehend it all. Sadly,
> comments, and examples are fairly minimal. Fortunately, documentation is
> slowly improving. Now if everyone would just comment the heck out of their
> work, over time, things will improve.
>
> The biggest problem I see is in the use of SECAs. Things happen with these
> bad boys that have you have no idea of unless you happened to write the
> thing.
>
> Skip
>
> -----Original Message-----
> From: BJ Freeman [mailto:[hidden email]]
> Sent: Friday, November 02, 2007 7:07 PM
> To: [hidden email]
> Subject: /framework/example
>
>
> I am sometime, a slow dumb witted learner.
> I have to have examples, and most importantly something that ties things
> to gather step by step, from a code point on view.
>
> I have been looking for a way to put this down for others that have a
> hard time figuring things out.
>
> here is an example.
>
> in the /framework/example/webapp/example/WEB-INF/web.xml
>
> I would like to see
>
> 
>
> 
>
> <context-param>
> <param-name>localDispatcherName</param-name><param-value>example</param-valu
> e>
> <description>A unique name used to identify/recognize the local
> dispatcher for the Service Engine</description>
> </context-param>
>
> 
> <param-name>entityDelegatorName</param-name><param-value>default</param-valu
> e>
> <description>The Name of the Entity Delegator to use, defined in
> entityengine.xml</description>
> </context-param>
>
> I am willing to add what I have learned this way into the example.
> Hopefully others will do the same
>
>
>
>

SkipDever

RE: /framework/example

Hmmm, well BJ, this can be a real plumbing nightmare. I have wasted the
entire day trying to track down why processCreditReturn was being run twice
for the same transaction (Opentaps code). I knew fairly soon that
updateReturnHeader service was the culprit, but it took a long time to track
down the sequence of SECA events that caused it because one SECA was
triggering another and so on. A nightmare to troubleshoot if you don't live
and breath this code. There were three hundred lines of log entries
involved for this single transaction and I had to go check what the service
code did causing another SECA to be triggered and then on the the next and
so on.

But, at least I wasn't bored.

Skip

-----Original Message-----
From: BJ Freeman [mailto:[hidden email]]
Sent: Friday, November 02, 2007 9:10 PM
To: [hidden email]
Subject: Re: /framework/example

there was some discussion when I brought this up a few years ago.
My impression it was not received well. As can be seen by the code
changes and not many comments.

I believe I saw a jira that someone is adding it to the Webtools so you
look up a service and the associated SECAS's

should not be hard if you follow the code that loads the SECAS and
figures out which one to use.

skip@theDevers sent the following on 11/2/2007 5:34 PM:
> BJ
>
> You are not alone here. Ofbiz is a great huge beast that unless you have
> lived with it for years, you cannot possibly comprehend it all. Sadly,
> comments, and examples are fairly minimal. Fortunately, documentation is
> slowly improving. Now if everyone would just comment the heck out of
their
> work, over time, things will improve.
>
> The biggest problem I see is in the use of SECAs. Things happen with
these

> bad boys that have you have no idea of unless you happened to write the
> thing.
>
> Skip
>
> -----Original Message-----
> From: BJ Freeman [mailto:[hidden email]]
> Sent: Friday, November 02, 2007 7:07 PM
> To: [hidden email]
> Subject: /framework/example
>
>
> I am sometime, a slow dumb witted learner.
> I have to have examples, and most importantly something that ties things
> to gather step by step, from a code point on view.
>
> I have been looking for a way to put this down for others that have a
> hard time figuring things out.
>
> here is an example.
>
> in the /framework/example/webapp/example/WEB-INF/web.xml
>
> I would like to see
>
> 
>
> 
>
> <context-param>
>

<param-name>localDispatcherName</param-name><param-value>example</param-valu
> e>
> <description>A unique name used to identify/recognize the local
> dispatcher for the Service Engine</description>
> </context-param>
>
> 
>
<param-name>entityDelegatorName</param-name><param-value>default</param-valu

> e>
> <description>The Name of the Entity Delegator to use, defined in
> entityengine.xml</description>
> </context-param>
>
> I am willing to add what I have learned this way into the example.
> Hopefully others will do the same
>
>
>
>

David E Jones

Re: /framework/example

Yeah, it's a lot easier when it's not your first time... it DOES get
more boring though. ;)

Seriously though, getting the technical part of OFBiz is easy, one
with knowledge of the underlying technologies (like webapps,
databases, etc) can usually be productive in a few weeks. On the
business side of things (ie the applications and specialpurpose
directories) things are a LOT more complicated. I usually tell people
to give themselves 1-4 years, depending on how they dive into it and
how much experience they have with business processes and practices
(and I very much do NOT mean the practices of a particular company,
but general practices, which are often very different... people make
very funny decisions sometimes thinking it is the "only" way).

-David

On Nov 2, 2007, at 9:33 PM, skip@theDevers wrote:

> Hmmm, well BJ, this can be a real plumbing nightmare. I have wasted
> the
> entire day trying to track down why processCreditReturn was being
> run twice
> for the same transaction (Opentaps code). I knew fairly soon that
> updateReturnHeader service was the culprit, but it took a long time
> to track
> down the sequence of SECA events that caused it because one SECA was
> triggering another and so on. A nightmare to troubleshoot if you
> don't live
> and breath this code. There were three hundred lines of log entries
> involved for this single transaction and I had to go check what the
> service
> code did causing another SECA to be triggered and then on the the
> next and
> so on.
>
> But, at least I wasn't bored.
>
> Skip
>
> -----Original Message-----
> From: BJ Freeman [mailto:[hidden email]]
> Sent: Friday, November 02, 2007 9:10 PM
> To: [hidden email]
> Subject: Re: /framework/example
>
>
> there was some discussion when I brought this up a few years ago.
> My impression it was not received well. As can be seen by the code
> changes and not many comments.
>
> I believe I saw a jira that someone is adding it to the Webtools so
> you
> look up a service and the associated SECAS's
>
> should not be hard if you follow the code that loads the SECAS and
> figures out which one to use.
>
> skip@theDevers sent the following on 11/2/2007 5:34 PM:
>> BJ
>>
>> You are not alone here. Ofbiz is a great huge beast that unless
>> you have
>> lived with it for years, you cannot possibly comprehend it all.
>> Sadly,
>> comments, and examples are fairly minimal. Fortunately,
>> documentation is
>> slowly improving. Now if everyone would just comment the heck out of
> their
>> work, over time, things will improve.
>>
>> The biggest problem I see is in the use of SECAs. Things happen with
> these
>> bad boys that have you have no idea of unless you happened to write
>> the
>> thing.
>>
>> Skip
>>
>> -----Original Message-----
>> From: BJ Freeman [mailto:[hidden email]]
>> Sent: Friday, November 02, 2007 7:07 PM
>> To: [hidden email]
>> Subject: /framework/example
>>
>>
>> I am sometime, a slow dumb witted learner.
>> I have to have examples, and most importantly something that ties
>> things
>> to gather step by step, from a code point on view.
>>
>> I have been looking for a way to put this down for others that have a
>> hard time figuring things out.
>>
>> here is an example.
>>
>> in the /framework/example/webapp/example/WEB-INF/web.xml
>>
>> I would like to see
>>
>> 
>>
>> 
>>
>> <context-param>
>>
> <param-name>localDispatcherName</param-name><param-value>example</
> param-valu
>> e>
>> <description>A unique name used to identify/recognize the
>> local
>> dispatcher for the Service Engine</description>
>> </context-param>
>>
>> 
>>
> <param-name>entityDelegatorName</param-name><param-value>default</
> param-valu
>> e>
>> <description>The Name of the Entity Delegator to use,
>> defined in
>> entityengine.xml</description>
>> </context-param>
>>
>> I am willing to add what I have learned this way into the example.
>> Hopefully others will do the same
>>
>>
>>
>>
>

smime.p7s (3K) Download Attachment

SkipDever

RE: /framework/example

Hmmm. Well David, the sad thing is that this wasn't my first time through
most of this code.

It would have been REAL nice if the SECA had written in the log a trace of
how it got triggered. But sadly, that would be a lot of work for very
little reward.

SECAs in concept are neat and nifty, but can have nightmarish consequences
in unintended areas a month after it was applied.

Skip

-----Original Message-----
From: David E Jones [mailto:[hidden email]]
Sent: Friday, November 02, 2007 8:43 PM
To: [hidden email]
Subject: Re: /framework/example

Yeah, it's a lot easier when it's not your first time... it DOES get
more boring though. ;)

Seriously though, getting the technical part of OFBiz is easy, one
with knowledge of the underlying technologies (like webapps,
databases, etc) can usually be productive in a few weeks. On the
business side of things (ie the applications and specialpurpose
directories) things are a LOT more complicated. I usually tell people
to give themselves 1-4 years, depending on how they dive into it and
how much experience they have with business processes and practices
(and I very much do NOT mean the practices of a particular company,
but general practices, which are often very different... people make
very funny decisions sometimes thinking it is the "only" way).

-David

On Nov 2, 2007, at 9:33 PM, skip@theDevers wrote:

http://docs.ofbiz.org/display/OFBTECH/Apache+OFBiz+Technical+Production+Setu

>> p+Guide
>> Database Setup-->
>>
> <param-name>entityDelegatorName</param-name><param-value>default</
> param-valu
>> e>
>> <description>The Name of the Entity Delegator to use,
>> defined in
>> entityengine.xml</description>
>> </context-param>
>>
>> I am willing to add what I have learned this way into the example.
>> Hopefully others will do the same
>>
>>
>>
>>
>

BJ Freeman

Re: /framework/example

in /framework/entity/src/org/ofbiz/service/eca/ServiceEcaUtil.java

public static Map getServiceEventMap(String serviceName) {
if (ServiceEcaUtil.ecaCache == null) ServiceEcaUtil.readConfig();
return (Map) ServiceEcaUtil.ecaCache.get(serviceName);
}

public static Collection getServiceEventRules(String serviceName,
String event)

and
public static void evalRules(String serviceName, Map eventMap,
String event, DispatchContext dctx, Map context, Map result, boolean
isError, boolean isFailure) throws GenericServiceException {

Since I need to understand these also will try to add this to webtools.

skip@theDevers sent the following on 11/2/2007 8:23 PM:

> Hmmm. Well David, the sad thing is that this wasn't my first time through
> most of this code.
>
> It would have been REAL nice if the SECA had written in the log a trace of
> how it got triggered. But sadly, that would be a lot of work for very
> little reward.
>
> SECAs in concept are neat and nifty, but can have nightmarish consequences
> in unintended areas a month after it was applied.
>
> Skip
>
> -----Original Message-----
> From: David E Jones [mailto:[hidden email]]
> Sent: Friday, November 02, 2007 8:43 PM
> To: [hidden email]
> Subject: Re: /framework/example
>
>
>
> Yeah, it's a lot easier when it's not your first time... it DOES get
> more boring though. ;)
>
> Seriously though, getting the technical part of OFBiz is easy, one
> with knowledge of the underlying technologies (like webapps,
> databases, etc) can usually be productive in a few weeks. On the
> business side of things (ie the applications and specialpurpose
> directories) things are a LOT more complicated. I usually tell people
> to give themselves 1-4 years, depending on how they dive into it and
> how much experience they have with business processes and practices
> (and I very much do NOT mean the practices of a particular company,
> but general practices, which are often very different... people make
> very funny decisions sometimes thinking it is the "only" way).
>
> -David
>
>
> On Nov 2, 2007, at 9:33 PM, skip@theDevers wrote:
>
>> Hmmm, well BJ, this can be a real plumbing nightmare. I have wasted
>> the
>> entire day trying to track down why processCreditReturn was being
>> run twice
>> for the same transaction (Opentaps code). I knew fairly soon that
>> updateReturnHeader service was the culprit, but it took a long time
>> to track
>> down the sequence of SECA events that caused it because one SECA was
>> triggering another and so on. A nightmare to troubleshoot if you
>> don't live
>> and breath this code. There were three hundred lines of log entries
>> involved for this single transaction and I had to go check what the
>> service
>> code did causing another SECA to be triggered and then on the the
>> next and
>> so on.
>>
>> But, at least I wasn't bored.
>>
>> Skip
>>
>> -----Original Message-----
>> From: BJ Freeman [mailto:[hidden email]]
>> Sent: Friday, November 02, 2007 9:10 PM
>> To: [hidden email]
>> Subject: Re: /framework/example
>>
>>
>> there was some discussion when I brought this up a few years ago.
>> My impression it was not received well. As can be seen by the code
>> changes and not many comments.
>>
>> I believe I saw a jira that someone is adding it to the Webtools so
>> you
>> look up a service and the associated SECAS's
>>
>> should not be hard if you follow the code that loads the SECAS and
>> figures out which one to use.
>>
>> skip@theDevers sent the following on 11/2/2007 5:34 PM:
>>> BJ
>>>
>>> You are not alone here. Ofbiz is a great huge beast that unless
>>> you have
>>> lived with it for years, you cannot possibly comprehend it all.
>>> Sadly,
>>> comments, and examples are fairly minimal. Fortunately,
>>> documentation is
>>> slowly improving. Now if everyone would just comment the heck out of
>> their
>>> work, over time, things will improve.
>>>
>>> The biggest problem I see is in the use of SECAs. Things happen with
>> these
>>> bad boys that have you have no idea of unless you happened to write
>>> the
>>> thing.
>>>
>>> Skip
>>>
>>> -----Original Message-----
>>> From: BJ Freeman [mailto:[hidden email]]
>>> Sent: Friday, November 02, 2007 7:07 PM
>>> To: [hidden email]
>>> Subject: /framework/example
>>>
>>>
>>> I am sometime, a slow dumb witted learner.
>>> I have to have examples, and most importantly something that ties
>>> things
>>> to gather step by step, from a code point on view.
>>>
>>> I have been looking for a way to put this down for others that have a
>>> hard time figuring things out.
>>>
>>> here is an example.
>>>
>>> in the /framework/example/webapp/example/WEB-INF/web.xml
>>>
>>> I would like to see
>>>
>>> 
>>>
>>> 
>>>
>>> <context-param>
>>>
>> <param-name>localDispatcherName</param-name><param-value>example</
>> param-valu
>>> e>
>>> <description>A unique name used to identify/recognize the
>>> local
>>> dispatcher for the Service Engine</description>
>>> </context-param>
>>>
>>> 
>>>
>> <param-name>entityDelegatorName</param-name><param-value>default</
>> param-valu
>>> e>
>>> <description>The Name of the Entity Delegator to use,
>>> defined in
>>> entityengine.xml</description>
>>> </context-param>
>>>
>>> I am willing to add what I have learned this way into the example.
>>> Hopefully others will do the same
>>>
>>>
>>>
>>>
>
>
>
>
>

BJ Freeman

Re: /framework/example

oops
/framework/service/src/org/ofbiz/service/eca/ServiceEcaUtil.java

BJ Freeman sent the following on 11/2/2007 10:25 PM:

> in /framework/entity/src/org/ofbiz/service/eca/ServiceEcaUtil.java
>
> public static Map getServiceEventMap(String serviceName) {
> if (ServiceEcaUtil.ecaCache == null) ServiceEcaUtil.readConfig();
> return (Map) ServiceEcaUtil.ecaCache.get(serviceName);
> }
>
> public static Collection getServiceEventRules(String serviceName,
> String event)
>
> and
> public static void evalRules(String serviceName, Map eventMap,
> String event, DispatchContext dctx, Map context, Map result, boolean
> isError, boolean isFailure) throws GenericServiceException {
>
> Since I need to understand these also will try to add this to webtools.
>
>
>
> skip@theDevers sent the following on 11/2/2007 8:23 PM:
>> Hmmm. Well David, the sad thing is that this wasn't my first time through
>> most of this code.
>>
>> It would have been REAL nice if the SECA had written in the log a trace of
>> how it got triggered. But sadly, that would be a lot of work for very
>> little reward.
>>
>> SECAs in concept are neat and nifty, but can have nightmarish consequences
>> in unintended areas a month after it was applied.
>>
>> Skip
>>
>> -----Original Message-----
>> From: David E Jones [mailto:[hidden email]]
>> Sent: Friday, November 02, 2007 8:43 PM
>> To: [hidden email]
>> Subject: Re: /framework/example
>>
>>
>>
>> Yeah, it's a lot easier when it's not your first time... it DOES get
>> more boring though. ;)
>>
>> Seriously though, getting the technical part of OFBiz is easy, one
>> with knowledge of the underlying technologies (like webapps,
>> databases, etc) can usually be productive in a few weeks. On the
>> business side of things (ie the applications and specialpurpose
>> directories) things are a LOT more complicated. I usually tell people
>> to give themselves 1-4 years, depending on how they dive into it and
>> how much experience they have with business processes and practices
>> (and I very much do NOT mean the practices of a particular company,
>> but general practices, which are often very different... people make
>> very funny decisions sometimes thinking it is the "only" way).
>>
>> -David
>>
>>
>> On Nov 2, 2007, at 9:33 PM, skip@theDevers wrote:
>>
>>> Hmmm, well BJ, this can be a real plumbing nightmare. I have wasted
>>> the
>>> entire day trying to track down why processCreditReturn was being
>>> run twice
>>> for the same transaction (Opentaps code). I knew fairly soon that
>>> updateReturnHeader service was the culprit, but it took a long time
>>> to track
>>> down the sequence of SECA events that caused it because one SECA was
>>> triggering another and so on. A nightmare to troubleshoot if you
>>> don't live
>>> and breath this code. There were three hundred lines of log entries
>>> involved for this single transaction and I had to go check what the
>>> service
>>> code did causing another SECA to be triggered and then on the the
>>> next and
>>> so on.
>>>
>>> But, at least I wasn't bored.
>>>
>>> Skip
>>>
>>> -----Original Message-----
>>> From: BJ Freeman [mailto:[hidden email]]
>>> Sent: Friday, November 02, 2007 9:10 PM
>>> To: [hidden email]
>>> Subject: Re: /framework/example
>>>
>>>
>>> there was some discussion when I brought this up a few years ago.
>>> My impression it was not received well. As can be seen by the code
>>> changes and not many comments.
>>>
>>> I believe I saw a jira that someone is adding it to the Webtools so
>>> you
>>> look up a service and the associated SECAS's
>>>
>>> should not be hard if you follow the code that loads the SECAS and
>>> figures out which one to use.
>>>
>>> skip@theDevers sent the following on 11/2/2007 5:34 PM:
>>>> BJ
>>>>
>>>> You are not alone here. Ofbiz is a great huge beast that unless
>>>> you have
>>>> lived with it for years, you cannot possibly comprehend it all.
>>>> Sadly,
>>>> comments, and examples are fairly minimal. Fortunately,
>>>> documentation is
>>>> slowly improving. Now if everyone would just comment the heck out of
>>> their
>>>> work, over time, things will improve.
>>>>
>>>> The biggest problem I see is in the use of SECAs. Things happen with
>>> these
>>>> bad boys that have you have no idea of unless you happened to write
>>>> the
>>>> thing.
>>>>
>>>> Skip
>>>>
>>>> -----Original Message-----
>>>> From: BJ Freeman [mailto:[hidden email]]
>>>> Sent: Friday, November 02, 2007 7:07 PM
>>>> To: [hidden email]
>>>> Subject: /framework/example
>>>>
>>>>
>>>> I am sometime, a slow dumb witted learner.
>>>> I have to have examples, and most importantly something that ties
>>>> things
>>>> to gather step by step, from a code point on view.
>>>>
>>>> I have been looking for a way to put this down for others that have a
>>>> hard time figuring things out.
>>>>
>>>> here is an example.
>>>>
>>>> in the /framework/example/webapp/example/WEB-INF/web.xml
>>>>
>>>> I would like to see
>>>>
>>>> 
>>>>
>>>> 
>>>>
>>>> <context-param>
>>>>
>>> <param-name>localDispatcherName</param-name><param-value>example</
>>> param-valu
>>>> e>
>>>> <description>A unique name used to identify/recognize the
>>>> local
>>>> dispatcher for the Service Engine</description>
>>>> </context-param>
>>>>
>>>> 
>>>>
>>> <param-name>entityDelegatorName</param-name><param-value>default</
>>> param-valu
>>>> e>
>>>> <description>The Name of the Entity Delegator to use,
>>>> defined in
>>>> entityengine.xml</description>
>>>> </context-param>
>>>>
>>>> I am willing to add what I have learned this way into the example.
>>>> Hopefully others will do the same
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>>
>
>
>

BJ Freeman

Re: /framework/example

hmmmm looks like there are plans for the Eca stuff in webtools
found
<screen name="ServiceEcaDetail">
which point to
serviceecadetail.ftl
but there is no serviceecadetail.ftl

Is this being worked on?

if not I will take a stab at it.

BJ Freeman sent the following on 11/2/2007 10:40 PM:

> oops
> /framework/service/src/org/ofbiz/service/eca/ServiceEcaUtil.java
>
> BJ Freeman sent the following on 11/2/2007 10:25 PM:
>> in /framework/entity/src/org/ofbiz/service/eca/ServiceEcaUtil.java
>>
>> public static Map getServiceEventMap(String serviceName) {
>> if (ServiceEcaUtil.ecaCache == null) ServiceEcaUtil.readConfig();
>> return (Map) ServiceEcaUtil.ecaCache.get(serviceName);
>> }
>>
>> public static Collection getServiceEventRules(String serviceName,
>> String event)
>>
>> and
>> public static void evalRules(String serviceName, Map eventMap,
>> String event, DispatchContext dctx, Map context, Map result, boolean
>> isError, boolean isFailure) throws GenericServiceException {
>>
>> Since I need to understand these also will try to add this to webtools.
>>
>>
>>
>> skip@theDevers sent the following on 11/2/2007 8:23 PM:
>>> Hmmm. Well David, the sad thing is that this wasn't my first time through
>>> most of this code.
>>>
>>> It would have been REAL nice if the SECA had written in the log a trace of
>>> how it got triggered. But sadly, that would be a lot of work for very
>>> little reward.
>>>
>>> SECAs in concept are neat and nifty, but can have nightmarish consequences
>>> in unintended areas a month after it was applied.
>>>
>>> Skip
>>>
>>> -----Original Message-----
>>> From: David E Jones [mailto:[hidden email]]
>>> Sent: Friday, November 02, 2007 8:43 PM
>>> To: [hidden email]
>>> Subject: Re: /framework/example
>>>
>>>
>>>
>>> Yeah, it's a lot easier when it's not your first time... it DOES get
>>> more boring though. ;)
>>>
>>> Seriously though, getting the technical part of OFBiz is easy, one
>>> with knowledge of the underlying technologies (like webapps,
>>> databases, etc) can usually be productive in a few weeks. On the
>>> business side of things (ie the applications and specialpurpose
>>> directories) things are a LOT more complicated. I usually tell people
>>> to give themselves 1-4 years, depending on how they dive into it and
>>> how much experience they have with business processes and practices
>>> (and I very much do NOT mean the practices of a particular company,
>>> but general practices, which are often very different... people make
>>> very funny decisions sometimes thinking it is the "only" way).
>>>
>>> -David
>>>
>>>
>>> On Nov 2, 2007, at 9:33 PM, skip@theDevers wrote:
>>>
>>>> Hmmm, well BJ, this can be a real plumbing nightmare. I have wasted
>>>> the
>>>> entire day trying to track down why processCreditReturn was being
>>>> run twice
>>>> for the same transaction (Opentaps code). I knew fairly soon that
>>>> updateReturnHeader service was the culprit, but it took a long time
>>>> to track
>>>> down the sequence of SECA events that caused it because one SECA was
>>>> triggering another and so on. A nightmare to troubleshoot if you
>>>> don't live
>>>> and breath this code. There were three hundred lines of log entries
>>>> involved for this single transaction and I had to go check what the
>>>> service
>>>> code did causing another SECA to be triggered and then on the the
>>>> next and
>>>> so on.
>>>>
>>>> But, at least I wasn't bored.
>>>>
>>>> Skip
>>>>
>>>> -----Original Message-----
>>>> From: BJ Freeman [mailto:[hidden email]]
>>>> Sent: Friday, November 02, 2007 9:10 PM
>>>> To: [hidden email]
>>>> Subject: Re: /framework/example
>>>>
>>>>
>>>> there was some discussion when I brought this up a few years ago.
>>>> My impression it was not received well. As can be seen by the code
>>>> changes and not many comments.
>>>>
>>>> I believe I saw a jira that someone is adding it to the Webtools so
>>>> you
>>>> look up a service and the associated SECAS's
>>>>
>>>> should not be hard if you follow the code that loads the SECAS and
>>>> figures out which one to use.
>>>>
>>>> skip@theDevers sent the following on 11/2/2007 5:34 PM:
>>>>> BJ
>>>>>
>>>>> You are not alone here. Ofbiz is a great huge beast that unless
>>>>> you have
>>>>> lived with it for years, you cannot possibly comprehend it all.
>>>>> Sadly,
>>>>> comments, and examples are fairly minimal. Fortunately,
>>>>> documentation is
>>>>> slowly improving. Now if everyone would just comment the heck out of
>>>> their
>>>>> work, over time, things will improve.
>>>>>
>>>>> The biggest problem I see is in the use of SECAs. Things happen with
>>>> these
>>>>> bad boys that have you have no idea of unless you happened to write
>>>>> the
>>>>> thing.
>>>>>
>>>>> Skip
>>>>>
>>>>> -----Original Message-----
>>>>> From: BJ Freeman [mailto:[hidden email]]
>>>>> Sent: Friday, November 02, 2007 7:07 PM
>>>>> To: [hidden email]
>>>>> Subject: /framework/example
>>>>>
>>>>>
>>>>> I am sometime, a slow dumb witted learner.
>>>>> I have to have examples, and most importantly something that ties
>>>>> things
>>>>> to gather step by step, from a code point on view.
>>>>>
>>>>> I have been looking for a way to put this down for others that have a
>>>>> hard time figuring things out.
>>>>>
>>>>> here is an example.
>>>>>
>>>>> in the /framework/example/webapp/example/WEB-INF/web.xml
>>>>>
>>>>> I would like to see
>>>>>
>>>>> 
>>>>>
>>>>> 
>>>>>
>>>>> <context-param>
>>>>>
>>>> <param-name>localDispatcherName</param-name><param-value>example</
>>>> param-valu
>>>>> e>
>>>>> <description>A unique name used to identify/recognize the
>>>>> local
>>>>> dispatcher for the Service Engine</description>
>>>>> </context-param>
>>>>>
>>>>> 
>>>>>
>>>> <param-name>entityDelegatorName</param-name><param-value>default</
>>>> param-valu
>>>>> e>
>>>>> <description>The Name of the Entity Delegator to use,
>>>>> defined in
>>>>> entityengine.xml</description>
>>>>> </context-param>
>>>>>
>>>>> I am willing to add what I have learned this way into the example.
>>>>> Hopefully others will do the same
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>
>>
>
>
>

Jacques Le Roux

Re: /framework/example

Administrator

Hi BJ,

Not sure it's related, I just created a Jira issue https://issues.apache.org/jira/browse/OFBIZ-1384

Jacques

De : "BJ Freeman" <[hidden email]>

> hmmmm looks like there are plans for the Eca stuff in webtools
> found
> <screen name="ServiceEcaDetail">
> which point to
> serviceecadetail.ftl
> but there is no serviceecadetail.ftl
>
> Is this being worked on?
>
> if not I will take a stab at it.
>
>
> BJ Freeman sent the following on 11/2/2007 10:40 PM:
> > oops
> > /framework/service/src/org/ofbiz/service/eca/ServiceEcaUtil.java
> >
> > BJ Freeman sent the following on 11/2/2007 10:25 PM:
> >> in /framework/entity/src/org/ofbiz/service/eca/ServiceEcaUtil.java
> >>
> >> public static Map getServiceEventMap(String serviceName) {
> >> if (ServiceEcaUtil.ecaCache == null) ServiceEcaUtil.readConfig();
> >> return (Map) ServiceEcaUtil.ecaCache.get(serviceName);
> >> }
> >>
> >> public static Collection getServiceEventRules(String serviceName,
> >> String event)
> >>
> >> and
> >> public static void evalRules(String serviceName, Map eventMap,
> >> String event, DispatchContext dctx, Map context, Map result, boolean
> >> isError, boolean isFailure) throws GenericServiceException {
> >>
> >> Since I need to understand these also will try to add this to webtools.
> >>
> >>
> >>
> >> skip@theDevers sent the following on 11/2/2007 8:23 PM:
> >>> Hmmm. Well David, the sad thing is that this wasn't my first time through
> >>> most of this code.
> >>>
> >>> It would have been REAL nice if the SECA had written in the log a trace of
> >>> how it got triggered. But sadly, that would be a lot of work for very
> >>> little reward.
> >>>
> >>> SECAs in concept are neat and nifty, but can have nightmarish consequences
> >>> in unintended areas a month after it was applied.
> >>>
> >>> Skip
> >>>
> >>> -----Original Message-----
> >>> From: David E Jones [mailto:[hidden email]]
> >>> Sent: Friday, November 02, 2007 8:43 PM
> >>> To: [hidden email]
> >>> Subject: Re: /framework/example
> >>>
> >>>
> >>>
> >>> Yeah, it's a lot easier when it's not your first time... it DOES get
> >>> more boring though. ;)
> >>>
> >>> Seriously though, getting the technical part of OFBiz is easy, one
> >>> with knowledge of the underlying technologies (like webapps,
> >>> databases, etc) can usually be productive in a few weeks. On the
> >>> business side of things (ie the applications and specialpurpose
> >>> directories) things are a LOT more complicated. I usually tell people
> >>> to give themselves 1-4 years, depending on how they dive into it and
> >>> how much experience they have with business processes and practices
> >>> (and I very much do NOT mean the practices of a particular company,
> >>> but general practices, which are often very different... people make
> >>> very funny decisions sometimes thinking it is the "only" way).
> >>>
> >>> -David
> >>>
> >>>
> >>> On Nov 2, 2007, at 9:33 PM, skip@theDevers wrote:
> >>>
> >>>> Hmmm, well BJ, this can be a real plumbing nightmare. I have wasted
> >>>> the
> >>>> entire day trying to track down why processCreditReturn was being
> >>>> run twice
> >>>> for the same transaction (Opentaps code). I knew fairly soon that
> >>>> updateReturnHeader service was the culprit, but it took a long time
> >>>> to track
> >>>> down the sequence of SECA events that caused it because one SECA was
> >>>> triggering another and so on. A nightmare to troubleshoot if you
> >>>> don't live
> >>>> and breath this code. There were three hundred lines of log entries
> >>>> involved for this single transaction and I had to go check what the
> >>>> service
> >>>> code did causing another SECA to be triggered and then on the the
> >>>> next and
> >>>> so on.
> >>>>
> >>>> But, at least I wasn't bored.
> >>>>
> >>>> Skip
> >>>>
> >>>> -----Original Message-----
> >>>> From: BJ Freeman [mailto:[hidden email]]
> >>>> Sent: Friday, November 02, 2007 9:10 PM
> >>>> To: [hidden email]
> >>>> Subject: Re: /framework/example
> >>>>
> >>>>
> >>>> there was some discussion when I brought this up a few years ago.
> >>>> My impression it was not received well. As can be seen by the code
> >>>> changes and not many comments.
> >>>>
> >>>> I believe I saw a jira that someone is adding it to the Webtools so
> >>>> you
> >>>> look up a service and the associated SECAS's
> >>>>
> >>>> should not be hard if you follow the code that loads the SECAS and
> >>>> figures out which one to use.
> >>>>
> >>>> skip@theDevers sent the following on 11/2/2007 5:34 PM:
> >>>>> BJ
> >>>>>
> >>>>> You are not alone here. Ofbiz is a great huge beast that unless
> >>>>> you have
> >>>>> lived with it for years, you cannot possibly comprehend it all.
> >>>>> Sadly,
> >>>>> comments, and examples are fairly minimal. Fortunately,
> >>>>> documentation is
> >>>>> slowly improving. Now if everyone would just comment the heck out of
> >>>> their
> >>>>> work, over time, things will improve.
> >>>>>
> >>>>> The biggest problem I see is in the use of SECAs. Things happen with
> >>>> these
> >>>>> bad boys that have you have no idea of unless you happened to write
> >>>>> the
> >>>>> thing.
> >>>>>
> >>>>> Skip
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: BJ Freeman [mailto:[hidden email]]
> >>>>> Sent: Friday, November 02, 2007 7:07 PM
> >>>>> To: [hidden email]
> >>>>> Subject: /framework/example
> >>>>>
> >>>>>
> >>>>> I am sometime, a slow dumb witted learner.
> >>>>> I have to have examples, and most importantly something that ties
> >>>>> things
> >>>>> to gather step by step, from a code point on view.
> >>>>>
> >>>>> I have been looking for a way to put this down for others that have a
> >>>>> hard time figuring things out.
> >>>>>
> >>>>> here is an example.
> >>>>>
> >>>>> in the /framework/example/webapp/example/WEB-INF/web.xml
> >>>>>
> >>>>> I would like to see
> >>>>>
> >>>>> 
> >>>>>
> >>>>> 
> >>>>>
> >>>>> <context-param>
> >>>>>
> >>>> <param-name>localDispatcherName</param-name><param-value>example</
> >>>> param-valu
> >>>>> e>
> >>>>> <description>A unique name used to identify/recognize the
> >>>>> local
> >>>>> dispatcher for the Service Engine</description>
> >>>>> </context-param>
> >>>>>
> >>>>> 
> >>>>>
> >>>> <param-name>entityDelegatorName</param-name><param-value>default</
> >>>> param-valu
> >>>>> e>
> >>>>> <description>The Name of the Entity Delegator to use,
> >>>>> defined in
> >>>>> entityengine.xml</description>
> >>>>> </context-param>
> >>>>>
> >>>>> I am willing to add what I have learned this way into the example.
> >>>>> Hopefully others will do the same
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
>

jonwimp

Re: /framework/example

In reply to this post by SkipDever

Actually, I thought the logs were alright and quite adequate when it comes to SECAs. They do say
which service triggered which action (another service).

At the moment, I can't imagine how the SECA logs can be further improved.

Even if not relying on logs, one can use grep fu to say "find all services that trigger this
particular service". Hmm... I believe Adam Heath is also quite strong in the force here. :) For
those trying to pick up OFBiz (or any other open source stuff) real quick, grep fu is certainly
one good fu to pick up.

As for adding a ECA rule in some corner of an OFBiz implementation, and finding out months later
that it broke things (this is mentioned in another message on the thread)... the above grep fu can
help us make informed choices before we introduce those potentially destabilizing ECA rules.

Jonathon

skip@theDevers wrote: