Dec
16
answered Running a jar produce from gradle build
Dec
14
answered Invalid source release: 1.8 on jenkins in SBT
Nov
30
awarded Supporter
Nov
29
awarded Custodian
Nov
29
reviewed Approve suggested edit on Curtain to hide storage under stairs
Nov
29
asked Curtain to hide storage under stairs
Nov
25
answered Java 7 -> Java 8: AES Causes exception: "BadPaddingException: Given final block not properly padded" in conjunction with BufferedReader & ZipStreams
Nov
20
awarded Nice Answer
Nov
12
revised Difference between servlet and web service
added 8 characters in body
Nov
4
answered javax.net.ssl.SSLException while calling a webservice in Soap UI through HTTPS
Oct
27
comment Do I need to enable canonicalization when using OWASP ESAPI?
"We are not encoding output given that after the input validation, data becomes trusted." noooooo!!! You must always escape output. The source maybe somewhere other than the input. This is as much about correctness as security
Oct
10
awarded Necromancer
Sep
30
awarded Explainer
Sep
29
comment SOAP WS-Security header UsernameToken is element tenant valid?
@c0dev look for xs:any type elements
Sep
29
comment SOAP WS-Security header UsernameToken is element tenant valid?
Doesn't look like it from the schema.
Sep
29
answered SOAP WS-Security header UsernameToken is element tenant valid?
Sep
24
comment Select file encoding in OutputStreamWriter
@Michael no. One of the 8-bit mappings might work (non-unicode), but why are you using a Writer to write binary data?
Sep
23
comment Spring - Autowire fails when adding an aspect-backed annotation to overridden method
@hoodieman I take it back - if your aspect does try/catch too, then it's better than a plain method call. Personally, I prefer a single fault barrier (see oracle.com/technetwork/java/effective-exceptions-092345.html) to ensure uncaught exceptions are logged exactly once, but your solution sounds good too.
Sep
22
answered Spring - Autowire fails when adding an aspect-backed annotation to overridden method
Sep
18
comment Null pointer exception only on application startup org.eclipse.persistence.jaxb.JAXBMarshaller.marshal
You could add some kind of initialization listener. The problem should only occur for the first user to hit the application, not once per user. (Of course, my answer might turn out not to be relevant)
1 2 3 4 5