Skip to main content
T
tfritsch4-Participant
4-Participant
February 5, 2015
Question

Blank JSP Page on 10.2M020 after applying Customization

  • February 5, 2015
  • 6 replies
  • 1816 views

We just trying an upgrade from 10.1 M030 to 10.2M020 on atestenvironnement (with all the process recommanded by ptc : Install new version 10.2, datapump Oracle database, export/import Ldif, Then following the pre and post install and upgrademanager) I had some troubles during the upgrade but all resolved by CS on ptc website. Following this, I have a 10.2M20 OOFT but with our data ( metadata,WTdocument,EPMDoc, Parts or Softypes.. who are in database and it works) After that we apply our customisation (the same we use in 10.1M030) and after a SM restart, All the JSP page are blank. If Only customised JSP page where blank we undestand but here, many standard pages not customised all blank like Clipboard, preference, new problem report or new part. we try the classic ant command likeant -f tools.xml customer_build;ant -f jsfrag_combine.xml;ant -f jar.xml under WT_HOME/bin directory but nothing doing. Is someone has an idea or already has the trouble. Last Thing, We don't have any errors under windchill or tomcat logs...


6 replies

D
ddemay1-Visitor
1-Visitor
February 5, 2015
Are you allowed to share customized code? The exception may be getting
caught and not rethrown or printed to logs. Does it follow MVC guidelines
and is any of the customization using JavaScript?
T
tfritsch4-ParticipantAuthor
4-Participant
February 5, 2015

Yes, We use JavaScript but on standard page, there is Java Scripts and it doesn't work too

D
ddemay1-Visitor
1-Visitor
February 5, 2015
Sounds like a JavasScript bug. You can use Firebug for Firefox or F12 in
Internet Explorer to view console. Also read about debug versions of major
scripts in customizers guide. You can also use Fiddler to monitor HTTP
requests and responses.
T
tfritsch4-ParticipantAuthor
4-Participant
February 6, 2015

We think about it too but in the preference page for example, we didn't touch anything and it didn't work

S
sauls1-Visitor
1-Visitor
February 6, 2015

Did you check your Locale setings? are they en_US ?

T
tfritsch4-ParticipantAuthor
4-Participant
February 6, 2015

Sound like good David. it is effectively Java Script trouble. After a detailed analyse of ours files, we have a size and modified date difference between the Windchill-all.js from 10.2 OOTB and this deployed by our system.


We test with original file and All is good.



Thanks a lot. We are gooing to check what we modified on it .


(Windhill-all.js under/ptc/wt/windchill_standard/codebase/netmarkets/javascript/util)

Terms & ConditionsCookie settingsAccessibility statement