[
https://issues.apache.org/jira/browse/OFBIZ-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-1366.
--
Resolution: Invalid
Assignee: Jacques Le Roux
RecurrenceRule.java has been rewritten/refa
[
https://issues.apache.org/jira/browse/OFBIZ-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-1263.
--
Resolution: Fixed
Fix Version/s: Release Branch 4.0
SVN trunk
[
https://issues.apache.org/jira/browse/OFBIZ-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552615
]
Jacques Le Roux commented on OFBIZ-1249:
I will try and add XSD and annotation
> To permit to to calculate o
Sorry I can't leave this alone.
but every reason I have been given I have shown it can not work the way
it was intended. to allow custom apps to give a a new main-decorator to
an already existing app.
So either some more work has to be done on it, like what scott has
proposed,
Adopt a simple solut
more specifically...
RequestHandler.java
after line 608
add:
req.setAttribute("_NEXT_PAGE", nextPage);
- Original Message
From: Chris Howe <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sent: Monday, December 17, 2007 6:44:43 PM
Subject: Re: mainDecoratorLocation was Include of controllers
duh guess I need a nap..
you right .
:)
Chris Howe sent the following on 12/17/2007 4:44 PM:
> It's already in the controller.
>
> page="component://content/widget/CommonScreens.xml#main"/>
> You need to update the servlet that when it reads where to go, that it puts
> that value of pag
It's already in the controller.
You need to update the servlet that when it reads where to go, that it puts
that value of page into the context. Then your decorator can pull it out.
- Original Message
From: BJ Freeman <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sent: Monday, Dece
ah gee just found a flaw
the @page value into the context
does that go into the products or application controller.
will that create a backward compatibility problem?
Chris Howe sent the following on 12/17/2007 4:28 PM:
> sorry, that should be page.startsWith("component://...")
> - Original
[
https://issues.apache.org/jira/browse/OFBIZ-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552587
]
bjfreeman edited comment on OFBIZ-1531 at 12/17/07 4:37 PM:
-
in then dev mailing list chr
for those that have read christopher robin
"All I want is a little marmalade for my bread"
thanks chris have put in
https://issues.apache.org/jira/browse/OFBIZ-1531
will comment further with what I get working in my global when done
Chris Howe sent the following on 12/17/2007 4:28 PM:
> sorry, th
[
https://issues.apache.org/jira/browse/OFBIZ-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
BJ Freeman resolved OFBIZ-1531.
---
Resolution: Fixed
in then dev mailing list chris came up with a feasable solution
this is from his em
sorry, that should be page.startsWith("component://...")
- Original Message
From: Chris Howe <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sent: Monday, December 17, 2007 6:16:14 PM
Subject: Re: mainDecoratorLocation was Include of controllers
You'll need to get put the @page value into t
that looks reasonable.have to looks up page.
Chris Howe sent the following on 12/17/2007 4:16 PM:
> You'll need to get put the @page value into the context and run a
> script in your main-decorator to determine the correct values
>
> if (page.like("component://partymgr")
> applicationMenuName =
yes.
Adrian Crum sent the following on 12/17/2007 4:15 PM:
> That's probably where the disconnect is coming in. The way the system is
> set up, you would have your own application menu, which would look
> something like:
>
> My Custom Application
> Main | My Page 1 | My Page 2 | Party Communicati
Chris Howe sent the following on 12/17/2007 4:09 PM:
> be sure to define the mainDecoratorLocation in the web.xml as
> component://myapp/widget/CommonScreens.xml
yes
>
>>From there the only app specific stuff is the whether it's including
>>leftbar/rightbar/etc. You will need to define those
You'll need to get put the @page value into the context and run a
script in your main-decorator to determine the correct values
if (page.like("component://partymgr")
applicationMenuName = "Party";
elseif(page.like("component://product")
applicationMenuName="Product";
etc
parameters.put("applicati
That's probably where the disconnect is coming in. The way the system is set up, you would have your
own application menu, which would look something like:
My Custom Application
Main | My Page 1 | My Page 2 | Party Communications | Product Lookup | Logout
The Party Communcations screen would co
BJ Freeman wrote:
Oh.. well I did.
and got all sorts of errors because I has not included what that
application expected for its decorator.
and I could not find a way to use the app specific information for each
app in my main-decorator.
which started me down the road to app-mainDecoratorLocati
be sure to define the mainDecoratorLocation in the web.xml as
component://myapp/widget/CommonScreens.xml
>From there the only app specific stuff is the whether it's including
>leftbar/rightbar/etc. You will need to define those basic ones as well.
- Original Message
From: BJ Freeman <
here is an exmple
now I can only setup that up for one menu
so how do I set that up for each menu for each app?
BJ Freeman sent the following on 12/17/2007 3:59 PM:
> Oh.. well I did.
> and got all sorts of errors because I has not included what that
> application expected for its decorator.
>
[
https://issues.apache.org/jira/browse/OFBIZ-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Crum updated OFBIZ-1249:
---
Attachment: set_calendar.patch
set_calendar.patch is a quick-and-dirty stab at the new simple method.
Oh.. well I did.
and got all sorts of errors because I has not included what that
application expected for its decorator.
and I could not find a way to use the app specific information for each
app in my main-decorator.
which started me down the road to app-mainDecoratorLocation
Chris Howe sent
Woops...pressed the send button by mistake.
Make your own decorator in /myapp/widget/CommonScreens.xml
create a main-decorator and a global decorator and use modify to your heart's
content
- Original Message
From: BJ Freeman <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sent: Monday, De
Make your own decorator
- Original Message
From: BJ Freeman <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sent: Monday, December 17, 2007 5:33:01 PM
Subject: Re: mainDecoratorLocation was Include of controllers
so what is the approach that works?
Chris Howe sent the following on 12/17
so what is the approach that works?
Chris Howe sent the following on 12/17/2007 3:26 PM:
> That's what I wasn't understanding. Your approach fails with that problem.
> The approach others have been using for the last two years does not. I
> thought you were asserting that both approaches fa
[
https://issues.apache.org/jira/browse/OFBIZ-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-1532:
---
Priority: Major (was: Blocker)
Thanks Adrian,
I will have a look tomorrow. I have also a pr
That's what I wasn't understanding. Your approach fails with that problem.
The approach others have been using for the last two years does not. I thought
you were asserting that both approaches fail.
- Original Message
From: BJ Freeman <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sen
been through this umteem times.
sigh
this is not the case for ftl files only widgets.
I access a screen widget in x-app from my custom app.
that screen has a decorator which eventually looks up
mainDecoratorLocation to get the main-decorator
so we are back to defining the mainDecoratorLocation.
I
I'm not sure I understand what you mean by access multiple apps from a custom
app. When you have a custom app, there is no notion that included screens,
called screens, included controllers, etc have a context of ownership. The
custom app is simply locating snippets of xml. Nothing more. You
[
https://issues.apache.org/jira/browse/OFBIZ-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552563
]
Adrian Crum commented on OFBIZ-1532:
Jacques,
If you look at the seed data for the ACCTG_ATX_CREATE permission,
[
https://issues.apache.org/jira/browse/OFBIZ-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-1532:
---
Attachment: GiftCertificateServices.java.patch
As I'm not a specialist of the accounting comp
Run GiftCertificateServices.createTransaction as system user
Key: OFBIZ-1532
URL: https://issues.apache.org/jira/browse/OFBIZ-1532
Project: OFBiz
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/OFBIZ-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552560
]
Ashish Vijaywargiya commented on OFBIZ-1504:
Alok and Pranay your patch is in rev # 605032
--
Ashish Vij
good point. #1
so I will not put this to sleep and do it for my releases until, as you
say it become a problem
However the use of mainDecoratorLocation beyond an app should be
discourage for access multiple apps from a custom app as well.
the conflict of data in each main-decorator has specific a
[
https://issues.apache.org/jira/browse/OFBIZ-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-1504.
--
Resolution: Fixed
Thanks Alok Agnihotri for the initial patch.
Pranay thanks to you too
David and Jacopo,
You both never fail to amaze me with the time and care taken to craft your
answers to OfBizian's questions - and even their inane rants (complaints? -
hehe). I can't thank you enough and wanted to wish you guys and the rest of
the list a very joyous Holiday Season and a Happy New
Note: I'm not saying that prefixing the variable is a bad solution I'm just
throwing out the downsides of it
1) The use case you present should not be encouraged. The opportunity for
conflicting requests/views between multiple controllers will drive you bat
crazy with unexpected results. The i
It seems a lot of work for simple solution
how about app-mainDecoratorLocation
then if someone want to use their own decorator it will still work.
they just define each app-mainDecoratorLocation in their web.xml
it either points to the original location or their customer decorator.
Chris Howe se
you say this works, let me walk you thru this
I agree with you statements as far as it went.
however you did not cover the
location="${parameters.mainDecoratorLocation}">
for main-decorator.
Now it is true if I put the
mainDecoratorLocation in my web.xml this will work.
the next test though is t
[
https://issues.apache.org/jira/browse/OFBIZ-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552549
]
Bilgin Ibryam commented on OFBIZ-1388:
--
Committed in 4.0 rev. 605015
> Bug in lookup windows URL
>
[
https://issues.apache.org/jira/browse/OFBIZ-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552548
]
Adrian Crum commented on OFBIZ-1249:
I said that there must be at least one adjuster, otherwise the set-calendar
[
https://issues.apache.org/jira/browse/OFBIZ-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-1504:
-
Attachment: jira-issue-1504.patch
Here i am submitting the updated patch for this issue.
--
Pran
I suggested that as well and Scott echoed it. It doesn't seem to be
satisfactory to BJ. So we work at it.
- Original Message
From: Adrian Crum <[EMAIL PROTECTED]>
To: dev@ofbiz.apache.org
Sent: Monday, December 17, 2007 3:57:53 PM
Subject: Re: mainDecoratorLocation was Include of contro
OK, I do it
Jacques
De : "Adrian Crum" <[EMAIL PROTECTED]>
> Take a look at services_ledger.xml, line 264. It would be preferable to
> convert it to permission
> service.
>
>
> Jacques Le Roux wrote:
>
> > Actually the file AcctgTransServices.xml is not containing services
> > implementions
If all BJ wants to do is display an existing screen with its existing main decorator, then he can
just use the screen's URL.
Chris Howe wrote:
Because he wants screens from the party component to be decorated with the
mainDecoratorLocation defined in party/webapp/partymgr/WEB-INF/web.xml and
did you use two different apps from your app?
yes it will work for one app.
Adrian Crum sent the following on 12/17/2007 1:49 PM:
> The best way to prove it is to code it according to my suggestion and
> test it against the original problem you stated in this thread. It
> works. How do I know tha
Ok so if we just change mainDecoratorLocation to
party-mainDecoratorLocation
everything will work
I can just include in my web.xml
one for each app I am using.
they will thier own main-decorators and everthing works as it should.
very simple fix.
BJ Freeman sent the following on 12/17/2007 1:44
Because he wants screens from the party component to be decorated with the
mainDecoratorLocation defined in party/webapp/partymgr/WEB-INF/web.xml and
screens from the product compnent decorated with the mainDecoratorLocation
defined in product/webapp/catalog/WEB-INF/web.xml
Adrian's solution do
The best way to prove it is to code it according to my suggestion and test it against the original
problem you stated in this thread. It works. How do I know that? Because I did it a month ago.
-Adrian
BJ Freeman wrote:
best way to prove this is to have a menu in a new app.
point it to two di
[
https://issues.apache.org/jira/browse/OFBIZ-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552542
]
Jacques Le Roux commented on OFBIZ-1249:
If I have weel understood, Adrian proposed in dev ML that the attrib
best way to prove this is to have a menu in a new app.
point it to two different screens one in each app.
try to get both screens to work with out error.
even using your code.
BJ Freeman sent the following on 12/17/2007 1:39 PM:
> you did not say to change
> location="${parameters.mainDecoratorLo
and just to make this a point
there can be only one
so if I had my own main-decorator it would not work for calling all
other apps.
BJ Freeman sent the following on 12/17/2007 1:38 PM:
> short answer is I can
> but that still would not solve the problem.
> take the party main-decorator
>
>
>
No, that's not what I said.
BJ Freeman wrote:
you did not say to change
so even your change will not work.
Adrian Crum sent the following on 12/17/2007 1:32 PM:
That line wouldn't exist if you made the change I suggested.
Make the code changes, THEN tell me what's wrong with it. Telling m
In that case, activeApp becomes your custom app, and appheaderTemplate points to your custom app
header template. The party manager javascript and stylesheet elements would have to be copied over
to your main-decorator.
BJ Freeman wrote:
short answer is I can
but that still would not solve t
Oops; sorry forgot the # when copying. Mmm... I wonder if it will not give the
same result a null string or a false string is the
same for an URL isn'it ?
Jacques
De : "BJ Freeman" <[EMAIL PROTECTED]>
> actually suggested, since he put in the code to look for a blank parm
>
> #payment.paypal.not
you did not say to change
so even your change will not work.
Adrian Crum sent the following on 12/17/2007 1:32 PM:
> That line wouldn't exist if you made the change I suggested.
>
> Make the code changes, THEN tell me what's wrong with it. Telling me
> what's already wrong with it is pointless
short answer is I can
but that still would not solve the problem.
take the party main-decorator
not these can not be the same ones if I am calling the product
main-decorator
Scott Gray sent t
Anyway it's one in trunk and release4.0, following your suggestion.
Jacques
De : "BJ Freeman" <[EMAIL PROTECTED]>
> don't see that message.
> I am aware I don't get all the message from the ML.
> considering the server my mail server is on, I am not sure why that is
> the case
>
> Jacques Le Rou
That line wouldn't exist if you made the change I suggested.
Make the code changes, THEN tell me what's wrong with it. Telling me what's already wrong with it is
pointless - I already know the existing code doesn't work.
BJ Freeman wrote:
I beg to differ with you.
where is
I beg to differ with you.
where is
defined
where is
in the CommonPartyDecorator defined.
Adrian Crum sent the following on 12/17/2007 1:03 PM:
> ListPartyCommEvents request maps to ListPartyCommEvents view, that maps
> to
> component://party/widget/partymgr/Commu
Why couldn't you supply your own custom mainDecorator? What do the base
mainDecorators provide that you can't in your custom app?
Scott
On 18/12/2007, BJ Freeman <[EMAIL PROTECTED]> wrote:
>
> Based on this, I can never see how even if I called from a custom app
> different screens in different
Based on this, I can never see how even if I called from a custom app
different screens in different apps how one main-decorator
so I am not sure how this feature would work at all.
Hence my original suggestion that is apps main-decorator be declared as
application-mainDecoratorLocation
this way I
[
https://issues.apache.org/jira/browse/OFBIZ-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya reassigned OFBIZ-1505:
--
Assignee: Ashish Vijaywargiya
> New screen to manage the default glAccountId fo
[
https://issues.apache.org/jira/browse/OFBIZ-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-1505.
--
Resolution: Fixed
Thanks Brajesh Patel for your valuable patch.
Your patch is in rev #
A complaint is a complaint, and doesn't usually get you very far in a
collaborative environment. Complaining in any form basically says that
someone else created a problem and that person should solve it... so
whoever that is: get on it already! You're either helping to create
the softwar
I was going to comment on this too. As Adrian has expressed a number
of times using millisecond calculations is not reliable and the
Calendar or similar objects should be used instead.
-David
On Dec 17, 2007, at 8:40 AM, Adrian Crum wrote:
Hans,
Did you read my last email on this subje
[
https://issues.apache.org/jira/browse/OFBIZ-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-1505:
-
Attachment: Jira_issue_1505.patch
Here I am submitting the updated patch for this issue.
--
Pran
ListPartyCommEvents request maps to ListPartyCommEvents view, that maps to
component://party/widget/partymgr/CommunicationScreens.xml#ListPartyCommEvents.
The ListPartyCommEvents screen in CommunicationScreens.xml doesn't contain anything specific to the
Party Manager's web.xml file. I don't se
[
https://issues.apache.org/jira/browse/OFBIZ-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-1504:
-
Comment: was deleted
> New screen to manage the default glAccountId for the InvoiceItemType entit
[
https://issues.apache.org/jira/browse/OFBIZ-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-1504:
-
Attachment: (was: Update_JIRA_1505.patch)
> New screen to manage the default glAccountId for
[
https://issues.apache.org/jira/browse/OFBIZ-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranay Pandey updated OFBIZ-1504:
-
Attachment: Update_JIRA_1505.patch
Here i am submitting the updated patch for this issue.
--
Pra
Take a look at services_ledger.xml, line 264. It would be preferable to convert it to permission
service.
Jacques Le Roux wrote:
Actually the file AcctgTransServices.xml is not containing services
implementions but simple-methods. So I will simply replace
ACCOUNTING by ACCTG where relevant (
I have a menu, no screens, that calls ListPartyCommEvents
this goes to the party controller to resolve.
the party controller uses it view for ListPartyCommEvents
It can not read the party web.xml so will error even with your changes.
so lets say i put in a mainDecoratorLocation in my web xml and d
Actually the file AcctgTransServices.xml is not containing services
implementions but simple-methods. So I will simply replace
ACCOUNTING by ACCTG where relevant (a sole occurence, the one I pointed)
Jacques
De : "Jacques Le Roux" <[EMAIL PROTECTED]>
> OK I do it
>
> Jacques
>
> De : "Adrian Cru
[
https://issues.apache.org/jira/browse/OFBIZ-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-1109.
--
Resolution: Fixed
Fix Version/s: SVN trunk
> Ability to add items with modifiers
> -
[
https://issues.apache.org/jira/browse/OFBIZ-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552526
]
Jacques Le Roux commented on OFBIZ-1109:
Thanks Chris,
Your patch is in trunk revision: 604993. Some advices
1. Move the CommonCommunicationEventDecorator screen to the
communicationsscreens.xml file.
2. Change all
location="${parameters.mainDecoratorLocation}">
to
location="${parameters.communicationEventDecoratorLocation}">
Since parameters.communicationEventDecoratorLocation isn't defined anywhe
actually suggested, since he put in the code to look for a blank parm
#payment.paypal.notify=http://[yourServerName]/ecommerce/control/payPalNotify
payment.paypal.notify=
Note the # Which is the equivalent of a remark
[EMAIL PROTECTED] sent the following on 12/17/2007 12:31 PM:
> Author: jleroux
I will still get the error since the parameters.mainDecoratorLocation
for that is in the web.xml for party.
BJ Freeman sent the following on 12/17/2007 12:23 PM:
> Ok here is a real situation:
> take the party/widgets/partymgr/commicationsscreens.xml
> location="${parameters.mainDecoratorLocatio
don't see that message.
I am aware I don't get all the message from the ML.
considering the server my mail server is on, I am not sure why that is
the case
Jacques Le Roux sent the following on 12/17/2007 12:16 PM:
> Yes, I already agreed, see my msg from 17/12/2007 at 01:30 in this thread :o)
>
Ok here is a real situation:
take the party/widgets/partymgr/commicationsscreens.xml
which is the CommonSreens.xml
which has
the main-decorator has
how would the be with your example
Adrian Crum sent the following on 12/17/2007 9:33 AM:
> BJ,
>
> Go ahead and create one. I
[
https://issues.apache.org/jira/browse/OFBIZ-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552518
]
Adrian Crum commented on OFBIZ-1249:
I'm thinking we could add one more attribute to this: align-start="day | wee
Yes, I already agreed, see my msg from 17/12/2007 at 01:30 in this thread :o)
Doing it right now, and I will backport to release4.0
Jacques
De : "BJ Freeman" <[EMAIL PROTECTED]>
> The generalization is if we adopted the blank parm to check for, any
> parm example will be lost.
> so when this is
OK I do it
Jacques
De : "Adrian Crum" <[EMAIL PROTECTED]>
> Oops, I just found it. That one slipped in there somehow. That method should
> use the permission service.
>
>
> Adrian Crum wrote:
>
> > I don't see any permission checking logic in AcctgTransServices.xml. I
> > refactored it to us
Oops, I just found it. That one slipped in there somehow. That method should
use the permission service.
Adrian Crum wrote:
I don't see any permission checking logic in AcctgTransServices.xml. I
refactored it to use the permission service.
Jacques Le Roux wrote:
Seems that we are on the s
[
https://issues.apache.org/jira/browse/OFBIZ-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
BJ Freeman updated OFBIZ-1531:
--
Fix Version/s: Release Branch 4.0
Issue Type: Bug (was: Improvement)
Affects Version
I don't see any permission checking logic in AcctgTransServices.xml. I refactored it to use the
permission service.
Jacques Le Roux wrote:
Seems that we are on the same page, I will change also AcctgTransServices.xml
accordingly. As I can't see any problems with this I
will do it right now.
The generalization is if we adopted the blank parm to check for, any
parm example will be lost.
so when this is done, the parm that was there should be commented then a
new parm that is blank be used.
Jacques Le Roux sent the following on 12/17/2007 10:52 AM:
> BJ,
>
> Don't worry about a Jira i
Please use user ML for such question : it's explained here
http://docs.ofbiz.org/display/OFBADMIN/Mailing+Lists#MailingLists-DeveloperList:dev@ofbiz.apache.org
Jacques
De : "qiyadeng" <[EMAIL PROTECTED]>
>
> I create a new component in the hot-deploy.
> first, i just add a index.jsp in the compon
Seems that we are on the same page, I will change also AcctgTransServices.xml
accordingly. As I can't see any problems with this I
will do it right now...
Jacques
De : "Adrian Crum" <[EMAIL PROTECTED]>
> The accounting component services use the ACCTG_ATX_CREATE permission.
> Properties files
Adrian,
Actually on my side the point was more about optionnal but one fields rule. I
wanted to underline this as "I don't think such a rule
is already used in minilang."
Jacques
- Message d'origine -
De : "Adrian Crum" <[EMAIL PROTECTED]>
À :
Envoyé : lundi 17 décembre 2007 17:13
Obj
The original intent of having the mainDecoratorLocation parameter was to be able to reuse OOTB
screens and have them decorated with your custom app's main decorator. If BJ wants to do something
different than that, then yes - he'll need to do some extra work in his custom app.
This thread start
only shied away from it because I don't understand it yet
so will try to make it work with you suggestion.
Adrian Crum sent the following on 12/17/2007 10:42 AM:
> Actually, it would be better if we stuck to the original example you
> gave - communication events in the Party Manager component. Hav
BJ,
Don't worry about a Jira issue (except if you see some kind of generalisation).
I will commit it directly soon...
Thanks
Jacques
De : "BJ Freeman" <[EMAIL PROTECTED]>
> I will create a general JIra for a config information
> I don't have commit privileges.
>
>
> [EMAIL PROTECTED] sent th
[
https://issues.apache.org/jira/browse/OFBIZ-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacopo Cappellato closed OFBIZ-1530.
Resolution: Fixed
> AR: implement a service to compute outstanding amounts of past due date
Ok I will try to get my head around you solution.
:)
Adrian Crum sent the following on 12/17/2007 10:42 AM:
> Actually, it would be better if we stuck to the original example you
> gave - communication events in the Party Manager component. Have you
> tried the solution I offerred?
>
> -Adrian
>
I agree with Chris' interpretation here, while you are right Adrian about
the sub decorators you're missing what BJ is trying to acheive. He wants to
include the controllers from the base apps but not have to define his own
mainDecoratorLocation for the screens from those apps.
Regards
Scott
On
Actually, it would be better if we stuck to the original example you gave - communication events in
the Party Manager component. Have you tried the solution I offerred?
-Adrian
Adrian Crum wrote:
Exactly. That's because the screen was designed poorly. If the products
screen was fixed as I sug
Exactly. That's because the screen was designed poorly. If the products screen was fixed as I
suggested, then it would work as you would expect.
BJ Freeman wrote:
The problem is any screen that used
location="${parameters.mainDecoratorLocation}
will can not be called from a remote controller th
If my suggestion is followed, then BJ can include all the controllers he wants and all of the
included screens will perform as expected - no additional work is needed.
-Adrian
Chris Howe wrote:
I would agree with the solution you offered of sending the views to custom
application screens tha
1 - 100 of 153 matches
Mail list logo
