cancel
Showing results for 
Search instead for 
Did you mean: 

Parser error because filename too long > 256 chars

Former Member
0 Kudos

Hi there,

after migrating from Netweaver 7.02 to 7.40 we encountered the following:
From an external CMS we deploy content to the Portal as JSPs. In the Portal they are parsed and compiled. The filename of the generated .Java and .class files is constructed from the whole file-path in the root directory of the web application plus the instance number of the portal instance plus 2 timestamps. all that is created by the Portal JSP engine. The second timestamp is new since 7.30 and now we found that in some cases the constructed file is > 256 characters and the jsp engine refuses the parsing because of that . any ideas how to solve such a problem ?    

Greetings

Walter

Accepted Solutions (0)

Answers (1)

Answers (1)

dror_last
Active Participant
0 Kudos

Hi Walter,

I did not find any solution for that.

Between 7.02 and 7.3x versions the Portal started to use the JSP Parser & Compiler of the J2EE engine and thus there is the incompatibility of the way it works compared to how it was in older versions.

The solution will be to control the file size by reducing the jsp file names and paths inside the application. You might need to adjust the portalapp.xml and relevant include of JSP resources in the code.

Best Regards,

Dror.