java - Is toResponse from ExceptionMapper thread safe? -

-

i use resteasy in application , have simple implementation of toresponse method exceptionmapper interface.

my question is: method have problems in environment massive amount of requests happening(many requests cause exception thrown)? have thread safety?

i must admit still don't understand question fully.

i used use exception response translation way: define exception class extends javax.ws.rs.webapplicationexception. in constructor of exception class call super constructor appropriate params, e.g. super(response.status(404).entity(errormessage).build())

what nice can use dto entity , gets translated.

note don't use reasteasy. use jersey jackson.

so in business logic throw exception, it's handled jaxrs , translated response. there's no place thread-unsafety ;)


Comments

Post a Comment

Popular posts from this blog

c# - ItextSharp font color issue in ver 5.5.4+ -

-
Image
i have code creates red "stamp" using red font color: string stampdate = datetime.now.tostring("mm/dd/yyyy"); string fontpath = server.mappath("/assets/fonts"); string origfile = server.mappath("/test.pdf"); const int opacitypercent = 80; const float pdfpaidfontsize = 28; const float pdfcopyx = 170; const float pdfpaidx = 385; const float pdfy = 20; const float pdfdatexoffset = 7; const float pdfdateyoffset = 12; const float pdfdatefontsize = 10; const string paidstamptxt = "paid"; const string copystamptxt = "copy"; const string arialfilename = "arialbd.ttf"; pdfstamper stamper = null; pdfreader reader = null; pdfreader.unethicalreading = true; memorystream streampdf; try { reader = new pdfreader(origfile); streampdf = new memorystream(); stamper = new pdfstamper(reader, streampdf); (int = 1; <= r...
Read more

jquery - Multiple issues with pushstate: history, loading, calling functions -

-
i have script pulling data via ajax/pushstate; works relatively well, there issues i'm running into. first , foremost, here code i'm using: function goto(href) { $.ajax({ url: href, success: function(data) { $('#wrapper').fadeout('fast', function(){ $(this).html(data).fadeto('fast', 1); $(".scroll").nicescroll({cursorcolor:"#f33d39", cursorwidth: "10px", cursorborder: "none", cursorborderradius: "0px", fixed: true}); }); // update page title var title = $('#page-right').find('h1').text(); $('head').find('title').text(title); } }); } if (typeof history.pushstate !== "undefined") { var historycount = 0; $('a[href*="rage.rage-wrestling.com"]').live('click',function(){ var href = $(this).attr('h...
Read more

ios - retrievePeripherals deprecated in IOS7 how to substitude it with retrievePeripheralsWithIdentifiers -

-
i using "[self.manager retrieveperipherals:[nsarray arraywithobject:(id)aperipheral.uuid]];” works fine deprecated in ios7. found have use “ retrieveperipheralswithidentifiers ” instead. can not figure out right syntax new function. can please translate "[self.manager retrieveperipherals:[nsarray arraywithobject:(id)aperipheral.uuid]];” to new function “retrieveperipheralswithidentifiers”. // invoked when central discovers heart rate peripheral while scanning. - (void) centralmanager:(cbcentralmanager *)central diddiscoverperipheral:(cbperipheral *)aperipheral advertisementdata:(nsdictionary *)advertisementdata rssi:(nsnumber *)rssi { nsmutablearray *peripherals = [self mutablearrayvalueforkey:@"heartratemonitors"]; if(![self.heartratemonitors containsobject:aperipheral]) [peripherals addobject:aperipheral]; // retrieve known devices [self.manager retrieveperipherals:[nsarray arraywithobject:(id)aperipheral.uuid]]; } ...
Read more