from:"Harsh Vijaywargiya"

Re: Welcome Rishi Solanki as new PMC member

2020-04-28 Thread Harsh Vijaywargiya

Many Congratulations Rishi!!

Thanks & Regards,
Harsh

On Wed, Apr 29, 2020 at 10:52 AM Mridul Pathak <
mridul.pat...@hotwaxsystems.com> wrote:

> Congratulations Rishi!!
>
> Thanks
> Mridul Pathak
>
> > On 28-Apr-2020, at 7:52 PM, Jacopo Cappellato <
> jacopo.cappell...@gmail.com> wrote:
> >
> > The OFBiz PMC has invited Rishi Solanki to become member of the committee
> > and we are glad to announce that he has accepted the nomination.
> >
> > On behalf of the OFBiz PMC, welcome on board!
>
>

Re: Welcome Swapnil M Mane as new PMC member

2020-04-23 Thread Harsh Vijaywargiya

Many Congratulations Swapnil!!

Thanks & Regards,
Harsh

On Thu, Apr 23, 2020 at 6:52 PM Girish Vasmatkar <
girish.vasmat...@hotwaxsystems.com> wrote:

> Congratulations, Swapnil.
>
> Best,
> Girish
>
> On Thu, Apr 23, 2020 at 6:48 PM Ankush Upadhyay <
> ankush.upadh...@hotwaxsystems.com> wrote:
>
> > Many Congratulations, Swapnil!!!
> >
> > Kind Regards,
> > Ankush Upadhyay
> > Senior Technical Consultant
> >
> > *HotWax Systems*
> > *Enterprise open source experts*
> > cell: +91-8109201285
> > office: 0731-409-3684
> > http://www.hotwaxsystems.com
> >
> >
> > On Thu, Apr 23, 2020 at 5:47 PM Ashish Vijaywargiya 
> > wrote:
> >
> > > Many congratulations, Swapnil!!
> > >
> > > Thanks,
> > > Ashish Vijaywargiya
> > >
> > > On Thu, Apr 23, 2020 at 5:02 PM Jacques Le Roux <
> > > jacques.le.r...@les7arts.com> wrote:
> > >
> > > > The OFBiz PMC has invited Swapnil M Mane to become member of the
> > > committee
> > > > and we are glad to announce that he has accepted the nomination.
> > > >
> > > > On behalf of the OFBiz PMC, welcome on board!
> > > >
> > > >
> > >
> >
>

Re: Welcome to Vasmatkar as new committer!

2020-04-22 Thread Harsh Vijaywargiya

Many Congratulations Girish!!

Thanks & Regards,
Harsh

On Thu, Apr 23, 2020 at 10:22 AM Devanshu Vyas 
wrote:

> Congratulations Girish!
>
> Thanks & Regards,
> Devanshu Vyas.
>
>
> On Wed, Apr 22, 2020 at 3:09 PM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > The OFBiz PMC has invited Girish to become a new committer and we are
> > pleased  to announce that he has accepted.
> >
> > Girish is part of the community for near 2 years and has proposed several
> > smart propositions notably related to security and GraphQL, but not only.
> >
> > Please join me in welcoming and congratulating Girish.
> >
> > Jacques
> >
> >
> >
>

Re: Welcome Pranay Pandey as a new PMC member

2019-09-25 Thread Harsh Vijaywargiya


Many Congratulations Pranay!!

Thanks & Regards,

Harsh


On Wednesday 25 September 2019 11:45 AM, Chandan Khandelwal wrote:

Many Congratulations Pranay!

Kind Regards,
Chandan Khandelwal



On Wed, Sep 25, 2019 at 10:56 AM Aditya Sharma 
wrote:


Felicitations Pranay !!

Thanks and Regards,
Aditya Sharma

On Wed, Sep 25, 2019 at 10:44 AM Suraj Khurana 
wrote:


Many Congratulations Pranay !!

--
Best Regards,
Suraj Khurana
Technical Consultant





On Wed, Sep 25, 2019 at 10:14 AM Ashish Vijaywargiya <
ashish.vijaywarg...@hotwaxsystems.com> wrote:


Many congratulations Pranay!!

--
Kind Regards,
Ashish Vijaywargiya
Vice President of Operations
*HotWax Systems*
*Enterprise open source experts*
cell: +91-9893479711
http://www.hotwaxsystems.com



On Tue, Sep 24, 2019 at 9:07 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


The OFBiz PMC has invited Pranay Pandey to become a new member of the
committee and we are glad to announce that he has accepted the

nomination.

Welcome on board Pranay!

Jacques (on behalf of the OFBiz PMC)

Re: Welcome Deepak Dixit as a new PMC member

2017-02-24 Thread Harsh Vijaywargiya


Great!! Many many congratulations to Deepak!!

Thanks & Regards,
Harsh
On Friday 24 February 2017 06:38 PM, Jacques Le Roux wrote:
The OFBiz PMC has invited Deepak Dixit to become a new member of the 
committee; and the committee members are happy to announce that he has 
accepted.


Deepak has been involved in OFBiz for a long time now, and is a 
respected committer for 2 years.


We are sure Deepak will help us to take good decisions in favour of a 
bright future for OFBiz!


Please join me in welcoming and congratulating Deepak.

Thanks

Jacques
PS: Deepak, I let you change your status on the wiki PMC page :)

Re: Welcome Swapnil Shah as a New Committer!

2017-02-14 Thread Harsh Vijaywargiya


Congratulations Swapnil !!


Thanks & Regards,

Harsh


On Tuesday 14 February 2017 06:52 PM, Yash Sharma wrote:

Congratulations Swapnil Shah !

On Tue, Feb 14, 2017 at 6:05 PM Nitesh Goyal 
wrote:


Congratulations Swapnil!

Regards,

Nitesh Goyal

https://in.linkedin.com/pub/nitesh-goyal/3a/178/b06




On Tue, Feb 14, 2017 at 4:30 PM, Sharan Foga  wrote:


The OFBiz PMC has invited Swapnil Shah to become a new committer and are
happy to announce that he has accepted.

Swapnil has been involved in OFBiz for a few years and has been active on
both the development and user mailing lists responding to some quite
technical functional questions.

Some of the key factors considered for inviting him were as follows:

- He has very good functional knowledge about OFBiz and this is a

valuable

skill that is useful to developers and users
- He is polite, positive, friendly and collaborative when dealing the
community discussions on the mailings lists or Jira
- He has raised Jiras, performed testing on patches and new other
functionality
- The PMC would like to see a wide range of people from the community
(developers and non-developers) recognised for their contributions to the
project.

Please join me in welcoming and congratulating Swapnil.

Thanks
Sharan

Re: svn commit: r1761181 [1/2] - in /ofbiz/trunk/applications/product/src/main/java/org/apache/ofbiz: product/category/ product/category/ftl/ product/config/ product/feature/ product/imagemanagement/

2016-10-03 Thread Harsh Vijaywargiya


Hi Jacques,

This is good idea to keep such information on JIRA ticket so anyone can 
easily pick it.


I have created https://issues.apache.org/jira/browse/OFBIZ-8341

If I find more such classes then I will add in this ticket, and will 
also try to provide the patch for this soon.


Thanks & Regards,

Harsh


On Monday 03 October 2016 04:48 PM, Jacques Le Roux wrote:

Hi Harsh,

Any chances about that, should we not create a Jira?

Thanks

Jacques


Le 17/09/2016 à 13:52, Harsh Vijaywargiya a écrit :

Hi Jacques, Ashish

I also noted few classes with such patterns during clean up, and in 
first attempt I just cleaned the default TODOs.


I will provide a patch with this and other suggested enhancements.

Thanks & Regards,

Harsh


On Saturday 17 September 2016 04:56 PM, Jacques Le Roux wrote:

Hi Ashish,

This should be improved, exception in services should use 
Debug.logError,  use return ServiceUtil.returnError and not swallow 
the exception



Le 17/09/2016 à 12:34, ash...@apache.org a écrit :
  product = 
EntityQuery.use(delegator).from("Product").where("productId", 
productId).queryOne();

  } catch (GenericEntityException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  if (EntityTypeUtil.hasParentType(delegator, 
"ProductType", "productTypeId", product.getString("productTypeId"), 
"parentTypeId", "MARKETING_PKG")) {

  try {
  resultOutput = 
dispatcher.runSync("getMktgPackagesAvailable", contextInput);

  } catch (GenericServiceException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  } else {
  try {
  resultOutput = 
dispatcher.runSync("getInventoryAvailableByFacility", contextInput);

  } catch (GenericServiceException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  }
@@ -910,7 +898,6 @@ public class InventoryServices {
  try {
  productPrices = 
EntityQuery.use(delegator).from("ProductPrice").where("productId",productId).orderBy("-fromDate").cache(true).queryList();

  } catch (GenericEntityException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  //change this for product price
@@ -977,7 +964,6 @@ public class InventoryServices {
  EntityOperator.AND);
  salesUsageIt = 
EntityQuery.use(delegator).from(salesUsageViewEntity).where(cond).queryIterator();

  } catch (GenericEntityException e2) {
-// TODO Auto-generated catch block
  e2.printStackTrace();
  }
  @@ -996,7 +982,6 @@ public class InventoryServices {
  try {
  salesUsageIt.close();
  } catch (GenericEntityException e2) {
-// TODO Auto-generated catch block
  e2.printStackTrace();
  }
  @@ -1013,7 +998,6 @@ public class InventoryServices {
  EntityOperator.AND);
  productionUsageIt = 
EntityQuery.use(delegator).from(productionUsageViewEntity).where(conditions).queryIterator();

  } catch (GenericEntityException e1) {
-// TODO Auto-generated catch block
  e1.printStackTrace();
  }
  @@ -1032,7 +1016,6 @@ public class InventoryServices {
  try {
  productionUsageIt.close();
  } catch (GenericEntityException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }


Thanks!

Jacques

Re: svn commit: r1761181 [1/2] - in /ofbiz/trunk/applications/product/src/main/java/org/apache/ofbiz: product/category/ product/category/ftl/ product/config/ product/feature/ product/imagemanagement/

2016-09-17 Thread Harsh Vijaywargiya


Hi Jacques, Ashish

I also noted few classes with such patterns during clean up, and in 
first attempt I just cleaned the default TODOs.


I will provide a patch with this and other suggested enhancements.

Thanks & Regards,

Harsh


On Saturday 17 September 2016 04:56 PM, Jacques Le Roux wrote:

Hi Ashish,

This should be improved, exception in services should use 
Debug.logError,  use return ServiceUtil.returnError and not swallow 
the exception



Le 17/09/2016 à 12:34, ash...@apache.org a écrit :
  product = 
EntityQuery.use(delegator).from("Product").where("productId", 
productId).queryOne();

  } catch (GenericEntityException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  if (EntityTypeUtil.hasParentType(delegator, "ProductType", 
"productTypeId", product.getString("productTypeId"), "parentTypeId", 
"MARKETING_PKG")) {

  try {
  resultOutput = 
dispatcher.runSync("getMktgPackagesAvailable", contextInput);

  } catch (GenericServiceException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  } else {
  try {
  resultOutput = 
dispatcher.runSync("getInventoryAvailableByFacility", contextInput);

  } catch (GenericServiceException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  }
@@ -910,7 +898,6 @@ public class InventoryServices {
  try {
  productPrices = 
EntityQuery.use(delegator).from("ProductPrice").where("productId",productId).orderBy("-fromDate").cache(true).queryList();

  } catch (GenericEntityException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }
  //change this for product price
@@ -977,7 +964,6 @@ public class InventoryServices {
  EntityOperator.AND);
  salesUsageIt = 
EntityQuery.use(delegator).from(salesUsageViewEntity).where(cond).queryIterator();

  } catch (GenericEntityException e2) {
-// TODO Auto-generated catch block
  e2.printStackTrace();
  }
  @@ -996,7 +982,6 @@ public class InventoryServices {
  try {
  salesUsageIt.close();
  } catch (GenericEntityException e2) {
-// TODO Auto-generated catch block
  e2.printStackTrace();
  }
  @@ -1013,7 +998,6 @@ public class InventoryServices {
  EntityOperator.AND);
  productionUsageIt = 
EntityQuery.use(delegator).from(productionUsageViewEntity).where(conditions).queryIterator();

  } catch (GenericEntityException e1) {
-// TODO Auto-generated catch block
  e1.printStackTrace();
  }
  @@ -1032,7 +1016,6 @@ public class InventoryServices {
  try {
  productionUsageIt.close();
  } catch (GenericEntityException e) {
-// TODO Auto-generated catch block
  e.printStackTrace();
  }


Thanks!

Jacques

Re: svn commit: r1757991 - in /ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manu facturing: bom/ jobshopmgt/ mrp/ techdata/

2016-09-01 Thread Harsh Vijaywargiya


Thanks Jacques,

Sounds good. I will take care of this suggestion in coming commits.

Thanks & Regards,
Harsh
On Wednesday 31 August 2016 04:51 PM, Jacques Le Roux wrote:
OK I checked, the commented out lines were from pre Apache Era. So 
indeed it was not an easy decision.


For

public void print(List arr, BigDecimal quantity, int 
depth, boolean excludeWIPs) {


I believe the lines were commented out because it's a recursive 
method. I still believe we should never let exceptions escape. The 
probability it happens is low. Another reason to not let it escape: it 
should not clutter the log but when really needed.


So I simply suggest to add

Debug.logError(e, "Problem calling the " + serviceName + " service 
(called by the createManufacturingOrder service)", module);


there.

Globally here is my take

Index: 
applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java

===
--- 
applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java 
(revision 1758522)
+++ 
applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java 
(working copy)

@@ -292,7 +292,7 @@
 variantProduct = 
variantProducts.get(0);

 }
 } catch (GenericServiceException e) {
-if (Debug.infoOn()) 
Debug.logInfo("Error calling getProductVariant service " + 
e.getMessage(), module);
+Debug.logError("Error calling 
getProductVariant service " + e.getMessage(), module);

 }
 if (variantProduct != null) {
 newNode = new 
BOMNode(variantProduct, dispatcher, userLogin);

@@ -433,7 +433,7 @@
 this.quantity = calcQuantity;
 }
 } catch (GenericServiceException e) {
-
+Debug.logError(e, "Problem calling the " + 
serviceName + " service (called by the createManufacturingOrder 
service)", module);

 }
 } else {
 this.quantity = 
quantity.multiply(quantityMultiplier).multiply(scrapFactor);

@@ -573,7 +573,7 @@
 }
 }
 } catch (GenericEntityException e) {
-
+Debug.logError(e, "Problem calling the 
getManufacturingComponents service", module);

 }
 }
 return UtilMisc.toMap("productionRunId", productionRunId, 
"endDate", endDate);


What to you think?

Jacques


Le 30/08/2016 à 11:21, Jacques Le Roux a écrit :

Le 30/08/2016 à 08:29, Jacopo Cappellato a écrit :
Highlighting code that could be improved rather than fixing it is a 
good

way to help potential contributors.
However, and I think this is the reason for Scott's remark, you 
should not
have addressed your review/request to individual 
committer/contributor (if
the defect you have noticed was not introduced by their 
contribution, as in

this case).

OK, got the subtle nuance, thanks

Jacques

Re: svn commit: r1757991 - in /ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manu facturing: bom/ jobshopmgt/ mrp/ techdata/

2016-08-29 Thread Harsh Vijaywargiya

Thanks Jacques for review comment. I think in such case it could be 
better to uncomment such log statements from Exception block, right? or 
we should leave it as is?


Thanks & Regards,
Harsh


On Saturday 27 August 2016 06:19 PM, Jacques Le Roux wrote:

Hi Ashish, Harsh,

Please don't let swallowed exceptions in code, there were 2 
opportunities here ;)


Thanks


Le 27/08/2016 à 13:27, ash...@apache.org a écrit :

Author: ashish
Date: Sat Aug 27 11:27:47 2016
New Revision: 1757991

URL: http://svn.apache.org/viewvc?rev=1757991&view=rev
Log:
Applied patch from jira issue - OFBIZ-7848 - Clean up commented out 
code in Java source for Manufacturing.

Thanks Harsh for the contribution.

Modified:
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/jobshopmgt/ProductionRun.java
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/jobshopmgt/ProductionRunServices.java
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/mrp/MrpServices.java
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/mrp/ProposedOrder.java
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/techdata/TechDataServices.java

Modified: 
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java?rev=1757991&r1=1757990&r2=1757991&view=diff
== 

--- 
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java 
(original)
+++ 
ofbiz/trunk/applications/manufacturing/src/main/java/org/apache/ofbiz/manufacturing/bom/BOMNode.java 
Sat Aug 27 11:27:47 2016

@@ -436,7 +433,7 @@ public class BOMNode {
  this.quantity = calcQuantity;
  }
  } catch (GenericServiceException e) {
-//Debug.logError(e, "Problem calling the 
getManufacturingComponents service", module);

+
  }
  } else {
  this.quantity = 
quantity.multiply(quantityMultiplier).multiply(scrapFactor);

@@ -576,7 +573,7 @@ public class BOMNode {
  }
  }
  } catch (GenericEntityException e) {
-//Debug.logError(e, "Problem calling the 
getManufacturingComponents service", module);

+
  }
  }
  return UtilMisc.toMap("productionRunId", productionRunId, 
"endDate", endDate);

[jira] [Updated] (OFBIZ-7838) Clean up commented out code in Java source for Content

2016-07-16 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7838:
--
Attachment: OFBIZ-7838.patch

> Clean up commented out code in Java source for Content
> --
>
> Key: OFBIZ-7838
> URL: https://issues.apache.org/jira/browse/OFBIZ-7838
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7838.patch
>
>
> Clean up commented out code in Java source for Content



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7826) Clean up commented out code in Java source for Accounting

2016-07-16 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380720#comment-15380720
 ] 

Harsh Vijaywargiya commented on OFBIZ-7826:
---

Attached is the new patch for this ticket

> Clean up commented out code in Java source for Accounting
> -
>
> Key: OFBIZ-7826
> URL: https://issues.apache.org/jira/browse/OFBIZ-7826
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7826.patch
>
>
> Clean up commented out code in Java source for Accounting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7826) Clean up commented out code in Java source for Accounting

2016-07-16 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7826:
--
Attachment: OFBIZ-7826.patch

> Clean up commented out code in Java source for Accounting
> -
>
> Key: OFBIZ-7826
> URL: https://issues.apache.org/jira/browse/OFBIZ-7826
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7826.patch
>
>
> Clean up commented out code in Java source for Accounting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7826) Clean up commented out code in Java source for Accounting

2016-07-16 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7826:
--
Attachment: (was: OFBIZ-7826.patch)

> Clean up commented out code in Java source for Accounting
> -
>
> Key: OFBIZ-7826
> URL: https://issues.apache.org/jira/browse/OFBIZ-7826
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Clean up commented out code in Java source for Accounting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7826) Clean up commented out code in Java source for Accounting

2016-07-16 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380677#comment-15380677
 ] 

Harsh Vijaywargiya commented on OFBIZ-7826:
---

Removed the old patch as package are renamed now so I will create and upload 
the new patch. 

> Clean up commented out code in Java source for Accounting
> -
>
> Key: OFBIZ-7826
> URL: https://issues.apache.org/jira/browse/OFBIZ-7826
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
> Fix For: Upcoming Branch
>
>
> Clean up commented out code in Java source for Accounting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7857) Clean up commented out code in Java source for Workeffort

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7857:
-

 Summary: Clean up commented out code in Java source for Workeffort
 Key: OFBIZ-7857
 URL: https://issues.apache.org/jira/browse/OFBIZ-7857
 Project: OFBiz
  Issue Type: Sub-task
  Components: workeffort
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Workeffort



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7855) Clean up commented out code in Java source for Party

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7855:
-

 Summary: Clean up commented out code in Java source for Party
 Key: OFBIZ-7855
 URL: https://issues.apache.org/jira/browse/OFBIZ-7855
 Project: OFBiz
  Issue Type: Sub-task
  Components: party
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Party



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7856) Clean up commented out code in Java source for Product

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7856:
-

 Summary: Clean up commented out code in Java source for Product
 Key: OFBIZ-7856
 URL: https://issues.apache.org/jira/browse/OFBIZ-7856
 Project: OFBiz
  Issue Type: Sub-task
  Components: product
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Party



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7854) Clean up commented out code in Java source for Order

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7854:
-

 Summary: Clean up commented out code in Java source for Order
 Key: OFBIZ-7854
 URL: https://issues.apache.org/jira/browse/OFBIZ-7854
 Project: OFBiz
  Issue Type: Sub-task
  Components: order
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Order



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7851) Clean up commented out code in Java source for Marketing

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7851:
-

 Summary: Clean up commented out code in Java source for Marketing
 Key: OFBIZ-7851
 URL: https://issues.apache.org/jira/browse/OFBIZ-7851
 Project: OFBiz
  Issue Type: Sub-task
  Components: marketing
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Marketing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7848) Clean up commented out code in Java source for Manufacturing

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7848:
-

 Summary: Clean up commented out code in Java source for 
Manufacturing
 Key: OFBIZ-7848
 URL: https://issues.apache.org/jira/browse/OFBIZ-7848
 Project: OFBiz
  Issue Type: Sub-task
  Components: manufacturing
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Manufacturing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7838) Clean up commented out code in Java source for Content

2016-07-16 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7838:
-

 Summary: Clean up commented out code in Java source for Content
 Key: OFBIZ-7838
 URL: https://issues.apache.org/jira/browse/OFBIZ-7838
 Project: OFBiz
  Issue Type: Sub-task
  Components: content
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Content



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7826) Clean up commented out code in Java source for Accounting

2016-07-16 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7826:
--
Attachment: OFBIZ-7826.patch

> Clean up commented out code in Java source for Accounting
> -
>
> Key: OFBIZ-7826
> URL: https://issues.apache.org/jira/browse/OFBIZ-7826
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7826.patch
>
>
> Clean up commented out code in Java source for Accounting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7826) Clean up commented out code in Java source for Accounting

2016-07-15 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7826:
-

 Summary: Clean up commented out code in Java source for Accounting
 Key: OFBIZ-7826
 URL: https://issues.apache.org/jira/browse/OFBIZ-7826
 Project: OFBiz
  Issue Type: Sub-task
  Components: accounting
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor
 Fix For: Upcoming Branch


Clean up commented out code in Java source for Accounting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Rename artifacts from org.ofbiz to org.apache.ofbiz

2016-07-13 Thread Harsh Vijaywargiya

Thanks Sharan for sharing this guideline. I am interested in this 
activity and will take care of it once Jira ticket is created.


Thanks & Regards,
Harsh
On Wednesday 13 July 2016 04:11 PM, Sharan Foga wrote:

Hi Everyone

Sorry to add more workload but there is another another ASF guideline regarding 
the naming of artifacts that we need to comply with.

Project "artifacts should include apache in the title as it gives trademark 
protection". This means that we need to rename our existing artifacts from

org.ofbiz.

to

   org.apache.ofbiz...

I'll create a JIRA for this so please try to include this as part of the 
current trunk changes.

Thanks
Sharan

[jira] [Closed] (OFBIZ-7158) Export PDF functionality throws exception on Inventory Evaluation screen

2016-07-04 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya closed OFBIZ-7158.
-
Resolution: Fixed

Seems same fix is committed in another ticket. So closing this ticket.

> Export PDF functionality throws exception on Inventory Evaluation screen
> 
>
> Key: OFBIZ-7158
> URL: https://issues.apache.org/jira/browse/OFBIZ-7158
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
>Reporter: Pritam Kute
>Assignee: Ashish Vijaywargiya
> Attachments: OFBIZ-7158.patch
>
>
> Steps to regenerate:
> 1) Go to Accounting
> 2) Click on Organisation GL Settings
> 3) Click on Accounting
> 4) Click on Reports
> 5) Click on Inventory Valuation
> 6) Select 'My Retail Store' option in facility id dropdown menu
> 7) Then click on 'Submit'
> 8) Click on 'Export as PDF'
> It will throw following error:
> [java] 2016-06-01 20:11:58,982 |http-nio-8443-exec-9 |ScreenFopViewHandler
>   |E| Unable to transform FO file: org.apache.fop.apps.FOPException: 
> org.apache.fop.fo.ValidationException: null:88:34: "fo:table-body" is missing 
> child elements. Required content model: marker* (table-row+|table-cell+) (See 
> position 88:34)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7158) Export PDF functionality throws exception on Inventory Evaluation screen

2016-06-27 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7158:
--
Attachment: OFBIZ-7158.patch

> Export PDF functionality throws exception on Inventory Evaluation screen
> 
>
> Key: OFBIZ-7158
> URL: https://issues.apache.org/jira/browse/OFBIZ-7158
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
>Reporter: Pritam Kute
>Assignee: Pritam Kute
> Attachments: OFBIZ-7158.patch
>
>
> Steps to regenerate:
> 1) Go to Accounting
> 2) Click on Organisation GL Settings
> 3) Click on Accounting
> 4) Click on Reports
> 5) Click on Inventory Valuation
> 6) Select 'My Retail Store' option in facility id dropdown menu
> 7) Then click on 'Submit'
> 8) Click on 'Export as PDF'
> It will throw following error:
> [java] 2016-06-01 20:11:58,982 |http-nio-8443-exec-9 |ScreenFopViewHandler
>   |E| Unable to transform FO file: org.apache.fop.apps.FOPException: 
> org.apache.fop.fo.ValidationException: null:88:34: "fo:table-body" is missing 
> child elements. Required content model: marker* (table-row+|table-cell+) (See 
> position 88:34)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6421) Unable to create New Communication from LEAD in SFA

2016-06-27 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-6421:
--
Attachment: OFBIZ-6421.patch

> Unable to create New Communication from LEAD in SFA
> ---
>
> Key: OFBIZ-6421
> URL: https://issues.apache.org/jira/browse/OFBIZ-6421
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: 13.07.01
>Reporter: Kian Yen Mah
>    Assignee: Harsh Vijaywargiya
> Attachments: OFBIZ-6421.patch
>
>
> Select Lead in SFA. Click COMMUNICATIONS. Click NEW COMMUNICATION. Click SAVE.
> The Following Errors Occurred:
> Exception thrown while performing entity find: [GenericDelegator.findOne] 
> Passed primary key is not a valid primary key: 
> [GenericEntity:CommunicationEventWorkEff][communicationEventId,10010(java.lang.String)]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7552) Clean up of deprecated code or shows warnings

2016-06-22 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7552:
-

 Summary: Clean up of deprecated code or shows warnings
 Key: OFBIZ-7552
 URL: https://issues.apache.org/jira/browse/OFBIZ-7552
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya


In our Re-Factor To-Do List one of the item is to clean up the code with 
warnings. 
This is the parent ticket and I will further create sub tasks under it for the 
component which shows warning or use the deprecated code.
Essentially this is for Java code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7536) Clean up commented out code

2016-06-22 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7536:
-

 Summary: Clean up commented out code
 Key: OFBIZ-7536
 URL: https://issues.apache.org/jira/browse/OFBIZ-7536
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
 Fix For: Upcoming Branch


In our Re-Factor To-Do List one of the item is to clean up the commented out 
code. 
This is the parent ticket and I will further create sub tasks under it so that 
we do not push large change in one commit.
This includes Java, Xml, Groovy and FTL files. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7193) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7193:
--
Affects Version/s: Trunk

> Checks --> Print (PDF) should be open in a new window
> -
>
> Key: OFBIZ-7193
> URL: https://issues.apache.org/jira/browse/OFBIZ-7193
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
>    Reporter: Harsh Vijaywargiya
>Assignee: Harsh Vijaywargiya
>Priority: Minor
> Attachments: OFBIZ-7193.patch
>
>
> Go to Accounting Manager --> Organization GL Settings 
> Click on Accounting --> Checks
> In Checks To Print click on button Print (PDF)
> PDF gets open in same window.
> To have the UI consistency it should be open in new window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-7193) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-7193:
--
Attachment: OFBIZ-7193.patch

> Checks --> Print (PDF) should be open in a new window
> -
>
> Key: OFBIZ-7193
> URL: https://issues.apache.org/jira/browse/OFBIZ-7193
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>Affects Versions: Trunk
>    Reporter: Harsh Vijaywargiya
>Assignee: Harsh Vijaywargiya
>Priority: Minor
> Attachments: OFBIZ-7193.patch
>
>
> Go to Accounting Manager --> Organization GL Settings 
> Click on Accounting --> Checks
> In Checks To Print click on button Print (PDF)
> PDF gets open in same window.
> To have the UI consistency it should be open in new window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7194) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya closed OFBIZ-7194.
-
Resolution: Duplicate

Due to some internet issues or Jira response this duplicate ticket was created 
so closing it now.

> Checks --> Print (PDF) should be open in a new window
> -
>
> Key: OFBIZ-7194
> URL: https://issues.apache.org/jira/browse/OFBIZ-7194
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
>
> Go to Accounting Manager --> Organization GL Settings 
> Click on Accounting --> Checks
> In Checks To Print click on button Print (PDF)
> PDF gets open in same window.
> To have the UI consistency it should be open in new window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-7195) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya closed OFBIZ-7195.
-
Resolution: Duplicate

Due to some internet issues or Jira response this duplicate ticket was created 
so closing it now.

> Checks --> Print (PDF) should be open in a new window
> -
>
> Key: OFBIZ-7195
> URL: https://issues.apache.org/jira/browse/OFBIZ-7195
> Project: OFBiz
>  Issue Type: Improvement
>  Components: accounting
>    Reporter: Harsh Vijaywargiya
>    Assignee: Harsh Vijaywargiya
>Priority: Minor
>
> Go to Accounting Manager --> Organization GL Settings 
> Click on Accounting --> Checks
> In Checks To Print click on button Print (PDF)
> PDF gets open in same window.
> To have the UI consistency it should be open in new window.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7195) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7195:
-

 Summary: Checks --> Print (PDF) should be open in a new window
 Key: OFBIZ-7195
 URL: https://issues.apache.org/jira/browse/OFBIZ-7195
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor


Go to Accounting Manager --> Organization GL Settings 
Click on Accounting --> Checks
In Checks To Print click on button Print (PDF)

PDF gets open in same window.

To have the UI consistency it should be open in new window.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7193) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7193:
-

 Summary: Checks --> Print (PDF) should be open in a new window
 Key: OFBIZ-7193
 URL: https://issues.apache.org/jira/browse/OFBIZ-7193
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor


Go to Accounting Manager --> Organization GL Settings 
Click on Accounting --> Checks
In Checks To Print click on button Print (PDF)

PDF gets open in same window.

To have the UI consistency it should be open in new window.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7194) Checks --> Print (PDF) should be open in a new window

2016-06-05 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7194:
-

 Summary: Checks --> Print (PDF) should be open in a new window
 Key: OFBIZ-7194
 URL: https://issues.apache.org/jira/browse/OFBIZ-7194
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Harsh Vijaywargiya
Assignee: Harsh Vijaywargiya
Priority: Minor


Go to Accounting Manager --> Organization GL Settings 
Click on Accounting --> Checks
In Checks To Print click on button Print (PDF)

PDF gets open in same window.

To have the UI consistency it should be open in new window.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (OFBIZ-6421) Unable to create New Communication from LEAD in SFA

2016-06-03 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya reassigned OFBIZ-6421:
-

Assignee: Harsh Vijaywargiya

> Unable to create New Communication from LEAD in SFA
> ---
>
> Key: OFBIZ-6421
> URL: https://issues.apache.org/jira/browse/OFBIZ-6421
> Project: OFBiz
>  Issue Type: Bug
>  Components: workeffort
>Affects Versions: 13.07.01
>Reporter: Kian Yen Mah
>    Assignee: Harsh Vijaywargiya
>
> Select Lead in SFA. Click COMMUNICATIONS. Click NEW COMMUNICATION. Click SAVE.
> The Following Errors Occurred:
> Exception thrown while performing entity find: [GenericDelegator.findOne] 
> Passed primary key is not a valid primary key: 
> [GenericEntity:CommunicationEventWorkEff][communicationEventId,10010(java.lang.String)]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5862) Have the ability to associate documents to a quote

2016-06-03 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314093#comment-15314093
 ] 

Harsh Vijaywargiya commented on OFBIZ-5862:
---

I think this ticket can be closed as same requirement is implemented in 
OFBIZ-6804

> Have the ability to associate documents to a quote
> --
>
> Key: OFBIZ-5862
> URL: https://issues.apache.org/jira/browse/OFBIZ-5862
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: content, quote,
>
> Currently the set of functionalities regarding quotes do not include the 
> means to associate documents (content like General Terms of Sale and Delivery 
> or product documentation) to a quote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-7082) FileNotFoundException while editing contact information

2016-05-20 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293395#comment-15293395
 ] 

Harsh Vijaywargiya commented on OFBIZ-7082:
---

To resolve this please rename EditcontaCtmech.ftl in party component to 
EditContactMech.ftl

> FileNotFoundException while editing contact information
> ---
>
> Key: OFBIZ-7082
> URL: https://issues.apache.org/jira/browse/OFBIZ-7082
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>    Reporter: Harsh Vijaywargiya
>Assignee: Amardeep Singh Jhajj
>
> Getting following error while trying to update any contact information
> Error rendering included template at location 
> [component://party/template/party/EditContactMech.ftl]: 
> java.io.FileNotFoundException: /home/common/ofbiz-



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7082) FileNotFoundException while editing contact information

2016-05-20 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7082:
-

 Summary: FileNotFoundException while editing contact information
 Key: OFBIZ-7082
 URL: https://issues.apache.org/jira/browse/OFBIZ-7082
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Trunk
Reporter: Harsh Vijaywargiya


Getting following error while trying to update any contact information

Error rendering included template at location 
[component://party/template/party/EditContactMech.ftl]: 
java.io.FileNotFoundException: /home/common/ofbiz-



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7055) RequestHandlerException on Find Query screen in Apache Solr Integration

2016-05-07 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7055:
-

 Summary: RequestHandlerException on Find Query screen in Apache 
Solr Integration
 Key: OFBIZ-7055
 URL: https://issues.apache.org/jira/browse/OFBIZ-7055
 Project: OFBiz
  Issue Type: Bug
  Components: specialpurpose/solr
Affects Versions: Trunk
Reporter: Harsh Vijaywargiya


RequestHandlerException on Find Query screen in Apache Solr Integration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-7054) Example -> PDF should be open in a new window

2016-05-07 Thread Harsh Vijaywargiya (JIRA)

Harsh Vijaywargiya created OFBIZ-7054:
-

 Summary: Example -> PDF should be open in a new window
 Key: OFBIZ-7054
 URL: https://issues.apache.org/jira/browse/OFBIZ-7054
 Project: OFBiz
  Issue Type: Improvement
  Components: specialpurpose/example
Affects Versions: Trunk
Reporter: Harsh Vijaywargiya
Priority: Minor


To have the consistency on all screens in addition to OFBIZ-7036 Example --> 
PDF should be open in a new window. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-3991) Order Manager / REQUEST /STATUS / STATUS_ID 2 ACCEPTED

2014-11-29 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228769#comment-14228769
 ] 

Harsh Vijaywargiya commented on OFBIZ-3991:
---

I could reproduce the same issue. If we do the correct email notification 
setting in general.properties then it works fine and we don't get this error. 
We can close this issue.

> Order Manager / REQUEST /STATUS / STATUS_ID 2 ACCEPTED
> --
>
> Key: OFBIZ-3991
> URL: https://issues.apache.org/jira/browse/OFBIZ-3991
> Project: OFBiz
>  Issue Type: Bug
>  Components: humanres, order
>Affects Versions: Release Branch 10.04
> Environment: MYSQL / OFBIZ 10.4
>Reporter: patrick LE BLAN
>Assignee: Ashish Vijaywargiya
>
> While trying to change a request to accepted in order to create a task  
> following problem occurs 
> The Following Errors Occurred:
> Error calling event: org.ofbiz.webapp.event.EventHandlerException: Service 
> invocation error (Could not commit transaction for service 
> [updateCustRequest] call: Roll back error, could not commit transaction, was 
> rolled back instead because of: Error in Service [sendMail]: [CON] Connection 
> error when sending message to [  m] from [] cc [null] bcc [null] 
> subject [OFBiz - Your Request is received: 'FORMAT_DATE' #CR10043 [To: , Cc: 
> null, Bcc: null]])



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-4482) findVisits request shows empty entry for user after logout

2014-11-29 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228671#comment-14228671
 ] 

Harsh Vijaywargiya commented on OFBIZ-4482:
---

In addition to Arun's comment we can see the different visitId in snapshot1 and 
snapshot2 i.e. 10091 when user is logged in and 10092 once user is logged out.

> findVisits request shows empty entry for user after logout
> --
>
> Key: OFBIZ-4482
> URL: https://issues.apache.org/jira/browse/OFBIZ-4482
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Wai
>Assignee: Ashish Vijaywargiya
>Priority: Minor
> Attachments: snapshot1.png, snapshot2.png, snapshot3.png
>
>
> When a user login, an entry is shown for the user in 
> https://localhost:8443/partymgr/control/findVisits.
> (refer to snapshot1.png)
> When the user logout, the same entry contains missing values for partyId, 
> userLoginId, New User, and Thru Date columns are empty.
> (refer to snapshot2.png)
> When the same user logs back in, those entries reappears.
> (refer to snapshot3.png)
> Ofbiz seem to be re-using the same visitorId and visitId after a logout.
> My expectation of how it works is that when a user logs out, the missing 
> entries should appear as it had been when the user was logged in and the Thru 
> Date should have be filled with the time of logout.
> When the same user login again, another entry should have been created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5546) RAW_MATERIAL return/RMA functionality not supported OOTB

2014-11-28 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228199#comment-14228199
 ] 

Harsh Vijaywargiya commented on OFBIZ-5546:
---

Created required data and attaching the patch file. Tested Return functionality 
for both Vendor and Customer returns.

> RAW_MATERIAL return/RMA functionality not supported OOTB
> 
>
> Key: OFBIZ-5546
> URL: https://issues.apache.org/jira/browse/OFBIZ-5546
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-5546.patch
>
>
> This error occurs when trying to create a return for a supplier RAW_MATERIAL 
> order item: "The following required parameter is missing: 
> [createReturnItem.returnItemTypeId]".  This occurs because there is no record 
> in the ReturnItemTypeMap entity for the RAW_MATERIAL.  A record should be 
> created in ReturnItemTypeMap for RAW_MATERIAL, VENDOR_RETURN, RET_MPROD_ITEM. 
>  RET_MPROD_ITEM needs to be added to the ReturnItemType entity also.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-5546) RAW_MATERIAL return/RMA functionality not supported OOTB

2014-11-28 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-5546:
--
Attachment: OFBIZ-5546.patch

> RAW_MATERIAL return/RMA functionality not supported OOTB
> 
>
> Key: OFBIZ-5546
> URL: https://issues.apache.org/jira/browse/OFBIZ-5546
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-5546.patch
>
>
> This error occurs when trying to create a return for a supplier RAW_MATERIAL 
> order item: "The following required parameter is missing: 
> [createReturnItem.returnItemTypeId]".  This occurs because there is no record 
> in the ReturnItemTypeMap entity for the RAW_MATERIAL.  A record should be 
> created in ReturnItemTypeMap for RAW_MATERIAL, VENDOR_RETURN, RET_MPROD_ITEM. 
>  RET_MPROD_ITEM needs to be added to the ReturnItemType entity also.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-3497) using date-time type="time" shouldn't display a textbox for a date

2014-11-27 Thread Harsh Vijaywargiya (JIRA)


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

Harsh Vijaywargiya updated OFBIZ-3497:
--
Attachment: training.png

> using date-time type="time" shouldn't display a textbox for a date
> --
>
> Key: OFBIZ-3497
> URL: https://issues.apache.org/jira/browse/OFBIZ-3497
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Erwan de FERRIERES
> Attachments: OFBIZ-3497.png, training.png
>
>
> When using a field like this :  input-method="time-dropdown"/>, a textbox is added at the beginning of the 
> field, but not needed. As we just want to select time, this textbox which is 
> usually for dates is not needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-3497) using date-time type="time" shouldn't display a textbox for a date

2014-11-27 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227486#comment-14227486
 ] 

Harsh Vijaywargiya commented on OFBIZ-3497:
---

This issue seems to be resolved now and can be closed. I edited the 
editTrainingCalendar form in file 
/applications/humanres/widget/forms/PersonTrainingForms.xml and tried 
 for From Date, Attaching 
the screenshot. 

> using date-time type="time" shouldn't display a textbox for a date
> --
>
> Key: OFBIZ-3497
> URL: https://issues.apache.org/jira/browse/OFBIZ-3497
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Trunk
>Reporter: Erwan de FERRIERES
> Attachments: OFBIZ-3497.png
>
>
> When using a field like this :  input-method="time-dropdown"/>, a textbox is added at the beginning of the 
> field, but not needed. As we just want to select time, this textbox which is 
> usually for dates is not needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-2509) partial select in simple methods does not decrypt encrypted fields

2014-11-26 Thread Harsh Vijaywargiya (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226070#comment-14226070
 ] 

Harsh Vijaywargiya commented on OFBIZ-2509:
---

I just verified the reported issues on latest trunk, and now it is working 
fine. We can close this issue.

> partial select in simple methods does not decrypt encrypted fields
> --
>
> Key: OFBIZ-2509
> URL: https://issues.apache.org/jira/browse/OFBIZ-2509
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Reporter: Chris Howe
>Assignee: Adam Heath
>Priority: Minor
>
> When using  in conjunction with entity-* in a simple method 
> encrypted field values are not decrypted.
> Try:
> 
>   
>   
> 
> 
> compared with:
> 
>   
> 
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

50 matches

Mail list logo