[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-09-14 Thread jae77
has any further work gone into this? i've given this a go myself, and i keep getting the following error trying to deploy: | 2004-09-14 22:27:11,851 ERROR [org.jboss.nukes.core.Main] Cannot register on component nukes.themes:name=imagic | java.lang.reflect.UndeclaredThrowableException |

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-11 Thread invisiblemage
ok, had some time today to have a look again... The getNext() is now done in the AbstractInterceptor.Invoke()... so I just deleted all the lines in the LifecycleInterceptor. Some strange things happen now and then wenn in the LifeCycle the invoke() is called with type invoke... debug showed

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-05 Thread invisiblemage
Invocation.OP_INVOKE == invoke which is first called on LifeCycleInterceptor for the create... but then Interceptor ic = invocation.nextInterceptor(); ic.invoke(interceptor) is called on the ModelMBeanAttributeInterceptor, where the invocation.getType() == OP_INVOKE, but it should be one of

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-04 Thread invisiblemage
Hi, yes, I have found that post two days ago... after several hours figuring out myself :-( what I did after that: I got MBeanNotCompliant, since the lifecycleinterceptor seems to be missing the default constructor, so I added public LifeCycleInterceptor() { super(); this.log

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-03 Thread jae77
i could have sworn i posted something about this not to long ago, but i can't seem to find the thread, and i'm pretty worn out from relocating back to nyc, and i don't really have the energy to keep looking. :) the Invocation class that used to reside in org.jboss.mx.interceptor package no

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-02 Thread theute
The thing is just that (i think) nobody really took care of it yet and is able to answer your question. If you succeed, please let us know how you did. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3843890#3843890 Reply to the post :

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-02 Thread KaMiKaTze
Ok, then let's start :-) (Just don't take me wrong, I didn't want to sound offending, it's just that if someone would have figured out what to do already, he would propably have coded it :-) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3843897#3843897 Reply

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-02 Thread cooper
I will look at the compatibility issue this week, Nukes 1.x should work with JBoss-3.2.6 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3843898#3843898 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3843898

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-02 Thread invisiblemage
Just trying to sound funny ;-) I will have a look at that Lifecycle and the changes to the AbstractInterceptor tomorrow Anyway, if somebody knows where the getNext() is gone, just tell me :) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3843921#3843921 Reply

[JBoss-dev] [Nukes Development] - Re: Nukes compatibility to JBoss upgrade path

2004-08-02 Thread KaMiKaTze
getNext().invoke() is the body of the AbstractInterceptor's invoke() method in 3.2.x. Have a look into the invoke() Method of the AbstractInterceptor of 4.0, there you see where getNext().invoke() has gone :-) Mika View the original post :