HI all,

I have a problem , first look at the output i get

10:43:58,458 DEBUG [WorkClientEJBServiceLocator] Using the JNDI URL
:http://localhost:80/invoker/JNDIFactory 10:43:58,520 DEBUG
[HttpNamingContextFactory] Retrieving content from :
http://localhost:80/invoker/JNDIFactory 10:43:58,583 DEBUG
[HttpNamingContextFactory] ContentLength: -1
ContentType: application/x-java-serialized-object;
class=org.jboss.invocation.MarshalledValue 10:43:58,989 INFO  [Util] The URL
value obtained from cleint:http://192.168.0.146:80/invoker/JMXInvokerServlet
10:43:59,114 DEBUG [EJBServiceLocator] Singleton instance of
EJBServiceLocator class 'de.sepp.client.WorkClientEJBServiceLocator'
created. 10:43:59,130 INFO  [Util] The URL used is
:http://192.168.0.146:80/invoker/JMXInvokerServlet


At the first time the JNDI invocation is done withe same URL as i have
provided

but later while accessing the JMXInvokerServlet its resolving the IP address
and instead of the host name

well i can change this in the http-invoker.sar/meta-inf/jboss-service.xml by
setting USeHostName property to true

but what it does is it takes the InetAddress.getHostName   which is nothing
but the computer name

in my case i am using a reverse proxy and there are two different ways of
accessing this machine. From local lan it is called xx1 and from outside it
is called xx2. So my request is in the second instance also it should
whatever hostname i gave it in the JNDI url...is it possible

any suggestions or solutions

thanks in advace
jani

-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Scott M
Stark
Gesendet: Donnerstag, 14. August 2003 13:09
An: [EMAIL PROTECTED]
Betreff: Re: [JBoss-user] Accessing a ResourceBundle from a MDB


Typically WEB-INF/classes is not visable outside of the associated war. Move
the
common resources to the mdb jar or a common jar referenced by the ear
--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

Brian McSweeney wrote:

> Hi all,
>
>
>
> I’m deploying my app on JBoss 3.2.1_tomcat-4.1.24
>
> I’m deploying an ear which contains a war which uses
>
> Struts as the web controller. The back end uses ejbs in
>
> an ejb-jar file.
>
>
>
> I’m using a resource bundle properties file successfully in
>
> my struts actions to internationalize the app.
>
> The resource bundle properties file is in the folder war file
>
> in the folder:
>
>
>
> /WEB-INF/classes
>
>
>
> All the struts actions are here too.
>
>
>
> However I also need to load the resource bundle from the
>
> back end. When I try to load the resource bundle from a
>
> Message Driven Bean it can’t find the file.
>
>
>
> Now the class files for the back end in the ear are in the
>
> appname-ejb.jar file. I had hoped that if they were packaged
>
> together in the one ear than, maybe they’d be able to see all
>
> the classes, but perhaps not.
>
>
>
> So should I just copy the resource bundle file into the ejb.jar file
>
> So that my session beans and message driven beans can see
>
> the properties file?
>
>
>
> Thanks for any responses,
>
> Regards,
>
> Brian
>



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to