>>>>> "Phil" == Phil Shrimpton <phil@...> writes:
Phil> Hi, I have a problem, and the solution seems to be an MBean,
Phil> but I need to call/use both remote and local EJB's (SLS).
Phil> Now I have a couple of JMX books, a number of JMX articles,
Phil> but none of them contain an example of using/calling EJB's
Phil> within an MBean.
Phil> It works, as I have tried it, but should I be doing it?
Sure, why not? An MBean is just another java client with some fancy
deploy and management stuff. We do it all the time.
-Bob
--
SynXis Corporation | bob@... | no .sig today.
1610 Wynkoop, Suite 400 | Ph: (303)595-2511 |
Denver, CO 80202 | Fax:(303)534-4257 |

When you say Tomcat running as a separate bundle, I'm taking that to
mean in a different JVM. If so, I don't think you can just look it up.
The Mail service is an MBean, not an EJB. You might be able to get a
handle to the MBeanServer, and locate the MBean that way.
Marco Tedone wrote:
> I tried with your code, Guy. Anyway, I'm trying to getting a Jboss Mail
> Session from a class running under Tomcat (running as separate bundle),
> therefore I don't bind the <resource-ref> element to any session or entity
> bean. What I would like is just to retrieve a Mail Session Object from JBoss
> and to use it, instead of implementing (as I've done) it on my own.
>
> I tried your code, but I obtain the following exception (the first part is
> customized):
>
> NamingException while getting the Jboss Mail Session: Mail not bound
>
> The InitialContext object has been set correctly, as I manage entity and
> session bean successfully.
>
> If you don't have time to follow this issue, just leave it, I'm happy with
> the service I implemented under Tomcat right now, but if I could use Jboss I
> would be happier.
>
> Marco
>
> ----- Original Message -----
> From: "Guy Rouillier" <guy-rouillier@...>
> To: <jboss-user@...>
> Sent: Tuesday, June 10, 2003 5:07 AM
> Subject: Re: [JBoss-user] Retrieving a mail session object from Jboss
> [3.2.1]
>
>
>
>>Here is what I did under 2.4.3. The same thing should work in 3.2.1, as
>>I see mail-service.xml is in the default server. Check your server
>>(either the logs or jmx-console) to make sure the mail service has
>>started properly.
>>
>>Source:
>>Session session = ((Session) new
>>InitialContext().lookup("java:comp/env/mail/Mail"));
>>
>>ejb-jar.xml:
>>
>><resource-ref>
>> <description>A mail session for the Email bean</description>
>> <res-ref-name>mail/Mail</res-ref-name>
>> <res-type>javax.mail.Session</res-type>
>> <res-auth>Container</res-auth>
>></resource-ref>
>>
>>jboss.xml:
>>
>><resource-managers>
>> <resource-manager>
>> <res-jndi-name>java:/Mail</res-jndi-name>
>> <res-name>mail/Mail</res-name>
>> </resource-manager>
>></resource-managers>
>>
>>
>>
>>Marco Tedone wrote:
>>
>>>Hi, I would like to retrieve a javax.mail.Session object from within a
>
> class
>
>>>running under Tomcat.
>>>
>>>I would like to user the javax.mail.Session provided by Jboss. In the
>>>jmx-console, I can see that under the java Namespace there is the 'Mail'
>>>name; however, from within my class, when I do the following:
>>>
>>>//setJbossProperties() returns a Properties object set for Jboss. It
>
> works
>
>>>as another class uses it and my entity/session
>>>//beans work greatly
>>>
>>>InitialContext context = new
>>>InitialContext(JbossService.newInstance().setJbossProperties());
>>>//jndiName contains "java:comp/env/Mail"
>>>Object node = context.lookup(jndiName);
>>>session = (Session)PortableRemoteObject.narrow(node, Session.class);
>>>
>>>I receive the following exception:
>>>
>>>ERROR 09 Jun 2003 22:37:41,859 framework.MailService --> NamingException
>>>while creating a JavaMail Session: comp not bound
>>>
>>>or, if I set jndiName with "java:/Mail"
>>>
>>>ERROR 09 Jun 2003 22:37:41,859 framework.MailService --> NamingException
>>>while creating a JavaMail Session: Mail not bound
>>>
>>>I also tried simply with the following:
>>>
>>>InitialContext context = new
>>>InitialContext(JbossService.newInstance().setJbossProperties());
>>>session = (Session)context.lookup(jndiName);
>>>
>>>Two questions:
>>>
>>>1) Is it possible from an external class (let's say under Tomcat) to
>>>retrieve a Session object by simply lookup the Jboss JNDI namespace?
>>>
>>>2) Is the source I wrote correct?
>>>
>>>Thanks for any help,
>>>
>>>Marco
>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by: Etnus, makers of TotalView, The best
>>>thread debugger on the planet. Designed with thread debugging features
>>>you've never dreamed of, try TotalView 6 free at http://www.etnus.com.
>>>_______________________________________________
>>>JBoss-user mailing list
>>>JBoss-user@...
>>>https://lists.sourceforge.net/lists/listinfo/jboss-user
>>
>>
>>--
>>Guy Rouillier
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: Etnus, makers of TotalView, The best
>>thread debugger on the planet. Designed with thread debugging features
>>you've never dreamed of, try TotalView 6 free at http://www.etnus.com.
>>_______________________________________________
>>JBoss-user mailing list
>>JBoss-user@...
>>https://lists.sourceforge.net/lists/listinfo/jboss-user
>>
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: eBay
> Great deals on office technology -- on eBay now! Click here:
> http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
> _______________________________________________
> JBoss-user mailing list
> JBoss-user@...
> https://lists.sourceforge.net/lists/listinfo/jboss-user
--
Guy Rouillier

Hi,
I have a problem, and the solution seems to be an MBean, but I need to
call/use both remote and local EJB's (SLS).
Now I have a couple of JMX books, a number of JMX articles, but none of them
contain an example of using/calling EJB's within an MBean.
It works, as I have tried it, but should I be doing it?
Phil
--
9:07pm up 56 days, 10:00, 1 user, load average: 0.15, 0.06, 0.01
ICQ: 760757 AIM: pjshrimpton Y!: pjshrimpton

Hi Scott,
Scott M Stark <scott.stark@...> writes:
> Filters are logically equivalent to the ejb interceptors on which
> the security proxy is based.
I'm hip to using a filter, but does it make sense to obtain,
continuing the example below, the customer ID from the authenticated
Subject, as some type of Credential maybe? What would be involved to
make that happen -- would I have to write my own LoginModule?
Thanks,
Jim
> On Friday, May 2, 2003, at 08:08 AM, Jim Crossley wrote:
>
>> Hi, I'm sure other people have solved this problem, but I can't find
>> any applicable solutions in the forums/archives.
>>
>> The J2EE role-based authorization model doesn't seem to address the
>> problem of say, preventing a user in the "customer" role from seeing
>> customer data other than his own.
>>
>> I understand the SecurityProxy class was designed to help with this,
>> but I'm looking for something I could use in a servlet instead of an
>> EJB.
>>
>> Any suggestions are welcome!
>>
>> Jim

Hi,
Is it possible to get notifications when modules are
deployed/undeployed?
I would like to write a JBoss 3.3 add-on that does 'something' when for
example a web app is deployed/undeployed.
Is this possible with a JMX component?
S.

According to the jBoss website DR2 is supposed to be released sometime today. Is this plan still on track? When is the released scheduled for?
Edward Flick
Enterprise Applications Designer / Database Administrator / Web Administrator
CDF, Inc.
---------------------------------
Do you Yahoo!?
Free online calendar with sync to Outlook(TM).

Hi, I've seen and uddi repository included in JBoss 4.0. As I am =
interested in registering my webservices with it, is there any =
documentation available? any examples?, I've seen juddi.jar and =
uddi4j.jar in java.net.sar, which one is used? and, what for?
Greets,
Alberto Rodriguez Galdo
tetoro@...

Hello Nicholas,
if you have NOT NULL foreign keys and want to use cascade-delete, you
should use a custom container configuration with sync-on-commit-only
set true:
<container-configurations>
<container-configuration extends="Standard CMP 2.x EntityBean">
<container-name>Sync On Commit Only CMP2.x Container</container-name>
<sync-on-commit-only>true</sync-on-commit-only>
</container-configuration>
</container-configurations>
alex
Wednesday, June 11, 2003, 3:58:10 PM, Nicholas Nicholas wrote:
N> We just figured this one out, but we are using 3.2.0.
N> The foregin key in the child table was defined as NOT
N> NULL and JBoss was trying to set it to null so it was
N> failing right there.
N> Once we set it to NULLABLE, it appears that JBoss sets
N> the foregin keys to null, then deletes them. I am sure
N> there is an explanation as to why it works this way,
N> but it does work as desired.
N> //Nicholas
N> --- Warren Mira <wowx@...> wrote:
>> Hi,
>>
>> We have configured oracle for cascade delete, works
>> fine from doing
>> delete via sqlplus, other clients, but if we do a
>> remove() from an
>> Entity bean, the cascade is not happening. Anyone
>> else experiencing
>> this?, using jboss-3.0.4
>>
>> Thanks
>> Warren

Hi,
I can't figure out what causes the following error. This happens when a
huge amount of data is written to a JMS queue. It occurs regularly in
the logs. The exception always causes an ORA-600 error in the Oracle
database:
2003-06-11 11:59:19,727 DEBUG
[org.jboss.resource.adapter.jms.JmsSession] Closing session
2003-06-11 11:59:19,727 DEBUG
[org.jboss.resource.adapter.jms.JmsManagedConnection] Sending connection
event: 1
2003-06-11 11:59:20,065 INFO
[org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener]
Unregistered handle that was not registered
! null for managedConnection:
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@...
2003-06-11 11:59:20,066 WARN
[org.jboss.resource.connectionmanager.JBossManagedConnectionPool]
ResourceException cleaning up ManagedConnection:org.jboss.reso
urce.JBossResourceException: Could not cleanup: ; - nested throwable:
(java.sql.SQLException: E/A-Exception: Broken pipe)
2003-06-11 11:59:20,067 INFO
[org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener]
Unregistered handle that was not registered
! null for managedConnection:
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@...
2003-06-11 11:59:20,068 INFO
[org.jboss.resource.connectionmanager.JBossManagedConnectionPool]
Exception destroying ManagedConnection
org.jboss.resource.JBossResourceException: SQLException; - nested
throwable: (java.sql.SQLException: E/A-Exception: Broken pipe)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:445)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:229)
at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.doDestroy(InternalManagedConnectionPool.java:374)
at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java:250)
at
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool.returnConnection(JBossManagedConnectionPool.java:653)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection(BaseConnectionManager2.java:451)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2$BaseConnectionEventListener.connectionErrorOccurred(BaseConnectionManager2.java:762)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionErrorOccurred(TxConnectionManager.java:629)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:309)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.connectionError(BaseWrapperManagedConnection.java:294)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:444)
at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:95)
at
org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:773)
at
org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1580)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:366)
at
org.jboss.mq.pm.jdbc2.PersistenceManager$TransactionManagerStrategy.endTX(PersistenceManager.java:183)
at
org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:696)
at
org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:39)
at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:124)
at
org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:404)
at
org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:430)
at
org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:185)
at
org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:370)
at
org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:187)
at org.jboss.mq.il.jvm.JVMServerIL.transact(JVMServerIL.java:328)
at org.jboss.mq.Connection.send(Connection.java:928)
at
org.jboss.mq.SpyXAResourceManager.commit(SpyXAResourceManager.java:127)
at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:103)
at
org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1580)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:366)
at
org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:369)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:253)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:104)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:117)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
at
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at
org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:322)
at org.jboss.ejb.Container.invoke(Container.java:674)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at
org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:88)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:77)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:80)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:109)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:82)
at $Proxy82.sendEntireTrafficMessageToQueue(Unknown Source)
Thanks,
-marek

We just figured this one out, but we are using 3.2.0.
The foregin key in the child table was defined as NOT
NULL and JBoss was trying to set it to null so it was
failing right there.
Once we set it to NULLABLE, it appears that JBoss sets
the foregin keys to null, then deletes them. I am sure
there is an explanation as to why it works this way,
but it does work as desired.
//Nicholas
--- Warren Mira <wowx@...> wrote:
> Hi,
>
> We have configured oracle for cascade delete, works
> fine from doing
> delete via sqlplus, other clients, but if we do a
> remove() from an
> Entity bean, the cascade is not happening. Anyone
> else experiencing
> this?, using jboss-3.0.4
>
> Thanks
> Warren
>
>
>
>
-------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of
> TotalView, The best
> thread debugger on the planet. Designed with thread
> debugging features
> you've never dreamed of, try TotalView 6 free at
> http://www.etnus.com.
> _______________________________________________
> JBoss-user mailing list
> JBoss-user@...
>
https://lists.sourceforge.net/lists/listinfo/jboss-user
=====
Nicholas Whitehead
Home: (973) 377 9335
Cell: (201) 615 2716
nwhitehe@...
Get Your News From The Crowbar: http://crowbar.dnsalias.com:443/crowbar/

Hi Guy,
I would like to explain the scenario in more detail.
When I perform a lookup to this particular Stateless session bean, it works
on all the scenario's except for the error one. I am pasting a debug
messages from my log for both the successfull lookup as well as for the
error ones
Success
----------
DEBUG 11/Jun/2003 16:58:00 [Thread-36] (HomeReferencesManager.java:249):
util.HomeReferencesManager - getContext( Properties env ) Context:
javax.naming.InitialContext@...
DEBUG 11/Jun/2003 16:58:00 [Thread-36] (Query.java:1732): ejb.Query -
jb_007 ---> execute() :: queryHome = QuerySessionHome
DEBUG 11/Jun/2003 16:58:00 [Thread-36] (Query.java:1734): ejb.Query -
jb_007 ---> execute() :: queryRemote = QuerySession:Stateless
where 'queryHome' and ''queryRemote'' are the Home and Remote interfaces.
Error
-------
ERROR 11/Jun/2003 16:58:30 [Thread-36] (HomeReferencesManager.java:106):
util.HomeReferencesManager - Cannot instantiate class:
org.jnp.interfaces.NamingContextFactory
java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
So as you can see both the scenario occur in the same flow. I.e in
successfull the initail context intialization is successfull and the other
one ERROR.
One doubt is, Is there any bug related to this in JBoss3.0.4? Reason for
the doubt being I upgraded to JBoss3.0.4 from 3.0 because of one bug in the
transaction race condition(suggested by Adrian).
Thanks
Muraly
At 15:15 10/06/2003 -0400, you wrote:
>Well, if jnp-client.jar were actually on the classpath when this code is
>executed, you wouldn't be getting this exception. How are you identifying
>the classpath used at this time? To help trace this down, find a scenario
>that you know is failing. Then, before doing the lookup, print out the
>classpath being used - you should be able to do a
>getProperty("java.classpath") or something like that. Hopefully, the
>value of the classpath at that moment will provide a clue as to where it
>is getting incorrectly set.
>
>Muraly R wrote:
>
>>Sorry, this time with stack trace attached...:-)
>>-M
>>At 14:22 10/06/2003 +0530, you wrote:
>>
>>>Hi Gurus,
>>> I am actually stuck with this error scenario. The flow for the
>>> scenario is there is lookup portion in my client code(i.e tomcat
>>> separate installation), which looks up JBoss server(3.0.4) for a
>>> session bean. This works fine, except in some scenario's the following
>>> error is thrown:
>>>
>>>ERROR 10/Jun/2003 13:49:13 [Thread-34] (HomeReferencesManager.java:106):
>>>util.HomeReferencesManager - Cannot instantiate class:
>>>org.jnp.interfaces.NamingContextFactory
>>>
>>>java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
>>>
>>>I have jnp-client.jar in the client classpath.
>>>
>>>Have any one encountered this scenario before? Please share your
>>>thoughts on the same.
>>>
>>>The most confusing(irritating actaully) part is, the same bean lookup
>>>from the same code snippet location works fine in some scenarios.
>>>
>>>Thanks
>>>Muraly
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by: Etnus, makers of TotalView, The best
>>>thread debugger on the planet. Designed with thread debugging features
>>>you've never dreamed of, try TotalView 6 free at http://www.etnus.com
>>><http://www.etnus.com/&gt;.
>>>_______________________________________________
>>>JBoss-user mailing list
>>>JBoss-user@...
>>>https://lists.sourceforge.net/lists/listinfo/jboss-user
>>
>>------------------------------------------------------------------------
>>ERROR 10/Jun/2003 13:49:13 [Thread-34] (HomeReferencesManager.java:106):
>>util.HomeReferencesManager - Cannot instantiate class:
>>org.jnp.interfaces.NamingContextFactory
>>java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
>> at java.net.URLClassLoader$1.run(Unknown Source)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at java.net.URLClassLoader.findClass(Unknown Source)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.net.FactoryURLClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>> at java.lang.Class.forName0(Native Method)
>> at java.lang.Class.forName(Unknown Source)
>> at com.sun.naming.internal.VersionHelper12.loadClass(Unknown Source)
>> at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
>> at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
>> at javax.naming.InitialContext.init(Unknown Source)
>> at javax.naming.InitialContext.<init>(Unknown Source)
>> at
>> com.cisco.nm.qpm.server.util.HomeReferencesManager.getContext(HomeReferencesManager.java:248)
>> at
>> com.cisco.nm.qpm.server.util.HomeReferencesManager.getHome(HomeReferencesManager.java:100)
>> at
>> com.cisco.nm.qpm.server.inventory.ejb.Query.execute(Query.java:1728)
>> at com.cisco.nm.qpm.web.util.grid.DataGrid.work(DataGrid.java:189)
>> at com.cisco.nm.qpm.web.util.grid.DataGrid.<init>(DataGrid.java:103)
>> at
>> policy.group.NetworkElementSelection_1._jspService(NetworkElementSelection_1.java:909)
>> at
>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>> at
>> org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574)
>> at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
>> at org.apache.tomcat.core.Handler.service(Handler.java:235)
>> at
>> org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
>> at
>> org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:917)
>> at
>> org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
>> at
>> org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection(Ajp13Interceptor.java:341)
>> at
>> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
>> at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
>> at java.lang.Thread.run(Unknown Source)
>>ERROR 10/Jun/2003 13:49:13 [Thread-34] (Query.java:1748): ejb.Query -
>>com.cisco.nm.qpm.server.util.HomeReferencesManagerException:
>>javax.naming.NoInitialContextException: Cannot instantiate class:
>>org.jnp.interfaces.NamingContextFactory [Root exception is
>>java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
>> at
>> com.cisco.nm.qpm.server.util.HomeReferencesManager.getHome(HomeReferencesManager.java:107)
>> at
>> com.cisco.nm.qpm.server.inventory.ejb.Query.execute(Query.java:1728)
>> at com.cisco.nm.qpm.web.util.grid.DataGrid.work(DataGrid.java:189)
>> at com.cisco.nm.qpm.web.util.grid.DataGrid.<init>(DataGrid.java:103)
>> at
>> policy.group.NetworkElementSelection_1._jspService(NetworkElementSelection_1.java:909)
>> at
>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>> at
>> org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574)
>> at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
>> at org.apache.tomcat.core.Handler.service(Handler.java:235)
>> at
>> org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
>> at
>> org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:917)
>> at
>> org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
>> at
>> org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection(Ajp13Interceptor.java:341)
>> at
>> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
>> at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
>> at java.lang.Thread.run(Unknown Source)
>
>
>--
>Guy Rouillier
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Etnus, makers of TotalView, The best
>thread debugger on the planet. Designed with thread debugging features
>you've never dreamed of, try TotalView 6 free at http://www.etnus.com.
>_______________________________________________
>JBoss-user mailing list
>JBoss-user@...
>https://lists.sourceforge.net/lists/listinfo/jboss-user

Surajit Bhattacharjee wrote:
>Hi ionel!
>
>I am new to JBoss and don't know if this is supported, but u can try this:
>
>U can specify a security principal (user id) and security credential
>(passwd) when u create the JNDI InitialContext for looking up the session
>bean in ur scheduler. The same user can be mapped to the desired role.
>
>Thanks,
>Surajit
>
Hi Surajit,
How to specify this ?
I find no methods that explcitly set the principal nor the credential.
The only supposed method to do so is addToEnvironment()
So using addToEnvironement(Context.SECURITY_PRINCIPAL, "theusername")
and addToEnvironment(Context.SECURITY_CREDENTIALS, "thepassword") should
do the trick ?
Am I on the rigth way ?
thanks,
ionel

Thanks for your reply. I added the parameter and the first time I make the
request I get the Authentication error and after that I get an Authorization
error. Still looks like M$ is not sending anything after getting the 500
error. Did you managed to get it working?
Is it possible that to trigger the sending of data M$ expect the 500 when
getting the wsdl on the init call and not on the actual web service call?
Thanks
Simone
----- Original Message -----
From: "Jung , Dr. Christoph" <christoph.jung@...>
To: <jboss-user@...>
Sent: Tuesday, June 10, 2003 4:43 PM
Subject: AW: [JBoss-user] M$ Soap 3.0 toolkit and JBoss.net interop
There was a bug-report on that issue stating that M$ would not send
authentication data
until faced with a server error (50x or something similar, I think).
The JBoss Authentication Handler has been extended with the parameter
"validateUnauthenticatedCalls"
<!-- authentication runs against the jaas:/other
domain -->
<handler
type="java:org.jboss.net.axis.server.JBossAuthenticationHandler">
<parameter name="securityDomain"
value="java:/jaas/other"/>
<parameter
name="validateUnauthenticatedCalls" value="false"/>
</handler>
This will block any unauthenticated calls from trying to get routed (this is
what M$ could first try to do before going the "right" way).
Best,
CGJ
> -----Ursprüngliche Nachricht-----
> Von: Simone Milani [mailto:milasx@...]
> Gesendet: Dienstag, 10. Juni 2003 16:29
> An: jboss-user@...
> Betreff: [JBoss-user] M$ Soap 3.0 toolkit and JBoss.net interop
>
>
> Hi,
>
> I am happily using the M$ Soap 3.0 toolkit as a client
> for JBoss.net. I am now having trouble having the Basic
> Authentication to work. Has anyone managed to use it?
>
> Thanks
>
>
> Simone
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of
> TotalView, The best thread debugger on the planet. Designed
> with thread debugging features you've never dreamed of, try
> TotalView 6 free at http://www.etnus.com.
> _______________________________________________
> JBoss-user mailing list
> JBoss-user@...
> https://lists.sourceforge.net/lists/listinfo/j&gt; boss-user
>
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at http://www.etnus.com.
_______________________________________________
JBoss-user mailing list
JBoss-user@...
https://lists.sourceforge.net/lists/listinfo/jboss-user

Hi ionel!
I am new to JBoss and don't know if this is supported, but u can try this:
U can specify a security principal (user id) and security credential
(passwd) when u create the JNDI InitialContext for looking up the session
bean in ur scheduler. The same user can be mapped to the desired role.
Thanks,
Surajit
-----Original Message-----
From: jboss-user-admin@...
[mailto:jboss-user-admin@...]On Behalf Of Ionel
Gardais
Sent: Wednesday, June 11, 2003 1:22 AM
To: jboss-user@...
Subject: Re: [JBoss-user] [help please] specifing a role to a scheduled
class
Hi kiuma,
thanks for the tip. I am already using this for my facade session bean
and the local entities.
My problem is that the scheduled class (the one which extends the
Schedulable interface) is not an EJB !
It's a basic java object with a perform method and that's all.
A solution should be to create all the classes needed for JAAS (a
callback handler ...) to create a security context in my class and to
log in the server.
It looks huge for what I want to do.
I thought the Scheduler would provide some security support (such a
<attribute name="username">name</attribute> and <attribute
name="password">pass</attribute> in the mbean configuration so the
schedulable class will be ran using these credentials.
thanks,
ionel
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at http://www.etnus.com.
_______________________________________________
JBoss-user mailing list
JBoss-user@...
https://lists.sourceforge.net/lists/listinfo/jboss-user