October 2008 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Update to jpa-deployers

by bstansberry＠jboss.com

Yeah, me too, except for the first time I touch a library and am totally unaware of whatever ticking timebombs may be associated with it. :) [OT] I'll get this checked in in the morning. With this and other stuff I've been doing, the ejb3 clustering testsuite will be down to 4 failures, due to 2 causes, one at least of which is just a need to tweak the test. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183083#4183083 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183083

16 years

1
0
0 / 0

[Design of POJO Server] - Re: appclient classpath additions for mc usage

by ALRubinger

"jaikiran" wrote : I had to add the %JBOSS_HOME%\server\default\lib\jboss-ejb3-core.jar because the %JBOSS_HOME%\client\jboss-ejb3-core-client.jar does not contain one of the required classes present in jboss-ejb3-core.jar. I see this also came up on the EJB3 User's Forum. Do you know which classes are missing from jboss-ejb3-client.jar? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183080#4183080 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183080

16 years

1
0
0 / 0

[Design of POJO Server] - Re: Update to jpa-deployers

by ALRubinger

"bstansberry(a)jboss.com" wrote : Any objections to that? In a perfect world we'd have mechanism that allowed us to keep everything in sync. As a general rule I update without question whenever necessary. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183078#4183078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183078

16 years

1
0
0 / 0

[Design of POJO Server] - Update to jpa-deployers

by bstansberry＠jboss.com

FYI, a fix for https://jira.jboss.org/jira/browse/JBAS-6111 requires an update to jpa-deployers. The pom for jpa-deployers is currently out of date w/ respect to the AS component-matrix pom; most significant difference is hibernate-entitymanager is still at 3.3.2 while the AS uses 3.4.0. A test I wrote for JBAS-6111 needs 3.4.0 in order to work, and even ignoring that I think jpa-deployers dependencies should be brought in sync w/ the AS. Any objections to that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183074#4183074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183074

16 years

1
0
0 / 0

[Design of EJB 3.0] - Class required in EJB3 application client launcher not prese

by jaikiran

The %JBOSS_HOME%\client\jboss-ejb3-core-client.jar contains only a subset of the classes present in %JBOSS_HOME%\server\default\lib\jboss-ejb3-core.jar. For ex: org.jboss.ejb3.DependencyPolicy class is not present in the client jar. While running the application client container to inject EJB in an application client https://www.jboss.org/community/docs/DOC-12835 i had to include %JBOSS_HOME%\server\default\lib\jboss-ejb3-core.jar in the classpath of the client. Is this expected? Or should the client folder contain the relevant jar files with this (and other related) class? There's a related discussion about the jars required for app client launcher here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=139904 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183066#4183066 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183066

16 years

1
0
0 / 0

[Design of POJO Server] - Re: appclient classpath additions for mc usage

by jaikiran

Apart from the ones listed in your post, while trying to get the EJB injection working (through -launcher org.jboss.ejb3.client.ClientLauncher) in application client https://www.jboss.org/community/docs/DOC-12835, i also had to add: %JBOSS_HOME%\client\jboss-metadata.jar %JBOSS_HOME%\lib\jboss-kernel.jar %JBOSS_HOME%\lib\jboss-xml-binding.jar %JBOSS_HOME%\lib\jboss-vfs.jar %JBOSS_HOME%\server\default\lib\jboss-ejb3-core.jar I had to add the %JBOSS_HOME%\server\default\lib\jboss-ejb3-core.jar because the %JBOSS_HOME%\client\jboss-ejb3-core-client.jar does not contain one of the required classes present in jboss-ejb3-core.jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183065#4183065 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183065

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: new QueueBrowser implementation

by timfox

We also need some core integration tests that test the new browsing implementation. This is a general thing when writing new stuff on core - we need integration tests. As I mentioned before don't worry too much about the easymock tests, they're not so important. For browsing I would expect to see: Browsing with and without selectors. Verifying messages don't get acknowledged Browsing with multiple browsers on same queue Verifying calling acknowledge on message does nothing etc Replication with browsing is also currently broke, although this will be hard to get it working with the copying technique - we'll have to wait for the iterator for that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183059#4183059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183059

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: new QueueBrowser implementation

by timfox

There were a few more issues too: 1) The copy queue was being created using the createQueue method which would also bind it in the post office. This is unnecessary - all we want is a simple in memory copy we can browse 2) The queueCopyLock was unnecessary - the list() method on Queue is already synchronized. 3) New references were being created before adding them to the copy queue. Since the browser queue refs would never get acknowledged, this would prevent the messages from ever getting deleted from the journal. I have fixed the code and committed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183042#4183042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183042

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: new QueueBrowser implementation

by timfox

Looking at your latest commit, I notice you added a method on the public client session api "createQueueCopy" - why is this necessary? Whilst, as a temporary measure the queue needs to be copied before browsing, there is no need for this to be exposed on the client or the wireformat, this should just be an internal implementation detail, when creating the browser on the server. I'm a bit baffled as to why you chose to do it this way....... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183041#4183041 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183041

16 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Default JNDI naming scheme in EJB3.0 and possible confli

by jaikiran

Thinking more about this, the conflict can arise even when there are 2 beans with the same classname (but different package names) in the same jar. Ex: MyApp.ear/Single.jar package org.myapp.business; | | @Stateless | public class ManagerBean implements org.myapp.business.Manager { | | } package org.myapp.persistence; | | @Stateless | public class ManagerBean implements org.myapp.persistence.Manager { | | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183030#4183030 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183030

16 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008