May 2010 - jboss-user - Jboss List Archives

Re: [jboss-user] [JBoss Tools] - Installing JBoss Tools on Eclipse 3.6 RC

by Maxim Areshkau

Maxim Areshkau [http://community.jboss.org/people/mareshkau] replied to the discussion "Installing JBoss Tools on Eclipse 3.6 RC" To view the discussion, visit: http://community.jboss.org/message/544454#544454 -------------------------------------------------------------- Hi Karsten, We haven't moved yet on eclipse 3.6, and will do it ASAP. So to use JBoss Tools you need eclipse 3.5 -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544454#544454] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [jBPM Development] - JBPM-2414 and JBPM-2506

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "JBPM-2414 and JBPM-2506" To view the discussion, visit: http://community.jboss.org/message/544452#544452 -------------------------------------------------------------- What I implemented is that join will terminate all left executions only when join activity will be completed, meaning that all or defined by multiplicity attribute execution have reached join node. So if I got it right this is what discriminator pattern is about?! (Please correct me if I am wrong). In my opinion, process that you described could be quite common so there is rather high probability that end users will encounter it. I would say that it needs to be fixed in 4.4. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544452#544452] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

[JBoss Tools Development] - List of XULRunner Issues Related to Visual Page Editor

by Yahor Radtsevich

Yahor Radtsevich [http://community.jboss.org/people/yradtsevich] modified the document: "List of XULRunner Issues Related to Visual Page Editor" To view the document, visit: http://community.jboss.org/docs/DOC-15275 -------------------------------------------------------------- h2. Known problems in XULRunner 1.9.2 h3. org.mozilla.interfaces.inIFlasher inIFlasher does not work on MacOS. It is needed to show a border around selected elements in VPE. *Workaround:* To show a border on MacOS the following style is used: "border: 2px solid COLOR_NAME !important". But the workaround has a drawback: if the selected elements has its own border, it is not visible. h3. draggesture event XULRunner does not fire 'draggesture' event on Linux. *Workaround:* Special button for Drag&Drop actions is used. Instead of listening to the 'draggesture' events, VPE listens to the 'mousedown' event on this button. h3. org.mozilla.interfaces.nsIDragService.invokeDragSession(...) The method invokeDragSession works differently on Windows and Linux. On Windows it exits *after* the session is ended. On Linux it exits *immediately*. The following snippet illustrates this: document.addEventListener("dragstart", new nsIDOMEventListener() { nsISupports queryInterface(String uuid) { return null; } void handleEvent(nsIDOMEvent event) { nsIDragService dragService = (nsIDragService) Mozilla.getInstance().getServiceManager() .getServiceByContractID("@mozilla.org/widget/dragservice;1", nsIDragService.NS_IDRAGSERVICE_IID); System.out.println("BEFORE invokeDragSession"); dragService.invokeDragSession(node, transferables, null, nsIDragService.DRAGDROP_ACTION_MOVE | nsIDragService.DRAGDROP_ACTION_COPY | nsIDragService.DRAGDROP_ACTION_LINK); System.out.println("AFTER invokeDragSession"); } }, false); document.addEventListener("dragend", new nsIDOMEventListener() { nsISupports queryInterface(String uuid) { return null; } void handleEvent(nsIDOMEvent event) { System.out.println("dragend"); } }, false); document.addEventListener("dragover", new nsIDOMEventListener() { nsISupports queryInterface(String uuid) { return null; } void handleEvent(nsIDOMEvent event) { System.out.println("dragover"); } }, false); * Windows output:* > BEFORE invokeDragSession > dragover > dragover > ... > dragover > dragend > AFTER invokeDragSession * Linux output:* > BEFORE invokeDragSession > AFTER invokeDragSession > dragover > dragover > ... > dragover > dragend -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-15275] Create a new document in JBoss Tools Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [JBoss Web Services] - Can the jboss ws support multi-porttype in one wsdl

by Lukas Jungmann

Lukas Jungmann [http://community.jboss.org/people/jlukas%40redhat.com] replied to the discussion "Can the jboss ws support multi-porttype in one wsdl" To view the discussion, visit: http://community.jboss.org/message/544448#544448 -------------------------------------------------------------- To get all interfaces from mentioned wsdl you need to pass '-e' option to wsprovide: {code}wsconsume.sh -k -e http://www.webservicex.net/BibleWebservice.asmx?wsdl http://www.webservicex.net/BibleWebservice.asmx?wsdl{code} -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544448#544448] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [jBPM Development] - JBPM-2414 and JBPM-2506

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "JBPM-2414 and JBPM-2506" To view the discussion, visit: http://community.jboss.org/message/544446#544446 -------------------------------------------------------------- H Maciej, I think the point is whether we should achieve the discriminator design pattern. In discriminator design pattern, the join node will end split executions when they arrived join node, it do not terminate them while the first of execution arrived join node. Indeed, it will increase the complex level of implements. So I think we could terminate all other executions in jBPM 4.4. And think about other scenarios in the future. By the way, I had met the wrong behaviour you mentained. There were two managers in a department. When a contact arrived, both of them need review it. But if one of them is off the office, the process should not wait, the process will continue to the next step when one of them review it. And if the other manager come back, he need review the contact again and let the process go to next step again. In my opinion, this process is totally strange, so we neednot achieve it in jPDL. :) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544446#544446] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [EJB 3.0] - Possible Deadlock Jboss 4.2.3

by Daniel Cullender

Daniel Cullender [http://community.jboss.org/people/cullendw] replied to the discussion "Possible Deadlock Jboss 4.2.3" To view the discussion, visit: http://community.jboss.org/message/544443#544443 -------------------------------------------------------------- False Alarm, The backlog occurred again, so the java version was not the issue. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544443#544443] Start a new discussion in EJB 3.0 at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [EJB 3.0] - EJB3 Deployment Error in JBoss 6.0.0.M1

by jaikiran pai

jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion "EJB3 Deployment Error in JBoss 6.0.0.M1" To view the discussion, visit: http://community.jboss.org/message/544437#544437 -------------------------------------------------------------- > Bhaswar Goswami wrote: > > Application runs and works well, but I can see when I deploy the application there are two interesting things in form of Warning and Error > > 2010-05-21 06:31:49,906 WARN [org.hibernate.ejb.Ejb3Configuration] (HDScanner) Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. > You can ignore that WARN message. > Bhaswar Goswami wrote: > > > 2010-05-21 06:31:49,906 ERROR [STDERR] (HDScanner) URL: jar:file:/D:/AppServers/jboss-6.0.0.M1/server/default/deploy/slsbsecure.jar!/ > META-INF/orm.xml > **/*.hbm.xml Did you remove any part from the ERROR message or exception stacktrace or is it only this much? I don't know what that ERROR message is trying to convey. P.S: Maybe you want to try the latest available 6.0.0.M3? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544437#544437] Start a new discussion in EJB 3.0 at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [EJB 3.0] - Possible Deadlock Jboss 4.2.3

by Daniel Cullender

Daniel Cullender [http://community.jboss.org/people/cullendw] replied to the discussion "Possible Deadlock Jboss 4.2.3" To view the discussion, visit: http://community.jboss.org/message/544434#544434 -------------------------------------------------------------- Just an update on this : We have used profilers and every trick under the sun to determine what is happening. We have found that we may not actually have a deadlock at all, but the jvm slows down acutely and causes backlogs in our cache queues. (memory and all other external indicators look ok). We have downgraded to java 6 update 14 (we were using the latest update 20) and it seems to be fine now. I will continue monitoring the situation, and when I am convinced that it is the latest update that caused the issue, I will take it up with Oracle. As I must stress now, this is only speculation. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544434#544434] Start a new discussion in EJB 3.0 at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

[JBoss Messaging] - problem executing jdbc statement via mdb

by Jose Miguel Loor

Jose Miguel Loor [http://community.jboss.org/people/jmiguel77] created the discussion "problem executing jdbc statement via mdb" To view the discussion, visit: http://community.jboss.org/message/544431#544431 -------------------------------------------------------------- hi i have an odd issue trying to execute a callable statement via a MessageDrivenBean. the scenario is like this: i have @Stateles session bean that produces the message @Stateless public class MensajesServiceImpl implements MensajesService, MensajesServiceRemote { @Resource(mappedName = "java:/JmsXA") private ConnectionFactory connectionFactory; @Resource(mappedName = "queue/balanceComprobacionQueue") private Queue balanceComprobacionQueue; public void llamarEjecucionArbolCuenta(final Integer periodo) throws JMSException { QueueConnectionFactory qcf = (QueueConnectionFactory) connectionFactory; QueueConnection queueConnection = qcf.createQueueConnection(); QueueSession queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); QueueSender queueSender = queueSession .createSender(balanceComprobacionQueue); ObjectMessage message = queueSession.createObjectMessage(); message.setIntProperty(Constantes.PERIODO_MESSAGE_PROPERTY, periodo); queueSender.send(message); } } the message is received by the MDB @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/balanceComprobacionQueue") }) public class BalanceComprobacionMessageDrivenBean implements MessageListener { @EJB private BalanceComprobacionService balanceComprobacionService; @Override public void onMessage(final Message message) { try { if (message instanceof ObjectMessage) { ObjectMessage periodoMessage = (ObjectMessage) message; Integer periodo = periodoMessage .getIntProperty(Constantes.PERIODO_MESSAGE_PROPERTY); balanceComprobacionService.ejecutarArbolCuentas(periodo); } } catch (JMSException e) { e.printStackTrace(); } catch (EjecucionFallidaException e) { e.printStackTrace(); } } } as you can see, in the MDB i am injecting another stateless session bean (BalanceComprobacionService) and calling a method registered in that session bean; the method i am executing is this @Stateless public class BalanceComprobacionDaoImpl implements BalanceComprobacionDao { @Resource(mappedName = "java:/myDataSource") private DataSource dataSource; @Override public void ejecutarArbolCuentas(final Integer periodo) throws EjecucionFallidaException { Connection connection = null; try { String sql = "{ call arbol_cuenta(?) }"; connection = dataSource.getConnection(); CallableStatement statement = connection.prepareCall(sql); statement.setInt(1, periodo); statement.execute(); } catch (SQLException e) { throw new EjecucionFallidaException(e); } finally { try { connection.close(); } catch (SQLException e) { throw new EjecucionFallidaException(e); } } } } everything works fine, until the statement.execute(); at this point, the execution just stops; it doesn't give any error, exception, nor in the jboss server or the database, it just stops right there i am using jboss 4.2.3.GA with jdk 1.6_0.15; the database is postgresql 8.3 i don't think the problem is related with the database or the function i am calling, because if i test the BalanceComprobacionDaoImpl by itself, it works ok, it's just when i test the whole process that it stops at the callable statement execution please help, thanks -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544431#544431] Start a new discussion in JBoss Messaging at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

1
0
0 / 0

Re: [jboss-user] [jBPM Development] - JBPM-2414 and JBPM-2506

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "JBPM-2414 and JBPM-2506" To view the discussion, visit: http://community.jboss.org/message/544429#544429 -------------------------------------------------------------- Hi HuiSheng, Thanks for reference. I am wondering what we could gain with this new attribute?! Since either way execution must be ended regardless of if it has timer or not. Because if we leave such execution (with timer on transition) then such execution will be fired as soon as timer goes off. Consider following scenario: - for creates four branches all of them goes to a task - multiplicity on join is set to 2 - users complete first two tasks meaning join will move on with the execution - join signals based on the multiplicity - 2 execution must be joined to continue - next users complete two remaining tasks (from the fork that are still active) - since multiplicity is set to 2 join will execute again - which in my opinion is wrong behavior My fix for this was ending all remaining forked execution only if multiplicity attribute was used so it does not break any other cases - as Ronald has pointed out in jira. What do you think about it? Maybe I am missing something ... so please correct me if I am wrong. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544429#544429] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 1 month

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 May 2010