Philip Mark Donaghy wrote:
Ate, Thorsten,
Fix confirmed. Now that I have an andromda application that works
using the struts bridge I would like to commit it to the applications
directory of the bridges project. I need to clean it up and add the
apache license.
Regarding licenses andromda is a bsd license and the dependencies
depend on which cartridge is used. I'm using the java, spring, and
bpm4struts catridges which are all compatible with the apache license.
Cool.
The build is m2 so I assume that I need to write a m1 build.
Well, not sure about that, especially as this concerns an example application,
not a new bridge (framework).
We intend to move to a m2 only build environment for Jetspeed-2 and Bridges when we truly switch to Jetspeed 2.2 dev after releasing Bridges 1.0.2 and Jetspeed
2.1.1.
In my opinion investing now on providing an m1 build version for a new
application is probably a bit of a waste.
Question is do we want to include such a demo so close to release?
If its working out of the box (e.g. a drop in war deployment), why not?
We will need to review and test it out if it is feasible (and cool) enough to include it in the Jetspeed-2-demo installer, but we always can provide a remote
installation through the LPAD.
I'd say: go for it :)
Just make sure it's not going to break the build though...
Is anyone else working with or interested in the mda techology?
Working with: no, interested in: yes!
Regards,
Ate
Philip
On 6/11/07, Ate Douma <[EMAIL PROTECTED]> wrote:
Ate Douma wrote:
> Thorsten, Philip,
>
> Confirmed!
And fixed :)
It was indeed caused by the r51073 changes where I missed the removal
of the RENDER_CONTEXT from the session.
I've now reimplemented it and the infinite loop problem is now gone.
Thanks guys for the problem report and confirmation!
Regards,
Ate
>
> I've just tested this out with a few older struts bridges jars I still
> had in my local repository, and one from before Feb 23 did work.
> It looks like the (big) change I committed with r51073 (or later, but I
> suspect that one) broke this.
> I'll look into it and try to find the cause.
> Keep you guys posted.
>
> NB: Thorsten, your not subscribed (anymore) to this list?
> I had to moderate you through this morning, so bear with me if your
> replies might seem to turn up with some delay.
>
> Regards, Ate
>
>
> Thorsten Berger wrote:
>> Hi Ate and Philip,
>>
>> I can confirm the StackOverflowError. I recently updated JS2 and
>> Portals Bridges to the latest trunk and are now getting the error when
>> forwarding to another action. Below is the complete stack trace.
>>
>> One test case: Use form validation and specify an action (not a JSP)
>> in the input attribute of the corresponding action. When validation
>> errors occur, I get the StackOverflowError. This is not the case when
>> specifying a JSP in the input attribute.
>>
>> I assume this is caused by some change to the Struts Bridge in the
>> last months, since this error didn't occur with an earlier version and
>> I'm sure to not have mixed up render and action requests ;)
>>
>> Regards, Thorsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
