date:20120417

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Sascha Rodekamp (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255356#comment-13255356
 ] 

Sascha Rodekamp commented on OFBIZ-4812:


Hi Francis,

I would avoid to patch single jar files, that increases the maintenance effort.

As Felix said using Class.forName(String) is problematic in OSGi scenarios. So 
i will refrain from replacing the jar file and prefer to wait for an official 
solution.

But anyway thanks for working on this issue.

Any options?



 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Sascha Rodekamp (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sascha Rodekamp updated OFBIZ-4812:
---

Issue Type: Sub-task  (was: Improvement)
Parent: OFBIZ-4659

 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Jacopo Cappellato (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255388#comment-13255388
 ] 

Jacopo Cappellato commented on OFBIZ-4812:
--

Francis,

Sascha explained some of the motivations pretty well.
In addition to this I would like to add:
1) we should limit as much as possible to commit code for making it compliant 
with IDEs; for example I don't like the code that Jacques committed in rev. 
1308085 and not much the code committed in rev. 1326300
2) running OFBiz in Eclipse is not the best way to run it; you can do if you 
like and it works but if it is causing problems you should use ant or the shell;
3) we should always use officially released jars from other projects; using a 
patched version (that doesn't even convince the committers of the other 
project) is not ok, especially if the reason is to make of biz compatible with 
an IDE




 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Jacques Le Roux (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255411#comment-13255411
 ] 

Jacques Le Roux commented on OFBIZ-4812:


Jacopo,

* About r1308085: it's really harmless and I can't see any issues with that. 
* r1326300 is really something important for Eclipse users, notably those wich 
uses releases where the schemas (XSDs) on site are not in sync with their XML 
files. I still wait Francis's documentation about that on wiki BTW ;)

I guess Francis is more interested by debugging mode than running in Eclipse. 
Else I agree it does not make sense.

 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Jacopo Cappellato (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255412#comment-13255412
 ] 

Jacopo Cappellato commented on OFBIZ-4812:
--

As far as I know debug mode works fine if you run of biz in debug mode from 
ant/shell and then connect to it from your IDE.


 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Jacopo Cappellato (Issue Comment Edited) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255412#comment-13255412
 ] 

Jacopo Cappellato edited comment on OFBIZ-4812 at 4/17/12 8:32 AM:
---

As far as I know debug mode works fine if you run ofbiz in debug mode from 
ant/shell and then connect to it from your IDE.


  was (Author: jacopoc):
As far as I know debug mode works fine if you run of biz in debug mode from 
ant/shell and then connect to it from your IDE.

  
 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Sascha Rodekamp (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255422#comment-13255422
 ] 

Sascha Rodekamp commented on OFBIZ-4812:


Hm the debug mode also works when starting ofbiz within eclipse, no problems 
with that. But i use the ofbiz.jar in my classpath and define the sources under 
source.

 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Jacques Le Roux (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255425#comment-13255425
 ] 

Jacques Le Roux commented on OFBIZ-4812:


I must say I never crossed issues using the other method (direct debug run) as 
well... I could revert r1308085, Francis?

 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Jacques Le Roux (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255426#comment-13255426
 ] 

Jacques Le Roux commented on OFBIZ-4812:


I do the same than Sascah, actually this is clearly explained for a long time 
at  
https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse

Francis did you follow those advices before creating OFBIZ-4777?


 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Summary of upcoming release related events

2012-04-17 Thread Jacopo Cappellato

Based on our tentative release plan:

http://ofbiz.apache.org/download.html

the upcoming events should be:

1) April 2012 - creation of the new release branch for 12.04 (this is not a 
release)
2) May 2012 - first release of the 11.04 series: Apache OFBiz 11.04.01

Regards,

Jacopo

Cleaning some of the Jira versions

2012-04-17 Thread Jacopo Cappellato

I would like to perform the following maintenance 

1) archive the following versions (they will disappears from drop down when 
tasks are created):
Release 09.04
Release 09.04.01
Release 10.04
because they are all for superseded releases; if there are open issues assigned 
(affects) to them we could bulk move them to versions Release Branch 09.04 
and Release Branch 10.04 

2) create new versions (for upcoming releases):
Release 09.04.03
Release 10.04.03
however new bugs should always be reported (affect) against the Release 
Branch 09.04, Release Branch 10.04 and Release Branch 11.04 ; we could use 
the Release 09.04.03 and Release 10.04.03 when the task is fixed in the 
branch as the fixed in version.

I think that #1 is rather important; I am not sure about #2.

What do you think?

Kind regards,

Jacopo

PS: I have also created Release 11.04.01 with a tentative release date of May 
15: I am going to use this version to log a series of tasks that are required 
before the release; after the release I will archive this version as the 
versions in #2 above.

[jira] [Commented] (OFBIZ-3155) Enhancing the useability of SFA by including an overview of the agreements of the account into the Account Screen

2012-04-17 Thread Erwan de FERRIERES (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255451#comment-13255451
 ] 

Erwan de FERRIERES commented on OFBIZ-3155:
---

only use what's in the context

 Enhancing the useability of SFA by including an overview of the agreements of 
 the account into the Account Screen
 -

 Key: OFBIZ-3155
 URL: https://issues.apache.org/jira/browse/OFBIZ-3155
 Project: OFBiz
  Issue Type: Improvement
  Components: marketing
Reporter: Pierre Smits
 Fix For: SVN trunk

 Attachments: OFBIZ-3155 sfa-accounts-agreements.patch, 
 sfa-accounts-agreements.patch


 This improvement includes:
 Adding an overview of associated agreements with the account to the account 
 screen
 Adding the functionality to create agreements from the account screen, with 
 setting the default agreement parties (Company and the account)
 The modifications are realized on:
 \applications\accounting\widgets\agreementscreen.xml - setting default 
 agreement parties
 \applications\party\webapp\partymgr\static\partymgr.css - including of style 
 elements for overviews in the bottom position of account screen
 \applications\party\widget\partymgr\profilescreens.xml  - including a screen 
 for partyAgreements
 \applications\party\widget\partymgr\partyforms.xml - including a form to 
 render the overview of agreements for accounts
 \applications\marketing\widget\sfa\sfamenus.xml - including the menu to 
 create new agreements from the acount screen
 \applications\marketing\widget\sfa\commonscreen.xml - including functionality 
 to add the overview of agreements to the bottom of the account screen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Cleaning some of the Jira versions

2012-04-17 Thread Vikas Mayur

Jacopo,

Since 09.04.02 was the last release of the series 09.04, does the proposed new 
version 09.04.03 has any purpose?

Regards
Vikas

On Apr 17, 2012, at 3:55 PM, Jacopo Cappellato wrote:

 I would like to perform the following maintenance 
 
 1) archive the following versions (they will disappears from drop down when 
 tasks are created):
 Release 09.04
 Release 09.04.01
 Release 10.04
 because they are all for superseded releases; if there are open issues 
 assigned (affects) to them we could bulk move them to versions Release 
 Branch 09.04 and Release Branch 10.04 
 
 2) create new versions (for upcoming releases):
 Release 09.04.03
 Release 10.04.03
 however new bugs should always be reported (affect) against the Release 
 Branch 09.04, Release Branch 10.04 and Release Branch 11.04 ; we could 
 use the Release 09.04.03 and Release 10.04.03 when the task is fixed in 
 the branch as the fixed in version.
 
 I think that #1 is rather important; I am not sure about #2.
 
 What do you think?
 
 Kind regards,
 
 Jacopo
 
 PS: I have also created Release 11.04.01 with a tentative release date of 
 May 15: I am going to use this version to log a series of tasks that are 
 required before the release; after the release I will archive this version 
 as the versions in #2 above.

Re: Cleaning some of the Jira versions

2012-04-17 Thread Jacopo Cappellato

ah ah, you are right Vikas!
Please disregard the proposal about 09.04.03... I probably need another coffee

Jacopo

On Apr 17, 2012, at 12:40 PM, Vikas Mayur wrote:

 Jacopo,
 
 Since 09.04.02 was the last release of the series 09.04, does the proposed 
 new version 09.04.03 has any purpose?
 
 Regards
 Vikas
 
 On Apr 17, 2012, at 3:55 PM, Jacopo Cappellato wrote:
 
 I would like to perform the following maintenance 
 
 1) archive the following versions (they will disappears from drop down 
 when tasks are created):
 Release 09.04
 Release 09.04.01
 Release 10.04
 because they are all for superseded releases; if there are open issues 
 assigned (affects) to them we could bulk move them to versions Release 
 Branch 09.04 and Release Branch 10.04 
 
 2) create new versions (for upcoming releases):
 Release 09.04.03
 Release 10.04.03
 however new bugs should always be reported (affect) against the Release 
 Branch 09.04, Release Branch 10.04 and Release Branch 11.04 ; we could 
 use the Release 09.04.03 and Release 10.04.03 when the task is fixed in 
 the branch as the fixed in version.
 
 I think that #1 is rather important; I am not sure about #2.
 
 What do you think?
 
 Kind regards,
 
 Jacopo
 
 PS: I have also created Release 11.04.01 with a tentative release date of 
 May 15: I am going to use this version to log a series of tasks that are 
 required before the release; after the release I will archive this version 
 as the versions in #2 above.

[jira] [Created] (OFBIZ-4816) Add release name as title at the top of the README file

2012-04-17 Thread Jacopo Cappellato (Created) (JIRA)

Add release name as title at the top of the README file
---

 Key: OFBIZ-4816
 URL: https://issues.apache.org/jira/browse/OFBIZ-4816
 Project: OFBiz
  Issue Type: Task
Reporter: Jacopo Cappellato
 Fix For: Release 11.04.01




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (OFBIZ-4817) Verify license compatibility

2012-04-17 Thread Jacopo Cappellato (Created) (JIRA)

Verify license compatibility


 Key: OFBIZ-4817
 URL: https://issues.apache.org/jira/browse/OFBIZ-4817
 Project: OFBiz
  Issue Type: Task
Reporter: Jacopo Cappellato
 Fix For: Release 11.04.01


Verify license headers with the help of RAT; verify LICENSE and NOTICE files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (OFBIZ-4819) Remove JCR/Jackrabbit experimental component from the 11.04 release branch

2012-04-17 Thread Jacopo Cappellato (Created) (JIRA)

Remove JCR/Jackrabbit experimental component from the 11.04 release branch
--

 Key: OFBIZ-4819
 URL: https://issues.apache.org/jira/browse/OFBIZ-4819
 Project: OFBiz
  Issue Type: Task
Affects Versions: Release Branch 11.04
Reporter: Jacopo Cappellato
 Fix For: Release 11.04.01




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (OFBIZ-4818) Remove mergefromtrunk scripts from release package

2012-04-17 Thread Jacopo Cappellato (Created) (JIRA)

Remove mergefromtrunk scripts from release package
--

 Key: OFBIZ-4818
 URL: https://issues.apache.org/jira/browse/OFBIZ-4818
 Project: OFBiz
  Issue Type: Task
Reporter: Jacopo Cappellato
 Fix For: Release 11.04.01




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (OFBIZ-4820) Add a file with Release Notes

2012-04-17 Thread Jacopo Cappellato (Created) (JIRA)

Add a file with Release Notes
---

 Key: OFBIZ-4820
 URL: https://issues.apache.org/jira/browse/OFBIZ-4820
 Project: OFBiz
  Issue Type: Task
Reporter: Jacopo Cappellato
 Fix For: Release 11.04.01


It should be derived from https://cwiki.apache.org/OFBIZ/main-new-features.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-4412) Set initial ecommerce Locale/Currency based on mount point specified in specialpurpose/ecommerce/ofbiz-component.xm

2012-04-17 Thread Jacopo Cappellato (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato updated OFBIZ-4412:
-

Affects Version/s: (was: Release Branch 11.04)
   (was: Release Branch 10.04)
Fix Version/s: (was: Release Branch 11.04)
   (was: Release Branch 10.04)
   (was: SVN trunk)

 Set initial ecommerce Locale/Currency based on mount point specified in 
 specialpurpose/ecommerce/ofbiz-component.xm
 ---

 Key: OFBIZ-4412
 URL: https://issues.apache.org/jira/browse/OFBIZ-4412
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: Not specific
Reporter: mz4wheeler
Priority: Trivial
  Labels: patch
 Attachments: OFBIZ-4412.patch

   Original Estimate: 2h
  Remaining Estimate: 2h

 Using the specified patch, it is now possible to set a users initial Locale 
 (and even currency) based on the webapp mount point.  This works with a 
 single store, and does not require the use virtual hosts.  This is especially 
 useful when setting up sitemap.xml, which allows crawlers (like google) to 
 correctly locate and traverse products and services in multiple languages.
 Here is an example where ecomclone has been modified to Locale=fr with a 
 mount point of /fr.
 specialpurpose/ecommerce/ofbiz-component.xml:
 !--  init-param name=Currency value=EUR/ --
 webapp name=ecommerce
 title=eCommerce
 server=default-server
 location=webapp/ecommerce
 mount-point=/ecommerce
 app-bar-display=false
 /webapp
 webapp name=ecomclone
 title=eCommerce Clone
 server=default-server
 location=webapp/ecomclone
 mount-point=/fr--- SPECIFY MOUNT
 app-bar-display=false
 init-param name=Locale value=fr/  --- SPECIFY LOCALE
 /webapp
 The below sitemap.xml would allow products with the /fr path to be indexed 
 in french.
 ?xml version=1.0 encoding=UTF-8?
 urlset xmlns=http://www.sitemaps.org/schemas/sitemap/0.9;
 urllochttp://ofbizsite.com/ecommerce/products/10002/p_1001TANGRAMPUZ/loc/url
 urllochttp://ofbizsite.com/fr/products/10002/p_1001TANGRAMPUZ/loc/url
 /urlset
 The patch:
 The attached patch modifies setDefaultStoreSettings in ProductEvents.java, 
 which is called once during the initial session creation.  
 After a user enters the URL, they are still free to modify the language, as 
 long as the page supports it (like the default demo store).  The patch also 
 allows the Currency to be forced as well, and it does appear to work, but 
 should be more throughly tested.
 Although this patch bypasses the requirement for multiple stores, there may 
 be issues with other aspects of the store, like emails.  However, it is no 
 different than a user who enters your English-based ecommerce store, selects 
 french, and attempts a checkout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-4379) Get first from list tag in screen's and form's action tag.

2012-04-17 Thread Jacopo Cappellato (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato updated OFBIZ-4379:
-

Affects Version/s: (was: Release 10.04)
Fix Version/s: (was: Release Branch 10.04)
   (was: SVN trunk)

 Get first from list tag in screen's and form's action tag.
 --

 Key: OFBIZ-4379
 URL: https://issues.apache.org/jira/browse/OFBIZ-4379
 Project: OFBiz
  Issue Type: New Feature
  Components: framework
Affects Versions: SVN trunk
Reporter: Ankit Jain
Priority: Minor
 Attachments: OFBIZ-4379.patch


 In most of the cases we need to get first record from a list in screen and 
 form widgets then we have to do something like this: 
 for eg:
 set field=websiteContent value=${groovy: 
 org.ofbiz.entity.util.EntityUtil.getFirst(websiteContentList);}/
 Instead of using like this my idea is to add a tag like first-from-list/ in 
 Screen  Form widget's action tag, so one can easily get first record from a 
 list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-3766) MacroScreenRenderer still uses HtmlFormRenderer (dependencies on html renderers)

2012-04-17 Thread Jacopo Cappellato (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato updated OFBIZ-3766:
-

Affects Version/s: (was: Release Branch 10.04)
Fix Version/s: (was: Release Branch 10.04)

 MacroScreenRenderer still uses HtmlFormRenderer (dependencies on html 
 renderers)
 

 Key: OFBIZ-3766
 URL: https://issues.apache.org/jira/browse/OFBIZ-3766
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: SVN trunk
Reporter: Blas Rodriguez Somoza
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: SVN trunk

 Attachments: OFBIZ-3766_html_dependencies.diff


 There are a bug in MacroScreenRenderer.renderScreenletSubWidget. and several 
 pages of the demo uses HtmlFormRenderer instead of MacroFormRenderer.
 The dependencies in org.ofbiz.widget.non-html directories against 
 org.ofbiz.widget.html are the following
 1.- org\ofbiz\widget\menu\MenuWrapTransform.java -- import 
 org.ofbiz.widget.html.HtmlMenuWrapper;
 2.- org\ofbiz\widget\screen\MacroScreenRenderer.java --:import 
 org.ofbiz.widget.html.HtmlScreenRenderer.ScreenletMenuRenderer;
 3.- org\ofbiz\widget\screen\ModelScreenWidget.java --:import 
 org.ofbiz.widget.html.HtmlMenuRenderer;
 4.- org\ofbiz\widget\screen\ModelScreenWidget.java --:import 
 org.ofbiz.widget.html.HtmlFormRenderer;
 5.- org\ofbiz\widget\screen\MacroScreenRenderer.java  --:import 
 org.ofbiz.widget.html.HtmlFormRenderer;
 6.- org\ofbiz\widget\screen\ScreenFopViewHandler.java --:import 
 org.ofbiz.widget.html.HtmlScreenRenderer;
 I excluded:
 ScreenWidgetViewHandler.java which is in widget.screen but is a piece of the 
 html renderers 
 References to HtmlWidgetRenderer, which although it is in the html directory 
 doesn't depend on other html directory sources.
 Comments:
 1.- OK. 
 2.- The real dependency is with HtmlMenuRenderer.
 3,4.- To avoid default renderers, ModelScreenWidget should use only the 
 renderer stored in the context.
 5.- bug.
 6.- if macro renderer will be the default one then this must be changed. It 
 will be better if the default renderer can be taken from the context but 
 AFAIK it isn't a default renderer in the context. 
 After the patch the dependencies against html directory are:
 org\ofbiz\widget\menu\MenuWrapTransform.java -- import 
 org.ofbiz.widget.html.HtmlMenuWrapper;
 org\ofbiz\widget\screen\MacroScreenRenderer.java --:import 
 org.ofbiz.widget.html.HtmlMenuRenderer; 
 org\ofbiz\widget\screen\MacroScreenViewHandler.java  --:import 
 org.ofbiz.widget.html.HtmlMenuRenderer;
 which are the expected ones, only with HtmlMenu because it isn't a macro 
 replacement.
 Patch:
 MacroScreenRenderer.java 
 - renderScreenletSubWidget method must use MacroFormRenderer instead of 
 HtmlFormRenderer
 - Added ScreenletMenuRenderer copied from HtmlScreenRenderer. This make the 
 dependency on HtmlMenuRenderer explicit and avoid the dependency on 
 HtmlScreenRenderer
 MacroScreenViewHandler.java
 - To avoid using defaults in ModelScreenWidget each ViewHandler must store 
 its form, tree and menu renderers in the context.
 ModelScreenWidget.java
 - There are not default renderers, each ScreenViewHandler must put its form, 
 tree and menu renderers in the context.
 ScreenFopViewHandler.java
 - Use MacroScreenRenderer instead HtmlScreenRenderer.
 ScreenWidgetViewHandler.java (aka ScreenHtmlViewHandler)
 - To avoid using defaults in ModelScreenWidget each ViewHandler must store 
 its form, tree and menu renderers in the context.
 ScreenXmlViewHandler.java
 - Should not depend on ScreenWidgetViewHandler

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (OFBIZ-3836) partybenifits leaves out using parytyrelationships

2012-04-17 Thread Jacopo Cappellato (Resolved) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacopo Cappellato resolved OFBIZ-3836.
--

Resolution: Incomplete

partybenifits leaves out using parytyrelationships
--

Key: OFBIZ-3836
URL: https://issues.apache.org/jira/browse/OFBIZ-3836
Project: OFBiz
Issue Type: Sub-task
Components: humanres
Affects Versions: Release Branch 09.04, SVN trunk
Reporter: BJ Freeman
Priority: Minor
Fix For: SVN trunk

Original Estimate: 168h
Remaining Estimate: 168h

In data model book the partybenefits use partyrelationship of employment to
tie a party and organization to partybenefits. Page 302.
The entity ties the party directly to the partybenefits.
I wanted to call this a design bug but figured I spend more time defending
that position than an improvement.
The Agreement of type Employment is also tied to the Party the same way.
The relationship goes through types from prospective, interviewee, newhire,
to employment
The newhire is usually a 90-day period of probation before benefits are
initiated.
In a way similar to statuschange the relationship if changed. Would have
changes that could happen for each relationship, be defined in
partyrelationshipchange.
Per the book only a relationship of employment would allow benefits to be
accessed and agreements to be setup of this relationship.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-3836) partybenifits leaves out using parytyrelationships

2012-04-17 Thread Jacopo Cappellato (Updated) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacopo Cappellato updated OFBIZ-3836:
-

Affects Version/s: (was: Release Branch 10.04)
Fix Version/s: (was: Release Branch 10.04)

partybenifits leaves out using parytyrelationships
--

Original Estimate: 168h
Remaining Estimate: 168h

[jira] [Created] (OFBIZ-4821) Error in rednring Reset field.

2012-04-17 Thread Sumit Pandit (Created) (JIRA)

Error in rednring Reset field.
--

 Key: OFBIZ-4821
 URL: https://issues.apache.org/jira/browse/OFBIZ-4821
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk
Reporter: Sumit Pandit
Priority: Blocker


MacroFormRenderer.renderResetField contains a missing entry when appending 
title to renderResetField's StringWritter.

MacroFormRenderer.java line# 1202
sr.append( title=\);
Where it should be 
sr.append(\ title=\);


Because of above reset/ button is not displaying on the screen. At back end 
it is returning Freemarker parser exception.

BTW it is one line change, if required I will submit the patch shortly.

--
Thanks and Regards
Sumit Pandit

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-4310) Conversion for complex-alias needs to be implemented

2012-04-17 Thread Jacopo Cappellato (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato updated OFBIZ-4310:
-

Affects Version/s: (was: Release 10.04)
   (was: Release Branch 11.04)
   (was: Release 09.04)
   SVN trunk
Fix Version/s: (was: Release Branch 11.04)
   (was: Release Branch 10.04)

 Conversion for complex-alias needs to be implemented 
 -

 Key: OFBIZ-4310
 URL: https://issues.apache.org/jira/browse/OFBIZ-4310
 Project: OFBiz
  Issue Type: New Feature
  Components: framework
Affects Versions: Release 4.0, SVN trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: Release Branch 09.04


 There is a TODO in ModelViewEntity.populateReverseLinks()
 // TODO: conversion for complex-alias needs to be implemented for cache and 
 in-memory eval stuff to work correctly
 This throws WARNING at OFBiz startup:
 {code}
 2011-05-27 13:23:53,161 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: quantityOrdered of 
 view-entity OrderItemQuantityReportGroupByItem
 2011-05-27 13:23:53,162 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: quantityOpen of 
 view-entity OrderItemQuantityReportGroupByItem
 2011-05-27 13:23:53,162 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: quantityOrdered of 
 view-entity OrderItemQuantityReportGroupByProduct
 2011-05-27 13:23:53,162 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: quantityOpen of 
 view-entity OrderItemQuantityReportGroupByProduct
 2011-05-27 13:23:53,169 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: quantityOrdered of 
 view-entity OrderReportSalesGroupByProduct
 2011-05-27 13:23:53,176 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: quantityOrdered of 
 view-entity OrderItemAndShipGrpInvResAndItemSum
 2011-05-27 13:23:53,176 (main) [ModelViewEntity.java:538:WARN ] 
 Conversion for complex-alias needs to be implemented for cache and in-memory 
 eval stuff to work correctly, will not work for alias: totQuantityAvailable 
 of view-entity OrderItemAndShipGrpInvResAndItemSum
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4821) Error in rednring Reset field.

2012-04-17 Thread Erwan de FERRIERES (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1321#comment-1321
 ] 

Erwan de FERRIERES commented on OFBIZ-4821:
---

Hi Sumit,

patch is mandatory so the Apache license can be accepted. If not, your code 
cannot be included in OFBiz.

Cheers,

 Error in rednring Reset field.
 --

 Key: OFBIZ-4821
 URL: https://issues.apache.org/jira/browse/OFBIZ-4821
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk
Reporter: Sumit Pandit
Priority: Blocker

 MacroFormRenderer.renderResetField contains a missing entry when appending 
 title to renderResetField's StringWritter.
 MacroFormRenderer.java line# 1202
 sr.append( title=\);
 Where it should be 
 sr.append(\ title=\);
 Because of above reset/ button is not displaying on the screen. At back end 
 it is returning Freemarker parser exception.
 BTW it is one line change, if required I will submit the patch shortly.
 --
 Thanks and Regards
 Sumit Pandit

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4821) Error in rednring Reset field.

2012-04-17 Thread Jacopo Cappellato (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1326#comment-1326
 ] 

Jacopo Cappellato commented on OFBIZ-4821:
--

Erwan,

for small contribution like this a patch is not needed.

Jacopo

 Error in rednring Reset field.
 --

 Key: OFBIZ-4821
 URL: https://issues.apache.org/jira/browse/OFBIZ-4821
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk
Reporter: Sumit Pandit
Priority: Blocker

 MacroFormRenderer.renderResetField contains a missing entry when appending 
 title to renderResetField's StringWritter.
 MacroFormRenderer.java line# 1202
 sr.append( title=\);
 Where it should be 
 sr.append(\ title=\);
 Because of above reset/ button is not displaying on the screen. At back end 
 it is returning Freemarker parser exception.
 BTW it is one line change, if required I will submit the patch shortly.
 --
 Thanks and Regards
 Sumit Pandit

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Cleaning some of the Jira versions

2012-04-17 Thread Vikas Mayur

No problem Jacopo :) 
The proposal otherwise looks good. We would perhaps need Release Branch 
09.04, even though the code will not be committed to this release branch but 
still one can post bug (if any) and/or attach patch for the fixes etc.

Regards
Vikas

On Apr 17, 2012, at 5:55 PM, Jacopo Cappellato wrote:

 ah ah, you are right Vikas!
 Please disregard the proposal about 09.04.03... I probably need another coffee
 
 Jacopo
 
 On Apr 17, 2012, at 12:40 PM, Vikas Mayur wrote:
 
 Jacopo,
 
 Since 09.04.02 was the last release of the series 09.04, does the proposed 
 new version 09.04.03 has any purpose?
 
 Regards
 Vikas
 
 On Apr 17, 2012, at 3:55 PM, Jacopo Cappellato wrote:
 
 I would like to perform the following maintenance 
 
 1) archive the following versions (they will disappears from drop down 
 when tasks are created):
 Release 09.04
 Release 09.04.01
 Release 10.04
 because they are all for superseded releases; if there are open issues 
 assigned (affects) to them we could bulk move them to versions Release 
 Branch 09.04 and Release Branch 10.04 
 
 2) create new versions (for upcoming releases):
 Release 09.04.03
 Release 10.04.03
 however new bugs should always be reported (affect) against the Release 
 Branch 09.04, Release Branch 10.04 and Release Branch 11.04 ; we could 
 use the Release 09.04.03 and Release 10.04.03 when the task is fixed in 
 the branch as the fixed in version.
 
 I think that #1 is rather important; I am not sure about #2.
 
 What do you think?
 
 Kind regards,
 
 Jacopo
 
 PS: I have also created Release 11.04.01 with a tentative release date of 
 May 15: I am going to use this version to log a series of tasks that are 
 required before the release; after the release I will archive this 
 version as the versions in #2 above.

[jira] [Commented] (OFBIZ-4813) ajax autocomplete and dialog during session timeout

2012-04-17 Thread Wai (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255663#comment-13255663
]

Wai commented on OFBIZ-4813:

Regarding point#4(centering of dialog):

I centered it as it looked unusual. Usually dialogs are at the center of the
screen. The modification was for esthetical reasons. I was not aware it was
like that by design given your explanation. I can change it back.

Regarding the change to label CommonSessionTimeoutPleaseLogIn:

The modification was made for the situation where a user has spent time filling
up a form and them through using the autocompleter realizes that a session
timeout has occurred. This normally would cause a mild panic. Hence the
message Your session has expired. A login is required. You can refresh the
page or save your data to login., lets the user know that there are 2 ways to
refresh the session. 1) refresh the page. Hence lose all changes. 2) save as
usually and expect to encounter a login screen during the process.

Regarding removal of code requestUrl = getViewNameWithSeparator(requestUrl) +
...:

The original code uses jQuery(...).load(...) to initiate an ajax request. The
new code uses jQuery.ajax(...). Hence, the code in question became unnecessary
as jQuery.ajax() requires specification of path and querystring separately.

Regarding the hardcoded timeout:

I should have defined a global variable to specify the value. I can corrected
it once all the points have been addressed.

Wai

ajax autocomplete and dialog during session timeout
---

Key: OFBIZ-4813
URL: https://issues.apache.org/jira/browse/OFBIZ-4813
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: Wai
Attachments: ofbiz-4813.patch, spinner.gif

1. autocomplete feature shows the message no records found during a session
timeout. This could be misleading for the user.
2. During a session timeout, clicking on ajax dialog button shows a large
frame containing a message indicating session has timeout. Should show a
more detailed message.
3. All ajax dialogs are on the left of browser window.
A number of fixes have been implemented for this issue.
1. At session timeout, user enters a character into autocomplete input box
results in a alert window popup.
2. At session timeout, clicking on ajax dialog button will cause alert window
to popup.
3. A large round spinner is shown when the ajax dialog is loading. This
spinner image comes from http://mentalized.net/activity-indicators/ and is
royalty free. Note the round spinner does not show in Tomahawk theme as it
uses its own spinner.
4. Now all ajax dialogs are centered.
5. Change session timeout message to something more detailed.
6. Server response to ajax request now contain html tags.

[jira] [Updated] (OFBIZ-4821) Error in rednring Reset field.

2012-04-17 Thread Sumit Pandit (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Pandit updated OFBIZ-4821:


Attachment: MacroFormRenderer.patch

Patch for issue.

 Error in rednring Reset field.
 --

 Key: OFBIZ-4821
 URL: https://issues.apache.org/jira/browse/OFBIZ-4821
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk
Reporter: Sumit Pandit
Priority: Blocker
 Attachments: MacroFormRenderer.patch


 MacroFormRenderer.renderResetField contains a missing entry when appending 
 title to renderResetField's StringWritter.
 MacroFormRenderer.java line# 1202
 sr.append( title=\);
 Where it should be 
 sr.append(\ title=\);
 Because of above reset/ button is not displaying on the screen. At back end 
 it is returning Freemarker parser exception.
 BTW it is one line change, if required I will submit the patch shortly.
 --
 Thanks and Regards
 Sumit Pandit

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-4814) eCommerce Profile Back Button Fail

2012-04-17 Thread Tom Burns (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Burns updated OFBIZ-4814:
-

Attachment: OFBIZ-4814 eCommerce Profile GoBack Branch.patch
OFBIZ-4814 eCommerce Profile GoBack Trunk.patch

 eCommerce Profile Back Button Fail
 --

 Key: OFBIZ-4814
 URL: https://issues.apache.org/jira/browse/OFBIZ-4814
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Priority: Minor
 Attachments: OFBIZ-4814 eCommerce Profile GoBack Branch.patch, 
 OFBIZ-4814 eCommerce Profile GoBack Trunk.patch, OFBIZ-4814 eCommerce Profile 
 GoBack.patch


 1. Some navigation buttons reached from the eCommerce Profile screen fail to 
 return to the Profile screen.
 Example:
 Login as DemoCustomer
 Click Profile
 Click Update In the Contact Information  Postal Address section.
 Click Go Back
 Expected: Return to profile page
 Actual: Remain on Edit Contact Information page
 2. Naming and display of back buttons is inconsistent across Profile Editing 
 screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]
 3. Create New Postal Address fails from OFBIZ-4801 Rev 1326397
 Error message
 State/Province --  
 Selected\Expected State Name = Expression selectedStateName is undefined on 
 line 163, column 42 in 
 component://ecommerce/webapp/ecommerce/customer/editcontactmech.ftl. The 
 problematic instruction: -- == ${selectedStateName} [on line 163,
 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4814) eCommerce Profile Back Button Fail

2012-04-17 Thread Tom Burns (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255699#comment-13255699
]

Tom Burns commented on OFBIZ-4814:
--

Jacques,

I'm going to upload a patch for the trunk and one for the branches to fix the
bug (1).
I've tested the branch batch on both 10.04 11.04
I will open a new issue for the improvement part.
I can not give you a clean patch on the improvements until after the bug has
been fixed.

Tom

eCommerce Profile Back Button Fail
--

Key: OFBIZ-4814
URL: https://issues.apache.org/jira/browse/OFBIZ-4814
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
Environment: demo-trunk
Reporter: Tom Burns
Priority: Minor
Attachments: OFBIZ-4814 eCommerce Profile GoBack Branch.patch,
OFBIZ-4814 eCommerce Profile GoBack Trunk.patch, OFBIZ-4814 eCommerce Profile
GoBack.patch

1. Some navigation buttons reached from the eCommerce Profile screen fail to
return to the Profile screen.
Example:
Login as DemoCustomer
Click Profile
Click Update In the Contact Information Postal Address section.
Click Go Back
Expected: Return to profile page
Actual: Remain on Edit Contact Information page
2. Naming and display of back buttons is inconsistent across Profile Editing
screens.
Example:
Changes Password label should be Go Back but is [Go Back]
3. Create New Postal Address fails from OFBIZ-4801 Rev 1326397
Error message
State/Province --
Selected\Expected State Name = Expression selectedStateName is undefined on
line 163, column 42 in
component://ecommerce/webapp/ecommerce/customer/editcontactmech.ftl. The
problematic instruction: -- == ${selectedStateName} [on line 163,

[jira] [Created] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency

2012-04-17 Thread Tom Burns (Created) (JIRA)

eCommerce Profile Improve Button Naming Consistency
---

 Key: OFBIZ-4822
 URL: https://issues.apache.org/jira/browse/OFBIZ-4822
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Priority: Minor
 Fix For: SVN trunk


This follows from OFBIZ-4814 bug fix.

In eCommerce the naming and display of back buttons is inconsistent across the 
Profile Editing screens.
Example:
Changes Password label should be Go Back but is [Go Back]


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4812) Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit component

2012-04-17 Thread Francis ANDRE (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255712#comment-13255712
 ] 

Francis ANDRE commented on OFBIZ-4812:
--

You miss an important point: all those improvements are for allowing hot 
replacement of class when running under the debug mode in Eclipse, which you 
cannot do if you remotely debug a ofbiz session started by ant, or you just run 
ofbiz under Eclipse because in this later case, ofbiz is using the ofbiz-*.jar 
and thus, one cannot use hot replacement of code. Even in the wiki 
https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse,
 it is clearly mentioned by P Gonon that

Note that when doing development work, you will have to stop OFBiz, run an Ant 
build and re-start. Because this method treats OFBiz as a plain Java up, you 
don't have any automatic classloading as you might be used to when using 
Eclipse-WTP and developing webapps.

Thus all those Jira for improvement are to allow a normal Eclipse debugging 
session as usual, with hot replacement of code.

When you do not want hot replacement of code, the methods stated in the 
https://cwiki.apache.org/confluence/display/OFBIZ/Running+and+Debugging+OFBiz+in+Eclipse
 works fine, but this is a different objective.

Thus, I am in favor to not revert the r1308085 and apply this one, which needs 
the replacement of the jackrabbit-core-2.3.3.jar by the patched one, otherwise 
ofbiz stops.


 Avoid the ClassNotFoundException on the jdbc driver used by jackrabbit 
 component
 

 Key: OFBIZ-4812
 URL: https://issues.apache.org/jira/browse/OFBIZ-4812
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
 Environment: WXP SP3, Sun SDK 1.6.0_30, PostgreSQL 9.2
Reporter: Francis ANDRE
 Attachments: jackrabbit-core-2.3.3.jar


 Hi
 When running ofbiz under Eclipse with the sources directories as classpath 
 and not the ofbiz-*.jar, the jcr component fails to load the jdbc driver 
 because jackrabbit-core is using Class.forName() instead of using the current 
 classloader of the thread. see https://issues.apache.org/jira/browse/JCR-3288
 I provide with this issue a jackrabbit-core-2.3.3.jar patched as described in 
 the JCR-3288 issue.
 Rgds

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (OFBIZ-4814) eCommerce Profile Back Button Fail

2012-04-17 Thread Jacques Le Roux (Assigned) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux reassigned OFBIZ-4814:
--

Assignee: Jacques Le Roux

 eCommerce Profile Back Button Fail
 --

 Key: OFBIZ-4814
 URL: https://issues.apache.org/jira/browse/OFBIZ-4814
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Attachments: OFBIZ-4814 eCommerce Profile GoBack Branch.patch, 
 OFBIZ-4814 eCommerce Profile GoBack Trunk.patch, OFBIZ-4814 eCommerce Profile 
 GoBack.patch


 1. Some navigation buttons reached from the eCommerce Profile screen fail to 
 return to the Profile screen.
 Example:
 Login as DemoCustomer
 Click Profile
 Click Update In the Contact Information  Postal Address section.
 Click Go Back
 Expected: Return to profile page
 Actual: Remain on Edit Contact Information page
 2. Naming and display of back buttons is inconsistent across Profile Editing 
 screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]
 3. Create New Postal Address fails from OFBIZ-4801 Rev 1326397
 Error message
 State/Province --  
 Selected\Expected State Name = Expression selectedStateName is undefined on 
 line 163, column 42 in 
 component://ecommerce/webapp/ecommerce/customer/editcontactmech.ftl. The 
 problematic instruction: -- == ${selectedStateName} [on line 163,
 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency

2012-04-17 Thread Jacques Le Roux (Assigned) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux reassigned OFBIZ-4822:
--

Assignee: Jacques Le Roux

 eCommerce Profile Improve Button Naming Consistency
 ---

 Key: OFBIZ-4822
 URL: https://issues.apache.org/jira/browse/OFBIZ-4822
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: SVN trunk


 This follows from OFBIZ-4814 bug fix.
 In eCommerce the naming and display of back buttons is inconsistent across 
 the Profile Editing screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency

2012-04-17 Thread Tom Burns (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom Burns updated OFBIZ-4822:
-

Attachment: OFBIZ-4822 eCommerce Profile GoBack Improvement.patch

 eCommerce Profile Improve Button Naming Consistency
 ---

 Key: OFBIZ-4822
 URL: https://issues.apache.org/jira/browse/OFBIZ-4822
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: SVN trunk

 Attachments: OFBIZ-4822 eCommerce Profile GoBack Improvement.patch


 This follows from OFBIZ-4814 bug fix.
 In eCommerce the naming and display of back buttons is inconsistent across 
 the Profile Editing screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency

2012-04-17 Thread Tom Burns (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255871#comment-13255871
 ] 

Tom Burns commented on OFBIZ-4822:
--

Jacques,

Please review carefully. I found some errors in the earlier patch where the 
javascript submits were not correct.

Thanks,

Tom


 eCommerce Profile Improve Button Naming Consistency
 ---

 Key: OFBIZ-4822
 URL: https://issues.apache.org/jira/browse/OFBIZ-4822
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: SVN trunk

 Attachments: OFBIZ-4822 eCommerce Profile GoBack Improvement.patch


 This follows from OFBIZ-4814 bug fix.
 In eCommerce the naming and display of back buttons is inconsistent across 
 the Profile Editing screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (OFBIZ-4814) eCommerce Profile Back Button Fail

2012-04-17 Thread Jacques Le Roux (Closed) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-4814.
--

   Resolution: Fixed
Fix Version/s: SVN trunk
   Release Branch 11.04
   Release Branch 10.04

Thanks Tom,

Your patch is in
trunk r1327260
R11.04 r1327264
R10.04 r1327261


You did not need to provide a patch for branches releases. Most of the time I 
can easily backport the trunk patches to the branches releases

 eCommerce Profile Back Button Fail
 --

 Key: OFBIZ-4814
 URL: https://issues.apache.org/jira/browse/OFBIZ-4814
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk

 Attachments: OFBIZ-4814 eCommerce Profile GoBack Branch.patch, 
 OFBIZ-4814 eCommerce Profile GoBack Trunk.patch, OFBIZ-4814 eCommerce Profile 
 GoBack.patch


 1. Some navigation buttons reached from the eCommerce Profile screen fail to 
 return to the Profile screen.
 Example:
 Login as DemoCustomer
 Click Profile
 Click Update In the Contact Information  Postal Address section.
 Click Go Back
 Expected: Return to profile page
 Actual: Remain on Edit Contact Information page
 2. Naming and display of back buttons is inconsistent across Profile Editing 
 screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]
 3. Create New Postal Address fails from OFBIZ-4801 Rev 1326397
 Error message
 State/Province --  
 Selected\Expected State Name = Expression selectedStateName is undefined on 
 line 163, column 42 in 
 component://ecommerce/webapp/ecommerce/customer/editcontactmech.ftl. The 
 problematic instruction: -- == ${selectedStateName} [on line 163,
 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (OFBIZ-3836) partybenifits leaves out using parytyrelationships

2012-04-17 Thread Jacques Le Roux (Closed) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacques Le Roux closed OFBIZ-3836.
--

No needs to keep this issue open

partybenifits leaves out using parytyrelationships
--

Original Estimate: 168h
Remaining Estimate: 168h

[jira] [Closed] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency

2012-04-17 Thread Jacques Le Roux (Closed) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux closed OFBIZ-4822.
--

Resolution: Fixed

Thanks Tom,

Your patch is in trunk at revision: 1327269.

You should not have included the editcontactmech.ftl changes since you already 
included them in the button fix. Anyway not a big deal I easily bypassed the 
conflict


 eCommerce Profile Improve Button Naming Consistency
 ---

 Key: OFBIZ-4822
 URL: https://issues.apache.org/jira/browse/OFBIZ-4822
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: SVN trunk

 Attachments: OFBIZ-4822 eCommerce Profile GoBack Improvement.patch


 This follows from OFBIZ-4814 bug fix.
 In eCommerce the naming and display of back buttons is inconsistent across 
 the Profile Editing screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4813) ajax autocomplete and dialog during session timeout

2012-04-17 Thread Jacques Le Roux (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255912#comment-13255912
]

Jacques Le Roux commented on OFBIZ-4813:

Hi Wai,

Agreed on CommonSessionTimeoutPleaseLogIn change. Better having it only in
English than keeping confusing/worrying previous even if we lose some
translation.

Agreed on removal of code requestUrl = getViewNameWithSeparator(requestUrl) +
...:

I let you provide a new patch to apply soon.

Thanks

ajax autocomplete and dialog during session timeout
---

Key: OFBIZ-4813
URL: https://issues.apache.org/jira/browse/OFBIZ-4813
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: Wai
Attachments: ofbiz-4813.patch, spinner.gif

[jira] [Commented] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency

2012-04-17 Thread Jacques Le Roux (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255922#comment-13255922
 ] 

Jacques Le Roux commented on OFBIZ-4822:


Tom,

double checking I found
{code}
Modified: 
ofbiz/trunk/specialpurpose/ecommerce/webapp/ecommerce/customer/changepassword.ftl
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/specialpurpose/ecommerce/webapp/ecommerce/customer/changepassword.ftl?rev=1327269r1=1327268r2=1327269view=diff
==
--- 
ofbiz/trunk/specialpurpose/ecommerce/webapp/ecommerce/customer/changepassword.ftl
 (original)
+++ 
ofbiz/trunk/specialpurpose/ecommerce/webapp/ecommerce/customer/changepassword.ftl
 Tue Apr 17 20:12:11 2012
@@ -17,9 +17,10 @@ specific language governing permissions 
 under the License.
 --
 div class=screenlet
-  h2${uiLabelMap.PartyChangePassword}/h2
-  a href=@ofbizUrlauthview/${donePage}/@ofbizUrl 
class=button[${uiLabelMap.CommonGoBack}]/a
-  a href=javascript:document.getElementById('changepasswordform').submit() 
class=button[${uiLabelMap.CommonSave}]/a
+  h2${uiLabelMap.PartyChangePassword}/h2  
+  nbsp;a href=@ofbizUrl${donePage}/@ofbizUrl 
class=button${uiLabelMap.CommonGoBack}/a
+  nbsp;a 
href=javascript:document.getElementById('changepasswordform').submit() 
class=button${uiLabelMap.CommonSave}/a
{code}

I guess the authview/ removing was not intended, right?

 eCommerce Profile Improve Button Naming Consistency
 ---

 Key: OFBIZ-4822
 URL: https://issues.apache.org/jira/browse/OFBIZ-4822
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
 Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
 Fix For: SVN trunk

 Attachments: OFBIZ-4822 eCommerce Profile GoBack Improvement.patch


 This follows from OFBIZ-4814 bug fix.
 In eCommerce the naming and display of back buttons is inconsistent across 
 the Profile Editing screens.
 Example:
 Changes Password label should be Go Back but is [Go Back]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Cleaning some of the Jira versions

2012-04-17 Thread Jacques Le Roux

Since we have decided to no longer maintain R09.04 (and below or related, like R09.04.02) I guess it's better to not confuse users 
and no longer propose Release Branch 09.04 (or below/related) in Jira. This does not prevent anybody to explicitly provide a patch 
for below R10.04 release branch users...


Jacques

From: Vikas Mayur vikasma...@gmail.com

No problem Jacopo :)
The proposal otherwise looks good. We would perhaps need Release Branch 09.04, even though the code will not be committed to 
this release branch but still one can post bug (if any) and/or attach patch for the fixes etc.


Regards
Vikas

On Apr 17, 2012, at 5:55 PM, Jacopo Cappellato wrote:


ah ah, you are right Vikas!
Please disregard the proposal about 09.04.03... I probably need another coffee

Jacopo

On Apr 17, 2012, at 12:40 PM, Vikas Mayur wrote:


Jacopo,

Since 09.04.02 was the last release of the series 09.04, does the proposed new 
version 09.04.03 has any purpose?

Regards
Vikas

On Apr 17, 2012, at 3:55 PM, Jacopo Cappellato wrote:


I would like to perform the following maintenance

1) archive the following versions (they will disappears from drop down when 
tasks are created):
Release 09.04
Release 09.04.01
Release 10.04
because they are all for superseded releases; if there are open issues assigned (affects) to them we could bulk move them to 
versions Release Branch 09.04 and Release Branch 10.04


2) create new versions (for upcoming releases):
Release 09.04.03
Release 10.04.03
however new bugs should always be reported (affect) against the Release Branch 09.04, Release Branch 10.04 and Release 
Branch 11.04 ; we could use the Release 09.04.03 and Release 10.04.03 when the task is fixed in the branch as the fixed 
in version.


I think that #1 is rather important; I am not sure about #2.

What do you think?

Kind regards,

Jacopo

PS: I have also created Release 11.04.01 with a tentative release date of May 15: I am going to use this version to log a 
series of tasks that are required before the release; after the release I will archive this version as the versions in #2 
above.

[jira] [Updated] (OFBIZ-4813) ajax autocomplete and dialog during session timeout

2012-04-17 Thread Wai (Updated) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wai updated OFBIZ-4813:
---

Attachment: ofbiz-4813.patch

Here's the updated patch.

ajax autocomplete and dialog during session timeout
---

Key: OFBIZ-4813
URL: https://issues.apache.org/jira/browse/OFBIZ-4813
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: Wai
Attachments: ofbiz-4813.patch, ofbiz-4813.patch, spinner.gif

[jira] [Updated] (OFBIZ-4813) ajax autocomplete and dialog during session timeout

2012-04-17 Thread Wai (Updated) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wai updated OFBIZ-4813:
---

Attachment: ofbiz-4813.patch

Please disregard previous patch.

ajax autocomplete and dialog during session timeout
---

Key: OFBIZ-4813
URL: https://issues.apache.org/jira/browse/OFBIZ-4813
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: Wai
Attachments: ofbiz-4813.patch, ofbiz-4813.patch, ofbiz-4813.patch,
spinner.gif

[jira] [Assigned] (OFBIZ-4813) ajax autocomplete and dialog during session timeout

2012-04-17 Thread Jacques Le Roux (Assigned) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacques Le Roux reassigned OFBIZ-4813:
--

Assignee: Jacques Le Roux

ajax autocomplete and dialog during session timeout
---

Key: OFBIZ-4813
URL: https://issues.apache.org/jira/browse/OFBIZ-4813
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: Wai
Assignee: Jacques Le Roux
Attachments: ofbiz-4813.patch, ofbiz-4813.patch, ofbiz-4813.patch,
spinner.gif

[jira] [Commented] (OFBIZ-4813) ajax autocomplete and dialog during session timeout

2012-04-17 Thread Jacques Le Roux (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256038#comment-13256038
]

Jacques Le Roux commented on OFBIZ-4813:

Sounds good,I will wait a timeout to check before committing. I wonder if we
should not also replace the Tomahawk spinner?

ajax autocomplete and dialog during session timeout
---

[jira] [Updated] (OFBIZ-4821) Form-Widget : Error in rendering Reset field.

2012-04-17 Thread Sumit Pandit (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Pandit updated OFBIZ-4821:


Summary: Form-Widget : Error in rendering Reset field.  (was: Error in 
rednring Reset field.)

 Form-Widget : Error in rendering Reset field.
 -

 Key: OFBIZ-4821
 URL: https://issues.apache.org/jira/browse/OFBIZ-4821
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk
Reporter: Sumit Pandit
Priority: Blocker
 Attachments: MacroFormRenderer.patch


 MacroFormRenderer.renderResetField contains a missing entry when appending 
 title to renderResetField's StringWritter.
 MacroFormRenderer.java line# 1202
 sr.append( title=\);
 Where it should be 
 sr.append(\ title=\);
 Because of above reset/ button is not displaying on the screen. At back end 
 it is returning Freemarker parser exception.
 BTW it is one line change, if required I will submit the patch shortly.
 --
 Thanks and Regards
 Sumit Pandit

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

50 matches

Mail list logo