• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JSP-"page" directive is a response header?

 
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi folks,
i was wondering if you can clarify on this fact...i mean,i assume "page" directive is for page attributes to be identified and set by the Server. So, it's more of a META info. But is it coming in Http response as header information???
[ January 11, 2007: Message edited by: Bear Bibeault ]
 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
No, it is not. It's merely holding some attributes the servlet container uses to process the page. But those aren't added as header information.
 
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Page attributes dont go as header but they appear in the generated servlet for example <@page import= appears as the import statements in the beginning of the generated servlet.
 
Subhadip Chatterjee
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That's true, bro...i also knew that, but what happened is whenever i am deploying my application into an app. server, it's firewall/proxy somehow manages to recognize the "page" info from the JSPs as HTTP response header. Hence if in JSP, the "page" attributes are spread in more than one line, the Application portal is throwing error, that WAS 5.0.x understands that as "multiline HTTP response headers" and thrwoing out "internal server error". I understood this, after i rewrite the "page" attributes in one line.

If you guys have come across such a dumb scenario, please feed me on that.
 
Sheriff
Posts: 13411
Firefox Browser VI Editor Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Unless something is really wrong, the page attribute should never be part of your output.
Are you saying that the JSP source is being returned when you make a request?
 
Subhadip Chatterjee
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ben,
i don't really know, 'cauz the Application is getting deployed in a diffrent location, and they have a App server hosting a B2B portal. Through this portal, whenever they are trying to access such kinda pages (JSP with "page" dierctive-multiline), they are ,getting "Internal server errors". And when i was doing a Trial-error method, i found this "page" directive stuff is the reason for that. It really doesn't make any sense, but still as far as the Application is concerned, it's working now. What can i say to that?Strange, man.
[ January 11, 2007: Message edited by: Subhadip Chatterjee ]
 
This guy is skipping without a rope. At least, that's what this tiny ad said:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic