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

[Design of POJO Server] - Re: AbstractDeploymentUnit.getMetaDataFiles()

by bill.burke＠jboss.com

so, VirtualFile.toURL() will return: vfs-file:/.../blah.ear/foo.jar/META-INF/persistence.xml cool? That's of course if the VFS is file based. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979470#3979470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979470

19 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: ClassNotFoundException when running ejb3 clustered in 4.

by pthurmond＠jboss.com

Thanks Brian. The application behaves correctly with the query cache disabled. --Phillip View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979466#3979466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979466

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: AbstractDeploymentUnit.getMetaDataFiles()

by scott.stark＠jboss.org

"bill.burke(a)jboss.com" wrote : "scott.stark(a)jboss.org" wrote : I have always thought jar urls were fundamentally flawed since they never have dealt with nested jars, and mix content with another protocol. Its also not really a protocol issue. I would like jar urls to disappear and whether or not a file was a compressed archive be a detail of the VFS. | | | | That's great you want to do this, but various SPIs in JavaEE5 require passing valid URLs. I'm running into this problem right now with nested jars within an EAR. PU need to pass in URL of the persistence.xml file but it is fucked up URL: | | jar:file:/.../foo.ear!/ejb.jar/META-INF/persistence.xml | | URL handler tries to open ejb.jar/META-INF/persistence.xml as a JarEntry within foo.ear (which its not obviously) | | Are we going to do: | | vfs:file:/.../foo.ear/ejb.jar/META-INF/persistence.xml? | | Is this something I can work on please as it is blocking me. | | Thanks, | | Bill Its something you can work on now that the structural deployer related vfs issues have been done. Instead of going with another nested url syntax, we may want: vfs-file:/.../foo.ear/ejb.jar/META-INF/persistence.xml so that URL/URI accessors like getPath, getHost, etc. work. They don't work with opaque url syntaxes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979465#3979465 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979465

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - jboss-head updated for vfs changes

by scott.stark＠jboss.org

jboss5 trunk has been updated for VFS changes to the visitor recursion and isAttribute removal. Code that previously was using VisitorAttributes.setRecurseArchives(false): | VisitorAttributes va = new VisitorAttributes(); | va.setRecurse(true); | va.setLeavesOnly(true); | va.setRecurseArchives(false); | FilterVirtualFileVisitor visitor = new FilterVirtualFileVisitor(filter, va); | Now needs to specify a recursion filter. To exclude known jar achive suffixes the following can be done: | VisitorAttributes va = new VisitorAttributes(); | va.setLeavesOnly(true); | SuffixesExcludeFilter noJars = new SuffixesExcludeFilter(JarUtils.getSuffixes()); | va.setRecurseFilter(noJars); | FilterVirtualFileVisitor visitor = new FilterVirtualFileVisitor(filter, va); | The server is booting fine with these changes. I'm still validating that there is no extra recursion/components being created because of these changes. The next refactoring I'm testing is the structural deployer changes to produce a StructuredMetaData object rather than DeploymentContexts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979462#3979462 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979462

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: removing isArchive()

by scott.stark＠jboss.org

isArchive has been removed. At best it was a hint about how recursion should be handled, but this is not an inherent property of a given VirtualFile implementation. Its a notion of the visitor. Now recursion is completely controlled by a separate VirtualFileFilter. See "Changed recurse notions in VisitorAttributes, VFS.visit": http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92962 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979458#3979458 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979458

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: refactoring visitor in VFS

by scott.stark＠jboss.org

This has been done. See Changed recurse notions in VisitorAttributes, VFS.visit: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92962 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979457#3979457 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979457

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: AbstractDeploymentUnit.getMetaDataFiles()

by scott.stark＠jboss.org

This is fixed. See the FileVFSUnitTestCase testClassScanFilesonly and testFilesOnlyJar tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979456#3979456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979456

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: POJOization of config elements

by bstansberry＠jboss.com

anonymous wrote : | Why doesn't the standard BL impl we ship with (there is only one) also come with a BLC subclass, could be a good example since Properties are ugly and we don't really want to promote that mechanism anyway? | I've written one. Also, the same pattern applies to CacheLoaders (substitute CacheLoaderConfig for BuddyReplicationConfig and IndividualCacheLoaderConfig for BuddyLocatorConfig.) I've got specific IndividualCacheLoaderConfig subclasses created for all the standard CacheLoader impls as well. anonymous wrote : | Why do we need to support Properties anyway, for 2.0.0 we don't need to be backward-compat ... | We still want to support creation of a config using the old 1.x format and XmlConfigurationParser, don't we? Otherwise we require use of the MC and a -beans.xml file, even outside the AS. The XmlConfigurationParser approach can't handle arbitrary sets of XML elements (at least not without a lot of work), hence the use of Properties as a workaround. Even if we decide to require use of the MC in 2.0.0.GA, leaving in Properties support for now makes it easier to transition. We can strip it out later (e.g. after alpha). FYI, I've been proceeding along the lines discussed on this thread trying to see if there are problems. Here's where it stands: 1) Custom config classes created for all NextMemberBuddyLocator, and all the CacheLoader impls, and impls designed to use them. 2) AFAICT, there are no testsuite regressions using this code (i.e. all the existing tests that use properties for configuration pass. The various config classes all know how to convert from the Properties format to POJO properties, so the existing testsuite is excercising this stuff fairly well. TODO: 1) Continue discussion. 2) If it sounds good, continue along same lines with eviction policies. This might be easier, as it looks like the eviction policy config is already somewhat done along these lines; e.g. a lot of specialized config classes exist. 2) Set up -beans.xml files for use in the AS to test building the standard cache configs used in the AS. That's provides a basic test of the MC approach. 3) Round out the JBC test suite with more formal tests of the MC approach. I'd say that can be done post-alpha. How's that sound? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979455#3979455 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979455

19 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: ClassNotFoundException when running ejb3 clustered in 4.

by bstansberry＠jboss.com

Is the Hibernate query cache enabled? If it is, does the problem go away if it is disabled? I've added a JIRA for a problem with the query cache that I suspect is your issue: http://jira.jboss.com/jira/browse/JBCLUSTER-150 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979448#3979448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979448

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: POJOization of config elements

by manik.surtani＠jboss.com

Ok, cool. This sounds good. anonymous wrote : | | A custom BL impl only used with the MC may not ever concern itself with the Properties; but the standard ones we ship w/ JBC need to be able to configure themselves via Properties. | Why doesn't the standard BL impl we ship with (there is only one) also come with a BLC subclass, could be a good example since Properties are ugly and we don't really want to promote that mechanism anyway? Why do we need to support Properties anyway, for 2.0.0 we don't need to be backward-compat ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979443#3979443 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979443

19 years, 5 months

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 October 2006