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

[Design the new POJO MicroContainer] - Re: Changing the way AbstractVFSDeployment serializes root

by alesj

"scott.stark(a)jboss.org" wrote : That saves bytes, but whether or not its going to work depends on the url being usable on the target jvm deserializing the file. I suppose that is true regardless of how serialization is done. | I think this is the right way to do it anyway. Since you are really forcing structure re-creation on target jvm. Where in the case of serializing full VirtualFile, you're depending on the impl details - which in our case you might even get wrong info due to in-memory handling of nested zips, or by-passing some permission control that is enforced on server side. If you would like to have full structure already present, I don't think you would gain much, since you would then 'pay' huge on transport, instead of at re-creation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159258#4159258 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159258

16 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Changing the way AbstractVFSDeployment serializes root

by scott.stark＠jboss.org

That saves bytes, but whether or not its going to work depends on the url being usable on the target jvm deserializing the file. I suppose that is true regardless of how serialization is done. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159250#4159250 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159250

16 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: Unit Tests for Unbinding References from JNDI in EJB3 Pr

by jaikiran

Thanks Andrew. Based on these inputs and the review comments, i have now updated the test case. The updated test case has been attached to the JIRA issue EJBTHREE-1420. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159244#4159244 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159244

16 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - The JBoss JCA container project

by jesper.pedersen

The goal of the JBoss JCA container project is to provide a Plain Old Java Object (POJO) implementation of the Java Connector Architecture (JCA) specification. The implementation is built on top of the JBoss Microcontainer and implemented in Java 5. Overview The implementation should be separated into different modules, so each module can be released separately or in certified bundles. Current module list JCA / Core JCA / JDBC JCA / JMS JCA / Mail JCA / Timer (Quartz) Requirements The new implementation will provide the JBoss projects with: Core implementation based on POJO / microcontainer JCA 1.5 profile JCA 1.6 profile JCA 1.0 profile Connection manager Work manager Deployers Meta-data handling and repository SPI implementation Separate sub-projects JDBC JMS Mail Timer Test-suite for each module (self-contained) Performance-suite for each module (self-contained) Management for each module Statistics for each module (f.ex. avg wait-time for JDBC connection) Integration with the JBoss Application Server Starting points The proof-of-concept implementation or first order of business will of course be the JCA 1.5 profile. Adrian and Vicky has provided a starting point in the jboss-jca project which we should investigate and there are many JIRAs that describes various ideas for each of the modules for this new implementation. JIRA and SVN information will follow. The main wiki page is located at http://wiki.jboss.org/wiki/JBossJCA_POJO Feel free to share ideas, comments or feedback on this project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159242#4159242 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159242

16 years, 1 month

1
0
0 / 0

[Design of EJB 3.0] - Re: @Service and @Consumer in metadata

by emuckenhuber

I have two questions regarding the @Service and @Consumer annotation: 1) a @Service annotated Bean inherits more or less the annotation processing as a @Stateless bean ? 2) the @Consumer annotation defines: | ActivationConfigProperty[] activationConfig() | which is not represented by the JBossConsumerBeanMetaData nor defined in the jboss_5_0.xsd. So should this be added to the metadata and the xml schema? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159237#4159237 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159237

16 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: container integration naming issue

by thomas.diesler＠jboss.com

Currently the container integrations jars translate as follows jbossws-jboss421-3.0.2.GA.jar => jbossws-jboss421.jar jbossws-jboss422-3.0.2.GA.jar => jbossws-jboss422.jar jbossws-jboss423x-3.0.2.GA.jar => jbossws-jboss423.jar jbossws-jboss500Beta4-3.0.2.GA.jar => jbossws-jboss500.jar jbossws-jboss500x-3.0.2.GA.jar => jbossws-jboss501.jar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159214#4159214 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159214

16 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: container integration naming issue

by thomas.diesler＠jboss.com

For container integrations that are used with unreleased container versions (i.e. jbossas/trunk, jbossas/branches/Branch_4_2) we use th e convention that we append 'x' to the container version | <dependency> | <groupId>org.jboss.ws</groupId> | <artifactId>jbossws-jboss423x</artifactId> | <version>3.0.3-SNAPSHOT</version> | </dependency> | <dependency> | <groupId>org.jboss.ws</groupId> | <artifactId>jbossws-jboss500x</artifactId> | <version>3.0.3-SNAPSHOT</version> | </dependency> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159209#4159209 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159209

16 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: Regarding JBoss ESB

by AmbicaSona

I got the solution for this too.... :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159208#4159208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159208

16 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Re: portal clustering problem when using optimistic locking

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : What JGroups version are you using? I'd recommend 2.4.2, which is what is in the latest EAP release (which is also what I'd recommend). Indeed. The latest EAP CP releases, whether 4.2.0.GA_CP03 or 4.3.0.GA_CP01 contain up to date JBC and JGRP releases, see: http://anonsvn.jboss.org/repos/jbossas/tags/JBPAPP_4_2_0_GA_CP03/build/bu... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159171#4159171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159171

16 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Changing the way AbstractVFSDeployment serializes root

by alesj

"scott.stark(a)jboss.org" wrote : That will also change the vfs relative path. Different vfs context should not matter, but being able to access the parent breaks the api usage. | What about this? | private void writeObject(ObjectOutputStream out) throws IOException, URISyntaxException | { | URL url = rootUrl; | if (url == null) | { | VFS vfs = getFile().getVFS(); | url = vfs.getRoot().toURL(); | } | String pathName = path; | if (pathName == null) | pathName = getFile().getPathName(); | | ObjectOutputStream.PutField fields = out.putFields(); | fields.put("rootUrl", url); | fields.put("path", pathName); | out.writeFields(); | } | | private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException | { | ObjectInputStream.GetField fields = in.readFields(); | rootUrl = (URL) fields.get("rootUrl", null); | path = (String) fields.get("path", null); | } | And then having a lazy construction on file. This way a lot less bytes get serialized. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159166#4159166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159166

16 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-dev-forums June 2008