Resource not loading - 404 Error

Hi Olena,

Excellent, I'm glad you got the hint to show the way you wanted.

Regarding your <xf:trigger> that uses and <xf:load>, could you share the
code of that trigger in a response? You might have done so already, but the
code doesn't show in your message. If that is the case, feel free to put it
in a text file, and attached that file to your response.

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Alex, thank you for a quick response. This is quite urgent for us as this
issue was found so late in our UAT cycle. I have attached a file, please see
the lines no# 254, 269 in the attached file

Dominion_messages_showData.jsp
<http://discuss.orbeon.com/file/t375473/Dominion_messages_showData.jsp>  


--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Olena,

I suspect that the issue might be caused by the `show="new"` or the
reference to the variable. You could try to remove the `show="new"` to see
if it works without it. You might might to add a `<xf:message
value="$urlValue"/>` to check if the variable has the correct value.
Finally, are you seeing anything interesting in your `orbeon.log` when you
click on trigger? If not, could you attach the relevant section of the
`orbeon.log`?

Finally, are you using Orbeon Forms PE? This would allow you to have support
with us.

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

HI, what changes you did to get the 403 error fixed as I am having the same
issue and going in circles trying to fix. Appreciate your urgent assistance
please as my UAT is stuck because of this.

Regards
Raheel

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Raheel,

Olena had custom code in their form which most likely was causing their
problem. They had edited the source of the form, and inserted their own
`xforms:load`. If you have done any changes to the source of the form, I
would recommend you try to reproduce the issue with a empty form you create
in Form Builder, and add things to the form until you can reproduce the
issue, so you can pinpoint what is causing the problem. Would this make
sense?

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Alex, when we run the vanilla and publish the forms, its a success. We
have customized codes so we will look into this as without the custom codes
all seems fine but with custom code it fails. Any other files/changes we
need to track?

Regards
Raheel

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Alex, there are no custom codes in my case. What else could the cause?
Regards
Raheel

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Raheel,

If you have custom code added to your form, and things work without it, you
have good lead! I'd recommend you start by identifying what is causing the
problem, removing that custom code piece by piece until things work, or
starting with a new form adding custom code piece by piece until they break.

Also, I would set logging per the "Development configuration" (see the
relevant section in the page linked below), and have a `tail -f orbeon.log`
running (or similar) so you can check the log file as you interact with the
page. Make sure you go back to any exception that scroll by, and see if you
can find any useful information about it.

https://doc.orbeon.com/configuration/advanced/xforms-logging.html

You'll let me know what you find!

Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

We had 403 coming up only in Pre-production environment, the code worked in
all lower environments. It was related partially to the naming convention -
we had a specific parameter named S2_...(for Silo2), but in pre-production
it was S1_... . We had discovered that Orbeon didn't read the parameter from
WebSphere console, so we hard-coded it in the
resources/config/properties-local-dev.xml and properties-local.xml

In code below we added bold part, so it would work in all three siloes that
we have:
<property
            as=&quot;xs:string&quot;
            name=&quot;oxf.http.forward-cookies&quot;
            value=&quot;JSESSIONID JSESSIONIDSSO S1_BMSFormsSESSIONID
&lt;b>S2_BMSFormsSESSIONID S3_BMSFormsSESSIONID*"/>

We also removed properties-local-prod.xml because it was causing confusion
and wasn't used in our packaging.

You probably have some other scenario, but I wanted to provide the detail so
you can move on. Alex was very helpful with our upgrade challenges.
Olena

--
Sent from: http://discuss.orbeon.com/

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].