Skip to main content

Repeatitive process in Servlet

Hishashiburi neh.
It’s been a long time before I post this solution.Actually I got a lot of problems and solutions but I didn’t have time to post it in my blog.So unlucky!
But right now I just steal some time to update and post this entry right after I got the solution. It’s been three days I faced this problem. It’s challenge my ability as programmer because as normal programmer, we will feel strong if our code works, is not, I feel that I am not good programmer at all,I should never be born as a programmer.
Problem: My servlet is keep repeating implement some code once you submit form from jsp page.I think it should not repeat if we don’t want to.

Example

public class PlacementServlet extends HttpServlet {
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
try{
String mode=request.getParameter("mode");
System.out.println("MODE ------------------------------>"+mode);
if(mode.equals("i can change my life ")){
//do something for example insert into databases
}
else {
System.out.println(Bye- bye)
}
//more codes
Placement. jsp sample code

<script>
function doSubmit(){
var frm=document.placement
frm.mode.value="i can change my life";
frm.action = "PlacementServlet";
frm.submit();}
</script>
<form name="placement">
<input name="btnsave" type="submit" class="button" id="btnsave" value="SAVE" onclick="javascript:doSubmit()">
</form>

So when I clicked SAVE button, the output in my NetBeans produce :
MODE ------------------------------> i can change my life
MODE ------------------------------> i can change my life

Which if I do code that inserting to database; it will insert two times and prompt error violent to primary key. I already get sick with the problem and modify almost entire coding until I got to see

<input name="btnsave" type="submit" class="button" id="btnsave" value="SAVE" onclick="javascript:doSubmit()">
I change it to type="button" , and now the stupid repeatiting thing stop.I thinks it happen because it implement two command, first submit from javascript (doSubmit()) and then submit from the button. But that’s only what I think.
So case is closed, right know I need to rewrite back the code that I modified due to my stupidiness.

Comments

Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {