[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604424#action_12604424
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Awdesh for your patch.
Its
Hi Jacopo,
From: Jacopo Cappellato [EMAIL PROTECTED]
I think that there are some issues in the current implementation of
customer returns.
Here is a list of the main ones:
1) the ReturnHeader.needsInventoryReceive field is misleading because
it actually means the opposite: if set to Y then
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awdesh Parihar updated OFBIZ-1839:
--
Attachment: Party.patch
Removed the Container option from all the screen definition of party
[
https://issues.apache.org/jira/browse/OFBIZ-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604448#action_12604448
]
Ashish Vijaywargiya commented on OFBIZ-1794:
Thanks Ratnesh and Ravindra for
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsha Chadhar updated OFBIZ-1839:
--
Attachment: HumanRes.patch
Replaced the code with the new screenlet - tag in the Screens with
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awdesh Parihar updated OFBIZ-1839:
--
Attachment: Content.patch
Removed the Container option from all the screen definition of
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604458#action_12604458
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Parimal Gain thanks for your
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604459#action_12604459
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Awdesh for your patch on
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604460#action_12604460
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Harsha Chadhar for your
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604461#action_12604461
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Awdesh Singh Parihar for
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsha Chadhar updated OFBIZ-1839:
--
Attachment: Manufacturing.patch
Updated Manufacturing Component with the Screenlet tag
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604487#action_12604487
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Harsha Chadhar for your
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
parimal gain updated OFBIZ-1839:
Attachment: Facility.patch
updated patch for Facility Component with screenlet.
Thanks to Ratnesh
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604498#action_12604498
]
awdesh edited comment on OFBIZ-1839 at 6/12/08 4:58 AM:
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604511#action_12604511
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Parimal for your patch on
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604510#action_12604510
]
Ashish Vijaywargiya commented on OFBIZ-1839:
Thanks Awdesh for your Workeffort
Hi,
I was testing few patches for test cases posted on Jira and thought to
modify if-empty field-name= to use if-empty field= instead.
But its giving following error ( This particular log is associated with when
test is run on example component )
Any thoughts, why this is happening ?
Vikas
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Awdesh Parihar updated OFBIZ-1839:
--
Attachment: ProjectMgr.patch
Removed the Container option from all the screen definition of
https://localhost:8443/accounting/control/editInvoiceApplications?invoiceId=demo1
Error from above link is coming because ListNotAppliedPayments.groovy has
been removed from
applications/accounting/webapp/accounting/WEB-INF/actions/invoice folder in
rev # r661623 and it is referencing in
Does anyone know how the WSDL is generated by Ofbiz. I know where it gets its
data from (serverdef/services.xml). However, I would like to know what
actually reads that and generated the associated WSDL document.
--
View this message in context:
[
https://issues.apache.org/jira/browse/OFBIZ-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
parimal gain updated OFBIZ-1839:
Attachment: Order.patch
Updated patch for Order Component with Screenlet.
Thanks to Harsha for
Hi all,
I'd like to see in the WorkEffort Calendar different types of
WorkEfforts - Tasks, Events, Available... Right now the calendar shows
only WorkEfforts with type Event. Is there any reason for this
restriction that I'm not aware of?
In the calendar screen there is possibility to filter by
Why are the page titles being removed if the purpose of the commit is to
convert container elements to screenlet elements?
It would be nice to keep the page title in the screen -
https://127.0.0.1:8443/accounting/control/EditFixedAssetIdents?fixedAssetId=DEMO_MACHINE
-Adrian
[EMAIL
Yes, this would be a great enhancement.
A couple of notes:
1. The intention of the Available type work effort is to model things
like when someone is working during the week or when a machine is
schedule to be running (available). These should be shown as a
background in the calendar, or
Hi Vikas
The two attributes field-name and field should be interchangeable, are you
sure that you don't have a problem even if you use field-name?
Regards
Scott
2008/6/13 Vikas Mayur [EMAIL PROTECTED]:
Hi,
I was testing few patches for test cases posted on Jira and thought to
modify
Hi Scott,
It is working fine with field-name though it gives few errors like
UtilXml.java:660:ERROR] XmlFileLoader: File
file:/Users/vikas/work/projects/ofbiz/framework/example/script/org/ofbiz/example/example/ExampleServices.xml
process error. Line: 123. Error message: cvc-complex-type.3.2.2:
Hi Vikas
I can't see any reason why it would not work, where is the code I can use to
replicate the issue?
Thanks
Scott
2008/6/13 Vikas Mayur [EMAIL PROTECTED]:
Hi Scott,
It is working fine with field-name though it gives few errors like
UtilXml.java:660:ERROR] XmlFileLoader: File
Hi Hans
Could you point me to the url where I can see the error, I'd like to
understand what the problem is a bit more.
Thanks
Scott
2008/6/13 [EMAIL PROTECTED]:
Author: hansbak
Date: Thu Jun 12 21:36:16 2008
New Revision: 667333
URL: http://svn.apache.org/viewvc?rev=667333view=rev
Log:
Hi Scott,
I have seen this problem coming while running a test case.
For now you can run the test case for example component to see the problem
and file of interest is ExampleServices.xml,
method-name=testCreateExampleService.
Thanks,
Vikas
On Fri, Jun 13, 2008 at 10:27 AM, Scott Gray [EMAIL
Hi David,
I have seen that work and was trying do similar modifications to test case
patches.
It worked nicely with field-name though with some errors as you said which
are fine, but
the test case fails using field.
Vikas
On Fri, Jun 13, 2008 at 10:07 AM, David E Jones [EMAIL PROTECTED]
wrote:
I think it's fine to go ahead and commit that change Jacques.
Scott
2008/6/9 Jacques Le Roux [EMAIL PROTECTED]:
Scott and all,
Yes good idea, this could be a solution to this issue. Could it be an
acceptable solution for everybody ?
I think so since it's really needed for the POS on
31 matches
Mail list logo