JBoss AS 7 not accepting remote connections

For those who use JBoss AS 7 and want to connect to your application using the IP or server name from a computer in the intranet, you need to do this:
This is for Dev Environments only!
The answer is... Change the 127.0.0.1 (localhost) to 0.0.0.0 in standalone.xml
<interfaces> <interface name="management"> <inet-address value="${jboss.bind.address.management:0.0.0.0}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:0.0.0.0}"/> </interface> <!-- TODO - only show this if the jacorb subsystem is added --> <interface name="unsecure"> <!-- ~ Used for IIOP sockets in the standard configuration. ~ To secure JacORB you need to setup SSL --> <inet-address value="${jboss.bind.address.unsecure:0.0.0.0}"/> </interface> </interfaces>

Apex Component error: Element type "input" should be followed by either attribute specifications, ">" or "/>"

Not sure if you have faced this situation, but let's see what we're trying to accomplish.

Scenario Display 2 radio buttons, one unchecked and another one checked based on the value of a variable.

How was developed
For educational purposes I'll just show 1 radio button :) <input type="radio" name="payment_options" {!IF(that.cartBean.payInInstallments == true,'','checked')} > Pay full amount today </input>
Looks simple, however we got the weird error message listed as title of this post.

Solution
After thinking carefully and asking salesforce support, we end up with the same solution
<apex:outputPanel rendered="{!that.cartBean.PayInInstallments == false}"> <input type="radio" name="payment_options" checked="checked" /> Pay full amount today </apex:outputPanel> <apex:outputPanel rendered="{!that.cartBean.PayInInstallments == true}"> <input type="radio" name="payment_options"/> Pay full amount today </apex:outputPanel> In order to display 1 radio button only, we have to write code for 2 radio buttons!

I hope this saves you valuable time.

Invoke a SOAP API written in Salesforce using Axis

I had to consume an API written by someone else in Salesforce. I got the WSDL and the EndPoint.

Essentially what I had to do is to replace existing code I wrote a year ago to perform User Provisioning in Salesforce and rely on this API to perform that logic.

Now the interesting part is how to write my client, the obvious answer was to use WSDL2Java (Axis), because I don't want to write much code. And this is my final code: public void executeAccountUserProvisioningOnSalesforce(){ log.debug("Execute Account, Contact and User Provisioning (using single API on Salesforce) for "+this.kaptestRegistrationFields.getEmail()); com.sforce.soap.schemas._class.SSOprovisioningFunctionCall.Details details = null; this.login(); //Invoke Login //Create a sessionHeader object and set its sessioId property to sessionId SessionHeader sessionHeader = new SessionHeader(); sessionHeader.setSessionId(this.connection.getSessionHeader().getSessionId()); SSOprovisioningFunctionCallService service = new SSOprovisioningFunctionCallServiceLocator(); details = this.transformKaptestRegistrationFields(this.kaptestRegistrationFields); try { SSOprovisioningFunctionCallPortType port = service.getSSOprovisioningFunctionCall(new URL(provisioningEndPoint));//Use the service to get a stub which implements the SDI log.debug("Invoking "+provisioningEndPoint); ((Stub)port).setHeader("SessionHeader", "SessionHeader", sessionHeader); port.executeAccountUserProvisioning(details);//Invokes API } catch (Exception ex) { log.error("Error while invoking "+provisioningEndPoint+" for "+this.kaptestRegistrationFields.getEmail(),ex); } log.debug("Provisioning call to Salesforce completed for "+this.kaptestRegistrationFields.getEmail()); } .... private Boolean login() { Boolean success = false; try { ConnectorConfig config = new ConnectorConfig(); config.setUsername(username); config.setPassword(password); log.debug("AuthEndPoint: " + authEndPoint); config.setAuthEndpoint(authEndPoint); connection = new EnterpriseConnection(config); // Set the SOAP header to roll back the create unless // all contacts are successfully created. connection.setAllOrNoneHeader(true); printUserInfo(config); success = true; } catch (ConnectionException ce) { log.error("Error while executing login",ce); }catch (Exception ex) { log.error("Other Error occurred while executing login",ex); } return success; } This is a simple Cooking recipe with the exception of these lines: this.login(); //Invoke Login ... //Create a sessionHeader object and set its sessioId property to sessionId SessionHeader sessionHeader = new SessionHeader(); sessionHeader.setSessionId(this.connection.getSessionHeader().getSessionId()); ... ((Stub)port).setHeader("SessionHeader", "SessionHeader", sessionHeader); Things to keep in mind (otherwise you'll get "INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session"):

1. Open a session in Salesforce (that's how get permission to invoke the API)
2. Populate SessionHeader object (with Salesforce sessionId)
3. Set the Header to your Port before making your call

Querying a DATE field and a TIMESTAMP

When I was running a few reports, I faced a very interesting scenario.
(Because I'm lazy I wrote a Stored Proc with all my queries and used a scheduled Job to run it)

Anyway, the idea here is that I had to run my report for a certain window of time.
So I declared my start date and end date variables as DATE and wrote all my queries using: WHERE created_on between V_START_DATE AND V_END_DATE And when I ran for the first time my queries in the body of the Stored Proc I got a bunch of errors. Why???

After thinking seriously, that maybe I've lost my edge I just realized that in a few tables the created_on column was declared as DATE and in others as TIMESTAMP. Not the end of the world, I just decided to change the data type of my variables to TIMESTAMP and end of the story :)

Java Code Refactoring

I recently browsed again the excellent book Code Complete from Steve McConnell while in the middle of several Java code reviews. Although the book is nor specifically dedicated to Java code, I still found it quite useful and inspiring.

The chapter on refactoring in particular offers a very practical perspective that all programmer should have in mind when it comes to infuse a dose of evolution in the life cycle of their software.

What I found particularly valuable are the checklists that the author has put together: reasons to refactor, specific re-factorings (data level, statement level, routine-level, class-implementation, class-interface, system-level), refactoring safely, strategies, summary.

Since I do not have time to comment every item in these checklists, I decided to pick-up those that are not trivial or obvious and might bring the best return on your refactoring investment.

In a future post, I would like to illustrate some of these refactoring techniques with java code snippets, but that will be later :)

Checklist: Reasons to Refactor

• Code is duplicate
• A routine is too long
• A loop is too long or too deeply nested
• A class/interface/method has poor cohesion ⇐
• A class interface does not provide a consistent level of abstraction ⇐
• A parameter list has too many parameters ⇐
• Changes within a class tend to be compartmentalized
• Changes require parallel modifications to multiple classes ⇐
• Inheritance hierarchies have to be modified in parallel
• Related data items that are used together are not organized into classes ⇐
• A routine uses more features of another class than of its own class
• A primitive data type is overloaded
• A class doesn't do very much
• A chain of routines passes tramp data ⇐
• A middle man object isn't doing anything
• One class is overly intimate with another
• A routine has a poor name
• Data members are public
• A subclass uses only a small percentage of its parents' routines
• Comments are used to explain difficult code
• Global variables are used
• A routine uses setup code before a routine call or takedown code after a routine call
• A program contains code that seems like it might be needed someday

Checklist: Summary of Refactorings

• Data Level Refactoring
• Replace a magic number with a named constant ⇐
• Rename a variable with a clearer or more informative name
• Move an expression inline
• Replace an expression with a routine
• Introduce an intermediate variable
• Convert a multi-use variable to a multiple single-use variables ⇐
• Use a local variable for local purposes rather than a parameter
• Convert a data primitive to a class
• Convert a set of type codes to a class
• Convert a set of type codes to a class with subclasses
• Change an array to an object
• Encapsulate a collection ⇐
• Replace a traditional record with a data class
• Statement Level Refactorings
• Decompose a boolean expression
• Move a complex boolean expression into a well-named boolean function
• Consolidate fragments that are duplicated within different parts of a conditional
• Use break or return instead of a loop control variable
• Return as soon as you know the answer instead of assigning a return value within nested if-then-else statements
• Replace conditionals with polymorphism (especially repeated case statements) ⇐
• Create and use null objects instead of testing for null values
• Routine Level Refactorings
• Extract a routine
• Move a routine's code inline
• Convert a long routine to a class
• Substitute a simple algorithm for a complex algorithm
• Add a parameter
• Remove a parameter
• Separate query operations from modification operations
• Combine similar routines by parameterizing them
• Separate routines whose behavior depends on parameters passed in ⇐
• Pass a whole object rather than specific fields
• Pass specific fields rather than a whole object
• Encapsulate downcasting ⇐ 

Class Implementation Refactorings

• Change value objects to reference objects
• Change reference objects to value objects
• Replace virtual routines with data initialization
• Change member routine or data placement
• Extract specialized code into a subclass ⇐
• Combine similar code into a superclass
• Class Interface Refactorings
• Move a routine to another class
• Convert one class to two
• Eliminate a class
• Hide a delegate ⇐
• Replace inheritance with delegation
• Replace delegation with inheritance
• Remove a middle man ⇐
• Introduce a foreign routine
• Introduce a class extension
• Encapsulate an exposed member variable
• Remove Set() routines for fields that cannot be changed
• Hide routines that are not intended to be used outside the class
• Encapsulate unused routines ⇐
• Collapse a superclass and subclass if their implementations are very similar
• System Level Refactorings
• Duplicate data you can't control ⇐
• Change unidirectional class association to bidirectional class association
• Change bidirectional class association to unidirectional class association
• Provide a factory routine rather than a simple constructor
• Replace error codes with exceptions or vice versa

Memory Settings on WebMethods - Windows Installation as Service

According to SoftwareAG, if you want to modify the memory settings of your WebMethods Installation (IS - Integration Server) you have to do it in one place:

setenv.bat

set JAVA_MIN_MEM=1024M
set JAVA_MAX_MEM=2048M
set JAVA_MAX_PERM_SIZE=512M

I'm not saying this is wrong, because is not if you start your IS using command line by invoking startup.bat (X:\SoftwareAG\IntegrationServer\bin)

However for us mortals (muggles) who have our installation configured as a Windows Service I found this that my service is started by executing an EXE file (which uses a config file named wrapper.conf):
X:\SoftwareAG\profiles\IS\configuration\wrapper.conf

Inside that file you'll find all sort of properties but no matter how many changes you perform in this file, you won't see any change reflected (no mater how many times you restart your service), unless you have checked at the end of this file where there is a commented line (leave it commented, no need to change anything) which actually includes an additional file custom_wrapper.conf (aha! That's the right spot!)

Feel free to modify this entries (those are the values I set to my DEV environment):

wrapper.java.additional.7=-Xms2048M
wrapper.java.additional.8=-Xmx2048M
wrapper.java.additional.9=-XX:MaxPermSize=512M 

If you want to add an additional property to your JVM (since the last property ends in 17), I added an additional property 18:

wrapper.java.additional.18=-Dcom.sun.management.jmxremote.port=7007 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

Restart your IS Windows Service and you'll see your changes reflected.

How to configure webMethods JDBC Adapter to use Oracle RAC

If you have created a JDBC Adapter on WebMethods, it's a really straight forward process, but what happens when we have to connect to a Cluster

Try it and see what happens...

Now it's not that simple isn't?

Thankfully I have a workaround

1. Leave blank serverName, databaseName and portNumber fields.
2. In Other Properties enter your URL:

   url=jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)
   (ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521))
   (ADDRESS=(PROTOCOL=TCP)(HOST=host2) (PORT=1521))
   (CONNECT_DATA=(SERVICE_NAME=service)))

I hope this will help you.

Built-In Services For Connections - WebMethods

Integration Server provides built‐in services that enable you to programmatically control connections.b You can use them to enable and disable a connection, and to return usage statistics and the current state (Enabled or Disabled) and error status for a connection. These services are located in the WmART package, in the pub.art.connection folder.

There are two built‐in services, setAdapterServiceNodeConnection and setPollingNotificationNodeConnection, that enable you to change the connection associated with an adapter service or notification respectively.

This is going to help you a lot and save you so much time if you haven't worked with this tool before.

Max number of values in IN clause

Somebody asked me about this a few days ago, and this person (really sure of what he was talking about) told me: "You can only pass a limit of 200 items in a IN clause (during a DELETE)"

I'm not an Expert DBA (know it all), but I do remember that you can pass up to 1000 elements. And that was my counter argument to this guy (as always if you don't believe me double check with your best friend or test it
In the past it used to be 256 elements, but that was in Oracle 8.

Add Token Based Authentication on Spring Security

Problem I have an application which has already implemented Basic Authentication using Spring Security.
Now as part of a new requirement I have to enable a Token based authentication as well.
My first task was to updgrade to Spring 3.0.7 and to Spring Security 3.1.3 among other dependicies that needed an update as well.
After that, let's go to the meaty part of this implementation :)
While researching I couldn't find any example, only pieces, that's why I'm publishing and sharing my findings with all the community:

At least I knew that I had to implement another Authentication Provider (that's why I needed to Upgrade my App) and something to catch the event of login and tell Spring to perform another authentication (like a Filter, maybe?)

This is my implementation: Spring's config <security:http auto-config="true" access-denied-page="/login" authentication-manager-ref="defaultAuthenticationManager"> <security:intercept-url pattern="/login" access="IS_AUTHENTICATED_ANONYMOUSLY"/> <security:intercept-url pattern="/logout.do" access="IS_AUTHENTICATED_ANONYMOUSLY"/> <security:intercept-url pattern="/**/*.gif" access="IS_AUTHENTICATED_ANONYMOUSLY"/> <security:custom-filter ref="kaplanCustomOncePerRequestFilterFilter" before="PRE_AUTH_FILTER"/> <security:intercept-url pattern="/3.0/onlineprofile" access="ROLE_ktp_user"/> <security:intercept-url pattern="/**" access="ROLE_ktp_user, ROLE_System User"/> <security:form-login authentication-failure-url="/login" default-target-url="/3.0/services" login-page="/login" login-processing-url="/login.do"/> <security:logout logout-success-url="/login" logout-url="/logout.do"/> </security:http> <security:authentication-manager id="defaultAuthenticationManager" alias="authenticationManager"> <security:authentication-provider user-service-ref="kaplanUserDetailsService"> <security:password-encoder ref="kaplanPasswordEncoder"/> </security:authentication-provider> <security:authentication-provider user-service-ref="kaplanOAuth2UserDetailsService"/> </security:authentication-manager> ... <bean id="kaplanOAuth2UserDetailsService" class="kaplan.ktpa.core.auth.oauth2.KaplanOAuth2UserDetailsService"/> <bean id="kaplanCustomOncePerRequestFilterFilter" class="kaplan.ktpa.core.auth.filter.KaplanCustomOncePerRequestFilterFilter"> <property name="accessToken" value="Authentication"/><!-- We can set this in a property --> <property name="tokenValidator" ref="pingIdentityTokenValidator"/> </bean> <bean id="pingIdentityTokenValidator" class="kaplan.ktpa.core.auth.ping.PingIdentityTokenValidatorImpl"> <property name="clientId" value="${security.ping.clientid}"/> <property name="clientSecret" value="${security.ping.clientsecret}"/> <property name="pingUrl" value="${security.ping.url}"/> </bean>
PingIdentityTokenValidatorImpl (Validates Given token) public class PingIdentityTokenValidatorImpl implements TokenValidator{ private static final Logger log = Logger .getLogger(PingIdentityTokenValidatorImpl.class); public static final String PROFILE_ID = "profileId"; public static final String TOKEN_PREFIX = "Bearer "; private String pingUrl; private String clientId; private String clientSecret; public String validateToken(final String accessTokenParam) { log.debug("Token with prefix="+accessTokenParam); String accessToken = StringUtils.substringAfterLast(accessTokenParam, TOKEN_PREFIX); log.debug("Token="+accessToken); String postData = "grant_type=urn:pingidentity.com:oauth2:grant_type:validate_bearer&token=" + accessToken; String result = ""; URL url = null; String profileId = null; try { log.debug("Posting to "+pingUrl); url = new URL(pingUrl); String authInfo = clientId + ":" + clientSecret; log.debug("authInfo="+authInfo); byte[] authinfobytes = authInfo.getBytes(); authInfo = new String(Base64.encodeBase64(authinfobytes)); URLConnection conn = url.openConnection(); conn.setDoOutput(true); conn.setRequestProperty("Content-Type", "application/x-www-form-urlencoded"); conn.setRequestProperty("Authorization", "Basic " + authInfo); conn.setRequestProperty("Content-Length", String.valueOf(postData.length())); conn.setRequestProperty("grant_type", "urn:pingidentity.com:oauth2:grant_type:validate_bearer"); conn.setRequestProperty("token", accessToken); OutputStreamWriter outputStreamWriter = new OutputStreamWriter( conn.getOutputStream()); outputStreamWriter.write(postData); outputStreamWriter.flush(); BufferedReader bufferedReader = new BufferedReader(new InputStreamReader( conn.getInputStream())); StringBuilder stringBuilder = new StringBuilder(); String aux = ""; while ((aux = bufferedReader.readLine()) != null) { stringBuilder.append(aux); } result = stringBuilder.toString(); log.debug("result="+result); if (result.contains(PROFILE_ID)) { log.debug("result contains profileId"); profileId = StringUtils.substringBetween(result, "\""+PROFILE_ID+"\":\"","\"}}"); //profileId = result.substring(result.indexOf("\""+PROFILE_ID+"\":\"") + 13, result.length() - 3); } outputStreamWriter.close(); bufferedReader.close(); } catch (MalformedURLException e) { log.warn("MalformedURLException while validating Token (noPrefix)=" + accessToken, e); } catch (IOException e) { log.warn("IOException while validating Token (noPrefix)=" + accessToken, e); } catch (Exception ex){ log.error("Error while validating Token (noPrefix)=" + accessToken, ex); } log.debug("profileId="+profileId); return profileId; } }
KaplanOAuth2UserDetailsService (Performs Authentication, generates user following spring security standards) public class KaplanOAuth2UserDetailsService implements UserDetailsService { private static final Logger log = Logger .getLogger(KaplanOAuth2UserDetailsService.class); @Override public UserDetails loadUserByUsername(String profileId) throws UsernameNotFoundException { log.debug("Loading profileId="+profileId); KaplanUser kaplanUser = new KaplanUser(profileId, profileId, true, true, true, true, this.grantedAuthorities(), 1L); log.debug("Returning kaplanUser="+kaplanUser); return kaplanUser; } private List<GrantedAuthority> grantedAuthorities() { List<GrantedAuthority> authorities = new ArrayList<GrantedAuthority>(); authorities.add(new SimpleGrantedAuthority("ROLE_"+ KaplanCustomAuthProcessingFilter.OAUTH_ROLE)); return authorities; } }
KaplanCustomOncePerRequestFilterFilter (This filter does the trick) Just add it to your security configuration in the right place of the chain of execution and you're set public class KaplanCustomOncePerRequestFilterFilter extends OncePerRequestFilter { private static final Logger log = Logger .getLogger(KaplanCustomOncePerRequestFilterFilter.class); private String accessToken; //Now looks like a RequestHeaderAuthFilter @Autowired private KaplanOAuth2UserDetailsService authUserDetailsService; @Autowired private TokenValidator tokenValidator; @Override protected void doFilterInternal(HttpServletRequest request, HttpServletResponse response, FilterChain filterChain) throws ServletException, IOException { String authToken = null; UsernamePasswordAuthenticationToken authRequest = null; Authentication authentication = SecurityContextHolder.getContext() .getAuthentication(); if (authentication != null) { authToken = authentication.getName(); } if (StringUtils.isNotBlank(request.getHeader(this.accessToken))) { authToken = request.getHeader(this.accessToken); String profileId = this.tokenValidator.validateToken(authToken); if (profileId == null) { throw new VerificationFailedException("Unable to authenticate using token " + authToken); } List<GrantedAuthority> authorities = new ArrayList<GrantedAuthority>(); authorities.add(new SimpleGrantedAuthority("ROLE_"+KaplanCustomAuthProcessingFilter.OAUTH_ROLE)); authRequest = new UsernamePasswordAuthenticationToken(profileId, profileId, authorities); HttpSession session = request.getSession(false); if (session != null) { request.getSession().setAttribute(KaplanCustomAuthProcessingFilter.SPRING_SECURITY_LAST_USERNAME, TextEscapeUtils.escapeEntities(authToken)); request.getSession().setAttribute(KaplanCustomAuthProcessingFilter.SPRING_SECURITY_SAVED_REQUEST, new DefaultSavedRequest(request, new PortResolverImpl())); } Object details = authUserDetailsService.loadUserByUsername(profileId); authRequest.setDetails(details); SecurityContextHolder.getContext().setAuthentication(authRequest); } filterChain.doFilter(request, response); } Although, my original approach was to extend from AbstractAuthenticationProcessingFilter, however I saw it being invoked multiple times per request (it didn't bother me), but that wasn't good enough for me, also it was more complex :P public class KaplanCustomAuthProcessingFilter extends AbstractAuthenticationProcessingFilter { private static final Logger log = Logger .getLogger(KaplanCustomAuthProcessingFilter.class); private static final String DEFAULT_FILTER_PROCESSES_URL = "/login"; private static final String POST = "POST"; public static final String OAUTH_ROLE = "ktp_user"; public static final String SPRING_SECURITY_LAST_USERNAME = "SPRING_SECURITY_LAST_USERNAME"; public static final String SPRING_SECURITY_SAVED_REQUEST = "SPRING_SECURITY_SAVED_REQUEST"; private String accessToken; //Now looks like a RequestHeaderAuthFilter @Autowired private AuthenticationManager authenticationManager; @Autowired private KaplanOAuth2UserDetailsService authUserDetailsService; @Autowired private TokenValidator tokenValidator; public KaplanCustomAuthProcessingFilter() { super(DEFAULT_FILTER_PROCESSES_URL); super.setAuthenticationManager(authenticationManager); super.setAuthenticationDetailsSource(authenticationDetailsSource); this.setTokenValidator(tokenValidator); } public void doFilter(HttpServletRequest request, HttpServletResponse response, FilterChain filterChain) throws IOException, ServletException { if (request.getMethod().equals(POST)) { log.debug("doFilter Method POST"); super.doFilter(request, response, filterChain); } else { log.debug("doFilter Method GET OR OTHER - not POST"); filterChain.doFilter(request, response); } } @Override protected boolean requiresAuthentication(final HttpServletRequest request, final HttpServletResponse response) { boolean result = false; if (StringUtils.isNotBlank(request.getHeader(this.accessToken))) { result = true; } log.debug("requiresAuthentication? "+result); return result; } @Override protected void successfulAuthentication(HttpServletRequest request, HttpServletResponse response, FilterChain chain, Authentication authResult) throws IOException, ServletException { log.debug("Authentication was successful"); super.successfulAuthentication(request, response, chain, authResult); } @Override public Authentication attemptAuthentication(HttpServletRequest request, HttpServletResponse response) throws AuthenticationException, IOException, ServletException { String authToken = null; UsernamePasswordAuthenticationToken authRequest = null; Authentication authentication = SecurityContextHolder.getContext() .getAuthentication(); if (authentication != null) { authToken = authentication.getName(); } if (StringUtils.isNotBlank(request.getHeader(this.accessToken))) { authToken = request.getHeader(this.accessToken); String profileId = this.tokenValidator.validateToken(authToken); if (profileId == null) { throw new VerificationFailedException("Unable to authenticate using token " + authToken); } List<GrantedAuthority> authorities = new ArrayList<GrantedAuthority>(); authorities.add(new SimpleGrantedAuthority("ROLE_"+OAUTH_ROLE)); authRequest = new UsernamePasswordAuthenticationToken(profileId, profileId, authorities); HttpSession session = request.getSession(false); if (session != null || getAllowSessionCreation()) { request.getSession().setAttribute(SPRING_SECURITY_LAST_USERNAME, TextEscapeUtils.escapeEntities(authToken)); request.getSession().setAttribute(SPRING_SECURITY_SAVED_REQUEST, new DefaultSavedRequest(request, new PortResolverImpl())); } Object details = authUserDetailsService.loadUserByUsername(profileId); authRequest.setDetails(details); return authRequest; } else throw new VerificationFailedException("Unable to authenticate; missing token value"); } }

Previously initiated loading for a different type with name "javax/management/MBeanServer"

When I was doing a migration / upgrade to Spring 3.1, I faced a really weird Error.

My App was using Jetty to run deploy my WAR file.


Short story / Long Story

Although I was not using MX4J library in my project, I remembered that:
"Jetty defaults to overriding the normal J2SE class loader delegation model  (which calls for delegating to the parent)."

Therefore, this could be fixed by using this System Property:

-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true

This is how you should do it in your pom:
<project> ... <plugins> ... <plugin> <groupid>org.mortbay.jetty</groupId> <artifactid>maven-jetty-plugin</artifactId> <configuration> ... <systemproperties> <systemproperty> <name>org.mortbay.jetty.webapp.parentLoaderPriority</name> <value>true</value> </systemProperty> ... </systemProperties> </configuration> </plugin> </plugins> </project>

And that error will go away.

JSONProvider builds wrong String

Looking at my backlog I found a very interesting ticket:

As a consumer of JSON web services, I would like the services to render fields with consistent types regardless of the content. When postal codes begin with zero, they are rendered as strings. When they begin with a non-zero character, they are rendered as numbers. This makes handling the JSON responses very cumbersome and causes hard to track down bugs in our code. 

It would be better if the conversion checked the type in the xsd (in the case of postal codes, string) and rendered it accordingly. 

Weird, isn't it? Then I realize, I wasn't the only one with this issue, a found a few other clueless developers with the same problem (look here and here), so that, I wasn't alone.

But so far no one had an answer, until I checked the code of my JSONProvider, this one: org.apache.cxf.jaxrs.provider.JSONProvider

My conclusion was simple, depending on the value of the string passed to the Converter, it will be casted to Boolean, String or Number.

There are 2 choices: Create my own custom JSONProvider extending from the original (and try to fix the world) or implement another which really worked as expected.

In a few words, I chose JacksonJsonProvider, however I had to customize it a little bit, because I needed to fix the issue and not create a new one (i needed the same output), and so far this is the result:

This is the original output { "postalCode": [ { "activeFlag": true, "areaCode": 603, "code": "03033", "createdOn": "2001-12-18", "isoCodeAlpha2": "US", "isoCodeAlpha3": "USA", "isoCodeNumeric": 840, "kbsPostalCodeId": 10998, "latitude": 42.740602, "longitude": -71.676612, "modifiedOn": "2006-12-08" }, { "activeFlag": true, "areaCode": 412, "code": 15102, "createdOn": "2001-12-18", "isoCodeAlpha2": "US", "isoCodeAlpha3": "USA", "isoCodeNumeric": 840, "kbsPostalCodeId": 15893, "latitude": 40.323747, "longitude": -80.037982, "modifiedOn": "2006-12-08" } ] }

This is my implementation public class JacksonJsonProvider extends org.codehaus.jackson.jaxrs.JacksonJsonProvider { private static final Logger log = Logger.getLogger(JacksonJsonProvider.class); @Override public boolean isWriteable(Class<?> type, Type genericType, Annotation[] annotations, MediaType mediaType) { boolean result = false; log.debug("Is Writeable? type="+type+", genericType="+genericType+", annotations="+annotations+", mediaType="+mediaType); result = super.isWriteable(type, genericType, annotations, mediaType); log.debug("Result="+result); if (String.class.equals(type)) { //pass strings as-is, they are most likely cached JSON responses return false; } else { return result;//return super.isWriteable(type, genericType, annotations, mediaType); } } public JacksonJsonProvider() { super(); ObjectMapper objectMapper = new ObjectMapper(); final Annotations[] BASIC_ANNOTATIONS = {Annotations.JACKSON, Annotations.JAXB}; objectMapper.configure(SerializationConfig.Feature.AUTO_DETECT_FIELDS, true); objectMapper.configure(SerializationConfig.Feature.INDENT_OUTPUT, true); objectMapper.configure(SerializationConfig.Feature.SORT_PROPERTIES_ALPHABETICALLY, true); objectMapper.configure(SerializationConfig.Feature.USE_ANNOTATIONS, true); objectMapper.configure(SerializationConfig.Feature.WRAP_ROOT_VALUE, true); super.setMapper(objectMapper); super.setAnnotationsToUse(BASIC_ANNOTATIONS); } }
And my new output { "ArrayList": [ { "activeFlag": true, "areaCode": "603", "code": "03033", "createdOn": "2001-12-18", "isoCodeAlpha2": "US", "isoCodeAlpha3": "USA", "isoCodeNumeric": 840, "kaplanPremierEligibleFlag": false, "kbsPostalCodeId": 10998, "latitude": 42.740602, "longitude": -71.676612, "modifiedOn": "2006-12-08" }, { "activeFlag": true, "areaCode": "412", "code": "15102", "createdOn": "2001-12-18", "isoCodeAlpha2": "US", "isoCodeAlpha3": "USA", "isoCodeNumeric": 840, "kaplanPremierEligibleFlag": true, "kbsPostalCodeId": 15893, "latitude": 40.323747, "longitude": -80.037982, "modifiedOn": "2006-12-08" } ] } I still have something to fix-customize because that "ArrayList" looks ugly though, but code and areCode now make sense, because they match my XSD and Pojo as well.