You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Georg Kallidis <gk...@cedis.fu-berlin.de> on 2016/11/02 15:30:16 UTC

Re: Re: Errors found trying to use the new Turbine4-M2 Archetype

Hi Jeffery, hi Thomas,

I updated the archetype 

- removing most of the memory classes and replaced them by Torque managers 
in role-configuration xml (reason: we are now in mysql)

- using lower case groups/roles (because Fulcrum Security 1.1.0 seems to 
have a bug - now fixed in 1.1.1)

- included some abstract classes, which should be not needed any more in 
Fulcrum Security 1.1.1 and 
- om classes, which in Torque 2.1 would be configurable in schema

- added module LogoutUser as getUser is null as, which is already 
corrected in Turbine 4.0 (Session validator did not run, so RunData is not 
populated).

I could successfully generate and test the archetype. 

If you think it´s ok, we have really to prepare release. Then I would 
suggest to first release Fulcrum Intake and Security, test it in Turbine 
4.0, and only after this release the latter.

Have fun! 

-Georg




Von:    Jeffery Painter <je...@jivecast.com>
An:     dev@turbine.apache.org
Datum:  24.10.2016 22:24
Betreff:        Re: Errors found trying to use the new Turbine4-M2 
Archetype



Hi Thomas,

I was able to reset my old Apache account and have checked in my 
changes.  I was able to keep your TurbineHtmlHead and body attributes 
with the new layout. However, I still have a couple issues.

I did some research and discovered the torque datasql task was removed 
quite a while back by Thomas fox, and while it looked like it was on 
target for the torque generator it was never completed (unless you know 
otherwise). https://issues.apache.org/jira/browse/TORQUE-24

Also - after building the sample app, I tried to complete the login/user 
authentication using the default LoginUser action and it does not seem 
like the user is ever authenticated. I will try to debug some more.

I added a folder "docs" to store the readme.txt and some sample data 
ready for insert (I used the old torque generator to build the turbine 
security sql). I inserted manually, launched the app and the login does 
not work.

Thanks,
Jeffery




On 10/23/2016 04:52 PM, Jeffery Painter wrote:
> Hi Thomas,
>
> I am not sure if I have commit access to the repo. It has been many 
> years since I was last involved with the project. I will take your 
> recommendations and try to update some tomorrow.  I could also look at 
> the torque test code.  It took me a while to figure out how the new 
> secure screen/action was supposed to work (since turbine 2.3 days), 
> but I found most of that in test code as well for the Turbine security 
> implementation with fulcrum.
>
>
> Thanks,
> Jeffery
>
>
> On 10/23/2016 01:48 PM, Thomas Vandahl wrote:
>> Hi Jeffrey,
>>
>> On 21.10.16 23:56, Jeffery Painter wrote:
>>> I spent several hours working on cleaning up a bit more to make this a
>>> little more friendly "out of the box" when someone invokes the 
>>> archetype.
>> One more thing: I appreciate your attempts to provide a better styling
>> to the sample application. However would it be possible to keep the
>> #TurbineHtmlHead() and #TurbineHtmlBodyAttributes() somehow in the
>> layout as a best-practice recommendation?
>>
>> Bye, Thomas.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
>> For additional commands, e-mail: dev-help@turbine.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: Antwort: Re: Errors found trying to use the new Turbine4-M2 Archetype

Posted by Jeffery Painter <je...@jivecast.com>.
This is great news.

Hopefully I can be of more help in the year to come.  Since I am working 
for myself again, I get to determine what takes priority :-)

--
Jeffery


On 11/18/2016 02:55 PM, Georg Kallidis wrote:
> Hi Thomas, this would make sense IMO. Turbine M2 archetype could then (after the release) be with all its bells and whistles again, which is a freshly polished Intake - and that&#180;s, what Jeffery kicked off, a perfect second milestone ! ;-)
>
> Best, Georg
>
> -----Thomas Vandahl <tv...@apache.org> schrieb: -----
> An: Turbine Developers List <de...@turbine.apache.org>
> Von: Thomas Vandahl <tv...@apache.org>
> Datum: 18.11.2016 16:34
> Betreff: Re: Errors found trying to use the new Turbine4-M2 Archetype
>
> Hi Georg,
>
> On 18.11.16 13:38, Georg Kallidis wrote:
>> the archetype seems to be now pretty ready and I would prepare a release.
>>
>> What do you think? Should we wait for the intake release? But Turbine 4 RC
>> is waiting too .. ;-)
> A Fulcrum Intake release is made in no time. If you are good with the
> current state I can kick off a vote this weekend.
>
>> I would recommend to release this archetype soon, because then the
>> archetype trunk could be updated soon and this  might be quite useful -
>> having the archetype ready at hand as a test environment for Turbine 4.
>> Have we not found this way some bugs now?
> It looks good to me.
>
> Bye, Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Antwort: Re: Errors found trying to use the new Turbine4-M2 Archetype

Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.
Hi Thomas, this would make sense IMO. Turbine M2 archetype could then (after the release) be with all its bells and whistles again, which is a freshly polished Intake - and that&#180;s, what Jeffery kicked off, a perfect second milestone ! ;-) 

Best, Georg

-----Thomas Vandahl <tv...@apache.org> schrieb: -----
An: Turbine Developers List <de...@turbine.apache.org>
Von: Thomas Vandahl <tv...@apache.org>
Datum: 18.11.2016 16:34
Betreff: Re: Errors found trying to use the new Turbine4-M2 Archetype

Hi Georg,

On 18.11.16 13:38, Georg Kallidis wrote:
> the archetype seems to be now pretty ready and I would prepare a release. 
> 
> What do you think? Should we wait for the intake release? But Turbine 4 RC 
> is waiting too .. ;-)

A Fulcrum Intake release is made in no time. If you are good with the
current state I can kick off a vote this weekend.

> I would recommend to release this archetype soon, because then the 
> archetype trunk could be updated soon and this  might be quite useful - 
> having the archetype ready at hand as a test environment for Turbine 4. 
> Have we not found this way some bugs now?

It looks good to me.

Bye, Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org

Re: Errors found trying to use the new Turbine4-M2 Archetype

Posted by Thomas Vandahl <tv...@apache.org>.
Hi Georg,

On 18.11.16 13:38, Georg Kallidis wrote:
> the archetype seems to be now pretty ready and I would prepare a release. 
> 
> What do you think? Should we wait for the intake release? But Turbine 4 RC 
> is waiting too .. ;-)

A Fulcrum Intake release is made in no time. If you are good with the
current state I can kick off a vote this weekend.

> I would recommend to release this archetype soon, because then the 
> archetype trunk could be updated soon and this  might be quite useful - 
> having the archetype ready at hand as a test environment for Turbine 4. 
> Have we not found this way some bugs now?

It looks good to me.

Bye, Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: Re: Re: Errors found trying to use the new Turbine4-M2 Archetype

Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi all, 

the archetype seems to be now pretty ready and I would prepare a release. 

What do you think? Should we wait for the intake release? But Turbine 4 RC 
is waiting too .. ;-)

I would recommend to release this archetype soon, because then the 
archetype trunk could be updated soon and this  might be quite useful - 
having the archetype ready at hand as a test environment for Turbine 4. 
Have we not found this way some bugs now?

Best regards, Georg




Von:    "Georg Kallidis" <gk...@cedis.fu-berlin.de>
An:     "Turbine Developers List" <de...@turbine.apache.org>
Datum:  07.11.2016 15:53
Betreff:        Re: Re: Errors found trying to use the new Turbine4-M2 
Archetype



Hi Thomas, 

@JNDI 
That´s a good idea, to appear like a well-behaved practicioner ;-)

I´ll check what´s needed to get it to work .. update is coming soon..

Best regards, Georg





Von:    Thomas Vandahl <tv...@apache.org>
An:     Turbine Developers List <de...@turbine.apache.org>
Datum:  05.11.2016 12:35
Betreff:        Re: Errors found trying to use the new Turbine4-M2 
Archetype



Hi Georg,

On 02.11.16 16:30, Georg Kallidis wrote:
> If you think it´s ok, we have really to prepare release. Then I would 
> suggest to first release Fulcrum Intake and Security, test it in Turbine 


> 4.0, and only after this release the latter.

As I discussed with Jeffery earlier, I would like to insist on the JNDI
configuration as a recommendation of best-practice to the user. I
believe it is simply wrong to have credentials for database access in
the application.

Following the path of best-practice recommendations, I modified some of
the modules to take advantage of the new Turbine annotations. However I
have yet to test this before commit.

Moreover, in the new archetype plugin you can execute maven goals at the
end of the generation process. So we could prepare the Turbine
application to be ready to run according to Jefferys how-to. WDYT?

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: Re: Errors found trying to use the new Turbine4-M2 Archetype

Posted by Georg Kallidis <gk...@cedis.fu-berlin.de>.
Hi Thomas, 

@JNDI 
That´s a good idea, to appear like a well-behaved practicioner ;-)

I´ll check what´s needed to get it to work .. update is coming soon..

Best regards, Georg





Von:    Thomas Vandahl <tv...@apache.org>
An:     Turbine Developers List <de...@turbine.apache.org>
Datum:  05.11.2016 12:35
Betreff:        Re: Errors found trying to use the new Turbine4-M2 
Archetype



Hi Georg,

On 02.11.16 16:30, Georg Kallidis wrote:
> If you think it´s ok, we have really to prepare release. Then I would 
> suggest to first release Fulcrum Intake and Security, test it in Turbine 

> 4.0, and only after this release the latter.

As I discussed with Jeffery earlier, I would like to insist on the JNDI
configuration as a recommendation of best-practice to the user. I
believe it is simply wrong to have credentials for database access in
the application.

Following the path of best-practice recommendations, I modified some of
the modules to take advantage of the new Turbine annotations. However I
have yet to test this before commit.

Moreover, in the new archetype plugin you can execute maven goals at the
end of the generation process. So we could prepare the Turbine
application to be ready to run according to Jefferys how-to. WDYT?

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org


Re: Errors found trying to use the new Turbine4-M2 Archetype

Posted by Thomas Vandahl <tv...@apache.org>.
Hi Georg,

On 02.11.16 16:30, Georg Kallidis wrote:
> If you think its ok, we have really to prepare release. Then I would 
> suggest to first release Fulcrum Intake and Security, test it in Turbine 
> 4.0, and only after this release the latter.

As I discussed with Jeffery earlier, I would like to insist on the JNDI
configuration as a recommendation of best-practice to the user. I
believe it is simply wrong to have credentials for database access in
the application.

Following the path of best-practice recommendations, I modified some of
the modules to take advantage of the new Turbine annotations. However I
have yet to test this before commit.

Moreover, in the new archetype plugin you can execute maven goals at the
end of the generation process. So we could prepare the Turbine
application to be ready to run according to Jefferys how-to. WDYT?

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org