May 2008 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: Send Mail in specified date.

by jalamos

Ok,Thank's View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151194#4151194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151194

18 years, 2 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: This is a drools (JBRMS) related deployment question

by guru_h1

Thanks Jaikiran View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151193#4151193 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151193

18 years, 2 months

1
0
0 / 0

[Clustering/JBoss] - Re: How to get the server being used in HA-JNDI

by jin.peng＠yahoo.ca

Thanks for the reply. If I really want to know, can I register an object into clustered JNDI and the object return the local server name. String getServerName(). This way by looking up the object from JNDI and query getServerName(), I can know what server I am connecting to. Will this work? Thanks, Jin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151192#4151192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151192

18 years, 2 months

1
0
0 / 0

[Clustering/JBoss] - Re: How to get the server being usign in HA-JNDI

by bstansberry＠jboss.com

Sorry, no such API. What server a naming request goes to is determined as part of making the request; it isn't known in advance. And there's no API to expose what it was after the fact. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151191#4151191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151191

18 years, 2 months

1
0
0 / 0

[Clustering/JBoss] - How to get the server being usign in HA-JNDI

by jin.peng＠yahoo.ca

Hi, In clustered jndi, if I give java.naming.provier.url=server1:1100,server2:1100,server3:1100,server4:1100 how do I kniow which server is being used. If there an API that can tell me the server that is being connected? Thanks in advance. Jin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151187#4151187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151187

18 years, 2 months

1
0
0 / 0

[EJB 3.0] - Re: Question on @Service annotated beans

by JonathanDFields

Thank you for the info. I have numerous requirements for "daemon" processing. Watching a directory for files, copying the files, making SOAP calls to a web service, querying/updating the database. Walking a file system and creating a Lucene index. Etc. This processing needs to occur on a regular basis. The way that I am doing this today is with regular MBeans, packaged in a SAR in an overall EAR application, which manage threads using java.util.concurrent.Executor framework. The threads are started via the JMX lifecycle methods (start/stop). Works great. Unfortunately, JBoss Tools for Eclipse does not support SARs as a module in an EAR. Therefore, I'm interested in using @Service beans as a replacement for my plain MBeans for my daemon processing, as I move to JBoss Tools for development. Portability is not a requirement. This only needs to work on JBoss. Would it be OK to do mostly the same with @Service beans as I'm currently doing with plain MBeans? Threads are created/destroyed in the JMX lifecycle methods, as before. The threads would access resources as required to do their work. Only, if they needed to access DB resources, they would call an EJB - perhaps the @Service bean itself. The threads in essence would be the "driver" for the daemon processing, accessing all non-EJB resources directly, and delegating DB access to EJBs. Or, is there a better way to handle this kind of daemon processing? Thanks, Jon View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151185#4151185 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151185

18 years, 2 months

1
0
0 / 0

Delivery Status Notification (Failure)

by postmaster＠lists.jboss.org

This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed. vskartus@localhost

18 years, 2 months

1
0
0 / 0

[JBoss Portal] - Google Widgets Not Editable

by dsulliva

Are Google Widgets Editable, when I add them I don't see how to edit them. There are normally edit features to change the widgets parameters. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151182#4151182 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151182

18 years, 2 months

1
0
0 / 0

[EJB 3.0] - Re: Question on @Service annotated beans

by wolfc

A bean annotated with @Service acts as a stateful bean with just one instance available. So in effect it's the same as a singleton in EJB 3.1. Any lookup or injection of the service bean will result in an association with that single instance. With the use of @Management the service bean will also expose a JMX view of itself. Note that lifecycle mbean methods are currently invoked, but I would rather eliminate that function and have the option of exposing a JMX view for stateless beans as well. In effect this means that the service (/singleton) bean has the same 'prohibitions' as any other EJB. The limitations are put in place to make the bean portable and easily maintainable. You can create threads or access the file system in an EJB, but that means governing your own resources and giving up portability. Resources available to any EJB (JPA entity managers, declarative transactions etc) are fully supported from a service bean. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151181#4151181 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151181

18 years, 2 months

1
0
0 / 0

[EJB 3.0] - Re: Remote Client to EJB 3.0 fail .. :( javax.naming.Communi

by prps1234

Check your context lookup code. If you have used run with a ipadress to start jboss then put the same ipaddess for java.naming.provider.url then you will not get this error. Properties env = new Properties(); env.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); // I had to change localhost to the ipadress of the dev server. // you might have to put it back to localhost if u want to test it on // your local server //env.setProperty("java.naming.provider.url", "localhost:1099"); env.setProperty("java.naming.provider.url", "Use your serverip address:1099"); env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming"); ctx = new InitialContext(env); View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151180#4151180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4151180

18 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user May 2008