Bpm4Struts Cartridge

Page Variables

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not an issue
  • Affects Version/s: 3.1M1
  • Fix Version/s: 3.1-RC1
  • Component/s: None
  • Description:
    Hide
    Since switching to 3.1 I have noticed problems with my page variables. I think I figured out why.

    The new version generates page variables with a <div id="PageVariables"> in the xxx-vars.jspf
    the old version did not have this. After removing the the <div tag it works again. I'm pretty sure it shouldn't be there, but if it is supposed to be, let me know how to make the page variables work again.

    Thanks
    Show
    Since switching to 3.1 I have noticed problems with my page variables. I think I figured out why. The new version generates page variables with a <div id="PageVariables"> in the xxx-vars.jspf the old version did not have this. After removing the the <div tag it works again. I'm pretty sure it shouldn't be there, but if it is supposed to be, let me know how to make the page variables work again. Thanks
  • Environment:
    Windows XP Pro, JDK 1.5 Tomcat 5.5.9, ant 1.65

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wouter Zoons added a comment - 11/Aug/05 8:18 AM
what do you mean when you say it doesn't work ? the fact there is a <div> layer around them doesn't change anything, right ?
Show
Wouter Zoons added a comment - 11/Aug/05 8:18 AM what do you mean when you say it doesn't work ? the fact there is a <div> layer around them doesn't change anything, right ?
Hide
Permalink
Wouter Zoons added a comment - 11/Aug/05 11:35 AM
the <div> has been placed there on user request, someone wanted to have those page variables under DHTML control
Show
Wouter Zoons added a comment - 11/Aug/05 11:35 AM the <div> has been placed there on user request, someone wanted to have those page variables under DHTML control
Hide
Permalink
Bobby Peterson added a comment - 11/Aug/05 12:01 PM
Sorry,

I mean that in the JSP when I try to access those variables set inside the <div tag they are null. When I remove the div tag they are not null. So I think it is changing something.
Show
Bobby Peterson added a comment - 11/Aug/05 12:01 PM Sorry, I mean that in the JSP when I try to access those variables set inside the <div tag they are null. When I remove the div tag they are not null. So I think it is changing something.
Hide
Permalink
Wouter Zoons added a comment - 11/Aug/05 5:33 PM
can you let me know how to reproduce this ? it seems VERY strange to me that HTML code is interfering with server-side scoped attributes
Show
Wouter Zoons added a comment - 11/Aug/05 5:33 PM can you let me know how to reproduce this ? it seems VERY strange to me that HTML code is interfering with server-side scoped attributes
Hide
Permalink
Wouter Zoons added a comment - 12/Aug/05 10:57 PM
hi Bobby, I will be closing this issue this weekend unless you let me know how to reproduce it, I can't get that error you're describing
Show
Wouter Zoons added a comment - 12/Aug/05 10:57 PM hi Bobby, I will be closing this issue this weekend unless you let me know how to reproduce it, I can't get that error you're describing
Hide
Permalink
Bobby Peterson added a comment - 15/Aug/05 12:49 PM
I apologize for not getting back to you quicker on this. I spent some time trying to track this down, the code that is currently generated from 3.1 works and I could not reproduce the error with it. But we have a lot of code that was generated with 3.0 and has been modified. Sense we don't want to loose those modification we have old files trying to work with new files. In a few cases where I think we might have made bad assumptions in our code variables that were available in the request are no longer in the request but are accessible as page variables. We have changed our code and things seem to work, sorry for the confusion. The change from inserting JSPs to including JSPFs has made it hard to make changes to the model and have them take effect.
Show
Bobby Peterson added a comment - 15/Aug/05 12:49 PM I apologize for not getting back to you quicker on this. I spent some time trying to track this down, the code that is currently generated from 3.1 works and I could not reproduce the error with it. But we have a lot of code that was generated with 3.0 and has been modified. Sense we don't want to loose those modification we have old files trying to work with new files. In a few cases where I think we might have made bad assumptions in our code variables that were available in the request are no longer in the request but are accessible as page variables. We have changed our code and things seem to work, sorry for the confusion. The change from inserting JSPs to including JSPFs has made it hard to make changes to the model and have them take effect.
Hide
Permalink
Wouter Zoons added a comment - 15/Aug/05 1:04 PM
okay, thanks for letting me know .. I'll close this issue
Show
Wouter Zoons added a comment - 15/Aug/05 1:04 PM okay, thanks for letting me know .. I'll close this issue

People

Dates

  • Created:
    10/Aug/05 7:36 PM
    Updated:
    15/Aug/05 1:04 PM
    Resolved:
    15/Aug/05 1:04 PM
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Andromda. Try JIRA - bug tracking software for your team.