December 2007 - jboss-user - Jboss List Archives

[JBossWS] - Regarding WS client using JSR109- JAX-RPC

by techie_techie

I need to write a client on JBoss 4.0.4 GA. In order to consume a web service using legacy style which approach of the following would be better JAX-RPC ServiceFactory or JNDI service lookup Is pro/cons of each approach is listed any where? Second question: 1. Can we put JNDI service lookup jar file in WEB-INF/lib of a war file? When I put jar file in deploy folder service context is established but when i put it inside war file it did not work. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116098#4116098 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116098

16 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: @DataModel makes me go nuts or it's a bug ?

by dexjam

Funny how nobody can answer this question i thought that was such a basic thing in seam. I was able to find out, that org.jboss.seam.afterPhase happens before the database is queried. because it's the last event shown on screen, i assume it's the RENDER_RESPONSE phase, and if that shows up before the DB was queried, i do believe that there is no chance for the dataTable to display the queried data. But again, why is this? Jens View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116096#4116096 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116096

16 years, 4 months

1
0
0 / 0

[EJB/JBoss] - Re: Jboos Lookup

by pslambh

Jboss version is 4.2.0 JNDI Tree: +- TopicConnectionFactory (class: org.jboss.naming.LinkRefPair) +- jmx (class: org.jnp.interfaces.NamingContext) | +- invoker (class: org.jnp.interfaces.NamingContext) | | +- RMIAdaptor (proxy: $Proxy48 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt) | +- rmi (class: org.jnp.interfaces.NamingContext) | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef) +- HTTPXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory) +- ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory) +- Bean (class: org.jnp.interfaces.NamingContext) | +- local (proxy: $Proxy131 implements interface beans.BeanBusiness,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject) +- UserTransactionSessionFactory (proxy: $Proxy14 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory) +- HTTPConnectionFactory (class: org.jboss.mq.SpyConnectionFactory) +- XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory) +- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple) +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction) +- UILXAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef) +- XMlBean (class: org.jnp.interfaces.NamingContext) | +- remote (proxy: $Proxy93 implements interface slsb.XMl,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject) +- UIL2XAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef) +- GreetingBean (class: org.jnp.interfaces.NamingContext) | +- local (proxy: $Proxy89 implements interface slsb.Greeting,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject) +- queue (class: org.jnp.interfaces.NamingContext) | +- A (class: org.jboss.mq.SpyQueue) | +- testQueue (class: org.jboss.mq.SpyQueue) | +- ex (class: org.jboss.mq.SpyQueue) | +- DLQ (class: org.jboss.mq.SpyQueue) | +- D (class: org.jboss.mq.SpyQueue) | +- C (class: org.jboss.mq.SpyQueue) | +- B (class: org.jboss.mq.SpyQueue) +- topic (class: org.jnp.interfaces.NamingContext) | +- testDurableTopic (class: org.jboss.mq.SpyTopic) | +- testTopic (class: org.jboss.mq.SpyTopic) | +- securedTopic (class: org.jboss.mq.SpyTopic) +- console (class: org.jnp.interfaces.NamingContext) | +- PluginManager (proxy: $Proxy49 implements interface org.jboss.console.manager.PluginManagerMBean) +- UIL2ConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef) +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory) +- UILConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef) +- SubBean (class: org.jnp.interfaces.NamingContext) | +- local (proxy: $Proxy134 implements interface beans.SubBeanInterface,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject) +- QueueConnectionFactory (class: org.jboss.naming.LinkRefPair) +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory) Stacktrace: javax.naming.InitialContext@b6ece5 log4j:WARN No appenders could be found for logger (org.jnp.interfaces.NamingContext). log4j:WARN Please initialize the log4j system properly. Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: jboss-server:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server jboss-server:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server jboss-server:1099 [Root exception is java.net.UnknownHostException: jboss-server]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589) at javax.naming.InitialContext.lookup(Unknown Source) at Main.main(Main.java:16) Caused by: javax.naming.CommunicationException: Failed to connect to server jboss-server:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server jboss-server:1099 [Root exception is java.net.UnknownHostException: jboss-server]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387) ... 4 more Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server jboss-server:1099 [Root exception is java.net.UnknownHostException: jboss-server] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243) ... 5 more Caused by: java.net.UnknownHostException: jboss-server at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source) at java.net.InetAddress.getAddressFromNameService(Unknown Source) at java.net.InetAddress.getAllByName0(Unknown Source) at java.net.InetAddress.getAllByName(Unknown Source) at java.net.InetAddress.getAllByName(Unknown Source) at java.net.InetAddress.getByName(Unknown Source) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:76) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239) ... 5 more And the Client is a standalone client. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116095#4116095 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116095

16 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: about component Name convention

by Fangzx

When I use name like this: | @Name("app.userService") | @AutoCreate | class UserService extends BaseService { | .... | I must use the component like this: | @In("app.userService") UserService userService | But when I use name in Entity class like this: | @Entity | @Name("app.user") | @Scope(SESSION) | @Table(name="App_User") | class User implements Serializable | { | I can still use the User component like this: | @In(required = false) | @Out(required = false, scope = SESSION) | User user; | Why JBoss Seam don't matter about the name 'app.user'? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116093#4116093 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116093

16 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Oddness - javax.persistence.EntityNotFoundException

by damianharvey

I've just run into this problem again and am posting back here so I don't forget again. When trying to delete an entity that has existing relationships (eg. OneToMany) you have to ensure that you clear the collection before removing the object. eg:public void deleteGroup(Group group) { | | //where the relationship btw a 'User' and a 'Group' is maintained in a 'UserGroupList' | | group.getUserGroupLists().clear(); | entityManager.remove(group); | } Cheers, Damian. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116092#4116092 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116092

16 years, 4 months

1
0
0 / 0

[EJB/JBoss] - Re: Jboos Lookup

by jaikiran

Which version of JBoss are you using? Is your client a standalone java class? Post the entire exception stacktrace and also the exact contents of the JNDI tree as you see from the jmx-console. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116091#4116091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116091

16 years, 4 months

1
0
0 / 0

[JBoss jBPM] - How can Jbpm exchange data with external system?

by fengzhi

hello everybody, I have read the jbpm jpdl tutorial, it told a little about external system. And I have some questions about data exchange between Jbpm and external system. I understand an external system can be a human or another applications. E.g. a process is being in the state-node and waiting for a signal of an external system to continue to next node. 1. A human, who at the web application clicks on a button, which sends a signal to the Jbpm, with token.signal(). 2. Another application, how can it send a signal to Jbpm? And where is the interface in Jbpm for data exchange with external system? How can I realise it? Please give me some information about it or what I have to read or lern to implement this function? Sinceres thanks for your help. regards, Fengzhi View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116090#4116090 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116090

16 years, 4 months

1
0
0 / 0

[JBoss Messaging] - Re: Different Message id for each listener

by timfox

I don't understand your use case. If your subscriptions are non durable, then they won't survive failure, therefore saying order is maintained is meaningless. Maybe you need to explain your scenario in more detail... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116089#4116089 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116089

16 years, 4 months

1
0
0 / 0

[JBoss Messaging] - Re: Different Message id for each listener

by assaf49

thanks for your quick reponse :) No, our Topic listeners are NOT durable, we must maintain order of messages only whilst listeners ARE Connected. I reckon that ordering (whilst Connected) is possible for such undurable listeners right? This seems like an important feature. Do you plan to support it (it will spare us a lot of trouble :)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116088#4116088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116088

16 years, 4 months

1
0
0 / 0

[JBoss Messaging] - Re: Different Message id for each listener

by timfox

I'm assuming you are using durable subscriptions on your topic, or they won't survive failure anyway. On that assumption, order after failover will be maintained. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116086#4116086 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116086

16 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2007