Re: BeanShell and Class: x not in namespace

> What do you mean by "...in your EAR directory..."? Do you mean the
> path to the exploded directory?
Your $HOME/.jython has a variable .python.path=. This variable needs  
to be set so that it has access to anything that you want to be able  
to us in jython (which include any beans you packaged up in your  
EAR). Usually you want to have access to Session Beans in the Java  
code. We had to specify in this the path to all the jar files we  
wanted JPublish jython to have access.

> lso, are you suggesting to use 2.0?
> What will I be "losing" by downgrading?
It has been some time when I was trying to get JPublish 3.0 working,  
I think it was still in Beta. I am guessing that it might be easier  
to get it working now that it is out of Beta. However I know 2.0  
works with JBoss 3.2 because that is what we are using. So if you  
can't seem to get 3.0 to work you might want to try and drop down.
http://jpublish.org/whatsnew/3.0.html
What reasons are you using JPublish for? You may not be loosing  
anything but depends on what you like about JPublish.

On Jun 16, 2006, at 10:24 AM, Rebel Geek wrote:

> Thanks Lateef,
>
> What do you mean by "...in your EAR directory..."? Do you mean the
> path to the exploded directory? Also, are you suggesting to use 2.0?
> What will I be "losing" by downgrading? Thanks.
>
>
>
> On 6/16/06, Lateef Jackson <[email protected]> wrote:
>>
>> There are a couple of issues (actually a lot of issues with JBoss/ 
>> J2EE but
>> that would take an encyclopedia):
>> 1) The jython issue (you are using bsh but the problem might be  
>> simular) :
>> You hopefully have a $HOME/.jython file which should have the  
>> class path to
>> all your jar you want jython to have access to (including the ones  
>> in your
>> EAR directory). Whatever the user that starts up jboss on your  
>> production
>> server also needs to have that .jython file.
>> 2) JPublish 3.0 is probably not going to work:
>> Spent a good week or two trying to get 3.0 to work and just gave  
>> up. It
>> could have been that we had some other complexities with our  
>> classpath but I
>> have a feeling that round peg and square hole. I believe I got  
>> upgraded to
>> 2.0 (had 1 originally) but you may have better luck because you  
>> are starting
>> from scratch.
>> 3) JBoss hotdeploy in all this:
>> hotdeploy might be more of not cold deploy. I think we had to do some
>> hacking to something to get this to work in 3.2 (Don't upgrade).  
>> Linux JVM
>> seemed to be the most stable with this however minor version  
>> releases make a
>> difference. So make sure you don't try to hot deploy when you are  
>> trying to
>> get this to work. Go with a cold deploy.
>> 4) Finally every WAR you have you have to have all the jar copied  
>> into the
>> WEB-INF/lib separately.
>>
>> If you have other issues let me know I might be able to help.
>> Good Luck,
>> Lateef
>>
>> On Jun 16, 2006, at 9:51 AM, Rebel Geek wrote:
>> Thanks Florin,
>>
>> The bsh-2.0.jar is in WEB-INF/lib of my JPublish project which is  
>> in a WAR
>> which is in an EAR which is archived. <smile> The version of JBoss  
>> is 3.2
>> and the version if JPublish is 3.0.
>>
>> I did notice that BeanShell *will* find classes if they have been  
>> deployed
>> independantly in their own jar file in the deploy directory as  
>> well as the
>> all/lib of JBoss, but this is not the desired effect. All the  
>> dependancies
>> are in the WEB-INF/lib of the individual project so if we need to  
>> deploy all
>> the relevant jars separately, then it becomes a management nightmare.
>>
>> I tried using the addClassPath in the startup bsh action (which, btw,
>> doesn't seem to be running at startup, so I had to use global- 
>> action, but
>> that's another topic) but beanshell complained that addClassPath  
>> is not a
>> known action.
>>
>> Do you have a solution to this? Thanks again.
>>
>>
>>
>> On 6/15/06, Florin T.PATRASCU <[email protected]> wrote:
>>>
>>>
>>> good old JBoss and the classpath saga:)
>>>
>>>
>>> Where exactly do you have the bsh-....jar? Is in your EAR  
>>> repository (EAR
>> is expanded or archived?) or is it in the JBoss server/[default| 
>> all]/lib?
>> JBoss 4.x or 3.x? And which version of JPublish are you running  
>> there?
>>>
>>>
>>> I know, is not exactly an answer ;)
>>>
>>>
>>> -florin
>>>
>>>
>>>
>>>
>>> On 15-Jun-06, at 9:48 AM, Rebel Geek wrote:
>>>
>>>
>>>
>>> Where I work, I have to deploy my application as an EAR file in a
>>> modified JBoss installation (the company that I work for is quite
>>> large and therefore capable of modifying a perfectly working app and
>>> making it worse <smile>). Anyway, everything works fine except  
>>> when I
>>> call one of my classes in a bsh script, BeanShell tells me that the
>>> class is not in the namespace. How do I set the classpath for
>>> BeanShell via JPublish?
>>>
>>> Thanks.
>>>
>>>
>>> --
>>> Rebel Geek
>>> [email protected]
>>> 954-839-6234
>>>
>>> _______________________________________________
>>> Jpublish-developer mailing list
>>> [email protected]
>>>
>> https://lists.sourceforge.net/lists/listinfo/jpublish-developer
>>>
>>>
>>>
>>> _______________________________________________
>>> Jpublish-developer mailing list
>>> [email protected]
>>>
>> https://lists.sourceforge.net/lists/listinfo/jpublish-developer
>>>
>>>
>>>
>>
>>
>>
>> --
>> Rebel Geek
>> [email protected]
>> 954-839-6234
>> _______________________________________________
>> Jpublish-developer mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jpublish-developer
>>
>>
>> Lateef Jackson
>> [email protected]
>>
>>
>>
>>
>>
>> _______________________________________________
>> Jpublish-developer mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jpublish-developer
>>
>>
>>
>
>
> -- 
> Rebel Geek
> [email protected]
> 954-839-6234
>
>
> _______________________________________________
> Jpublish-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jpublish-developer

Lateef Jackson
[email protected]