Recent migration from old glassfish to wildfly...
54 views
Skip to first unread message
Karl Krasnowsky
Sep 4, 2021, 12:08:30 PM9/4/21
to WildFly
Good morning,
I've run into an "interesting" issue after we upgraded and moved our jsf web application suite over to wildfly (currently v 20.0.1)
One of the major applications in this suite provides forms to enter formatted text in to textarea inputs, e.g., line feeds, and we've noticed that this data is now storing these as dos formatted line endings (\r\n) as opposed to unix (\n).
This has posed some edge case issues with one of our client apps that depend on this data downstream and we now have to do some backflips to account for this dos line ending format. I'd rather change this at the source rather than hoist the fix on the client applications.
Both this wildfly and prior glassfish 4 server is hosted on a windows system, but with the apps on glassfish these line endings were always in unix format (they were running this way for a L O N G time).
I don't believe there was any special configuration we did to force this behavior on glassfish, and I assume wildfly is just inheriting this behavior based on the hosted OS ?
Is there a method for turning this behavior off and force it to use unix format?
regards.
Jaikiran Pai
Sep 8, 2021, 6:06:26 AM9/8/21
to wil...@googlegroups.com
Hello Karl,
On 04/09/21 9:38 pm, Karl Krasnowsky wrote:
> Good morning,
> I've run into an "interesting" issue after we upgraded and moved our jsf
> web application suite over to wildfly (currently v 20.0.1)
> One of the major applications in this suite provides forms to enter
> formatted text in to textarea inputs, e.g., line feeds, and we've noticed
> that this data is now storing these as dos formatted line endings (\r\n) as
> opposed to unix (\n).
As far as I know, there isn't any configurable option to change this in
WildFly. Plus, it does look like WildFly is doing the right thing by
using the system's line separator. In any case, it's difficult to guess
which area/layer of the application server (or even the client) needs to
be analyzed, without knowing what kind of technologies are in use in
this application (things like servlets? jsps? or something else).
-Jaikiran
On 04/09/21 9:38 pm, Karl Krasnowsky wrote:
> Good morning,
> I've run into an "interesting" issue after we upgraded and moved our jsf
> web application suite over to wildfly (currently v 20.0.1)
> One of the major applications in this suite provides forms to enter
> formatted text in to textarea inputs, e.g., line feeds, and we've noticed
> that this data is now storing these as dos formatted line endings (\r\n) as
> opposed to unix (\n).
WildFly. Plus, it does look like WildFly is doing the right thing by
using the system's line separator. In any case, it's difficult to guess
which area/layer of the application server (or even the client) needs to
be analyzed, without knowing what kind of technologies are in use in
this application (things like servlets? jsps? or something else).
-Jaikiran
Reply all
Reply to author
Forward
0 new messages