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

[Design of JBoss ESB] - Re: Maven ESB plugin

by Kevin.Conner＠jboss.com

Try specifying a scope of 'provided'. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146541#4146541 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146541

18 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Maven ESB plugin

by beve

Hi, do you have a dependency setup in your pom for jbossesb-rosetta? Could you post it if you do? Thanks, Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146540#4146540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146540

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Function of jboss-aspect-library-jdk50.jar

by wolfc

What's the function of this jar? Shouldn't AS consume a jboss-aspects assembly or individual artifacts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146538#4146538 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146538

18 years, 1 month

1
0
0 / 0

Delivery Notification <antonette.bell@umcsn.com>

by Postmaster＠lists.jboss.org

This is a delivery status notification, automatically generated by MTA umcsecmx1.umcsn.com on Thu, 24 Apr 2008 07:30:48 -0700 Regarding recipient(s) : antonette.bell(a)umcsn.com Delivery status : Failed. Message could not be delivered to domain <umcsn.com> .Error while sending data. MTA Response :550 The original message headers are included as attachment.

18 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Maven ESB plugin

by Andre1001

Hi beve, I did exactly what you told and it generates a "lib" directory inside my package with jbossesb-rosetta.jar. Is it the recommended approach? If not, is there a Maven parameter in order to generate a package whitout "lib"!? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146536#4146536 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146536

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

by scott.stark＠jboss.org

We could do that. It requires more changes to the current ext-api org.jboss.ejb3.jndipolicy api, possibly just dropping it in favor of the metadata version. Just need to make the call one way or the other. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146533#4146533 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146533

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

by alex.loubyansky＠jboss.com

I would make the binding policy responsible for the jndi names and give it access to the metadata. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146528#4146528 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146528

18 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

by scott.stark＠jboss.org

The DefaultJndiBindingPolicy does not accept the metadata. Rather it takes a summary of the ejb deployment/bean in question: | public interface DefaultJndiBindingPolicy | { | /** | * Returns the JNDI name that should be assigned to this deployment | * based on the information contained in the specified summary | * | * @param summary | * @return | */ | String getJndiName(EjbDeploymentSummary summary); | | String getDefaultRemoteJndiName(EjbDeploymentSummary summary); | | String getDefaultRemoteHomeJndiName(EjbDeploymentSummary summary); | | String getDefaultLocalHomeJndiName(EjbDeploymentSummary summary); | | String getDefaultLocalJndiName(EjbDeploymentSummary summary); | } | public class EjbDeploymentSummary | { | // Instance Members | private String deploymentName; | private String deploymentScopeBaseName; | private String ejbName; | private String beanClassName; | private boolean isLocal; | private boolean isStateful; | private boolean isHome; | private boolean isService; | private ClassLoader loader; | ... | // accessors omitted | } | The determineJndiName(EjbDeploymentSummary) on the base class just implements the default name based on the DefaultJndiBindingPolicy. The entity and session bean metadata still have the determineJndiName() which has the old logic as well as an overriden determineJndiName(EjbDeploymentSummary) which looks at the other sources of jndi names before defaulting to the superclass policy version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146525#4146525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146525

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: GA releases of mc projects?

by kabir.khan＠jboss.com

Having dug a bit more into the dependencies and seeing where they are used from, all we need to bundle in the standalone release is jboss-mdr and jboss-reflect, the others are needed for integration into jboss 5, but I guess by the time AS 5 is released we can release a new AOP version. So, can we have GA releases of jboss-mdr and jboss-reflect as discussed in Neuchatel? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146524#4146524 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146524

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Resource GC problem

by harish43

Tim, Do you know which version of JBoss Messaging contains the fix you mention? Also is there a corresponding fix in JBoss Remoting as well? If so in which version is it? We are experiencing similar issues when load testing with JBoss Messaging with usage pattern of JMS connections being very similar (lookup factory, lookup queue, connect to queue, open session, send message, close connection) but we are using a JMS connection max-pool-size of 20 as defined in the tx-connection-factory in jms-ds.xml. Our environment is : JBM 1.4.0 SP3 JBoss AS 4.2.2 GA JDK 1.5.0_06 Redhat Linux MySQL for JMS persistence Sybase for data persistence As mentioned by Kevin Conner the BisocketServerInvoker$ControlMonitorTimerTask and BisocketClientInvoker and HashMaps are growing in number and size throughout the test and never getting GC'd. Any help is appreciated. Harish. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146523#4146523 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146523

18 years, 1 month

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-dev-forums April 2008