Minor Form Change Requires Restart

[PaulCooper]

We are using a third party ebase application (AIS by Northgate) but have been given some training on making changes to the forms.

When we make minor changes to a particular form and deploy it, it throws an error (XML message failed validation) but it all works again after a restart. With other forms, deployment work perfectly ok and do not require a restart.

Can anyone explain this? Is there anything we need to do to stop this?

We have reported this to the vendor (Northgate) but they have yet to come back to us with a solution.

Any help will be gratefully accepted.

Regards,

Paul Cooper

[Steve]

Hi Paul...

Do you have any code in the HTML++ (Form Properties-->Web Resources). I have seen errors in here cause problems.

I am assuming that you mean deploy it... you are exporting the form and importing it into another system?

Also is there an error message in the log file. If so, could you post the error message?

Kind regards

Steve

[PaulCooper]

The edit wasn't done in the Form but in a component. I did check the parent form's HTML++ section and that is:

Code: Select all

<style>
.mainblock &#123;border&#58;inset 0px&#125;
</style>

The deployment was done by clicking on the button "Deploy changes to all linked forms", so to the same server not another one. We did try reversing the changes and deploying again but that didn't get rid of the problem.

The error log is a bit long so I have put it in pastebin.

Regards,

Paul

[Steve]

Hi Paul...

It appears there is an error in the EJB layer of the application. Nothing to do with the redeployment of forms and Ebase. I see there is a stack trace from CustomSource....then into Northgate custom EJB layer. This is out of our control.

My guess is, that the EJB is cached and needs reloading when the form is redeployed because the underlying XML is wrong after re-deployment. I do not know the whole architecture of this application. Perhaps Northgate can advise some more on this.

Kind regards

Steve

[PaulCooper]

My guess is, that the EJB is cached and needs reloading when the form is redeployed because the underlying XML is wrong after re-deployment.

Do you mean the underlying XML file of the EJB? And if XML file in question is invalid why would a restart correct it?

Regards,

Paul

[Steve]

Hi Paul...

This is my the problem....

I am not sure how this all works. So anything I suggest would be a pure guess.

I am assuming this is a runtime error?

Have Northgate come back with anything yet?

Regards

Steve

[PaulCooper]

To be honest I have only a tiny amount of understanding of how their application works. And nothing that shines any light on this situation.

No they haven't come back to us yet and it has been approximately a week since they last asked for more info. We will have to wait.

Yes it is a runtime error.

Regards,

Paul