Petals CDK

A patch of this problem is available in the issue PETALSCDK-57

It is the case for all the JBI parameters if they are not trimmed at the CDK or component level...

I'm not sure because others parameters are not defined as string, but as integer, boolean, ... and the parser should return an explicit error if a provided value is invalid.

Hi guys,

Last year, I submitted a similar problem in the EJB BC.
See PETALSBCEJB-4 for more details, but it was a component parameter.

I think all the parameters values should be trimmed.
That would avoid lots of useless problems. That's what I do for all the component parameters in my components.

An other solution could be to use xml schema restrictions (like the one describe here : http://www.w3.org/TR/xmlschema-0/#CreatDt) to be able to detect problem at design time. And use regular expressions for "class names" that forbids white spaces and CR. But I'm not sure that IDE validators and jaxb validators support this type of restrictions...

Fix patch in the branch 3.1.X

Olivier, your proposal can be a solution if the validation used is able to detect such an error. I think that, in a user point of view, the user wants the best error message even with the solution. That's why I think a validation is sufficient instead of to trim each parameter value.
Perhaps the validation should be the solution to implement in trunk ?

To merge in trunk