March 2010 - jboss-dev-forums - Jboss List Archives

[JBoss Microcontainer Development] New message: "Re: ClassLoadingAdmin"

by Adrian Brock

JBoss development, A new message was posted in the thread "ClassLoadingAdmin": http://community.jboss.org/message/529880#529880 Author : Adrian Brock Profile : http://community.jboss.org/people/adrian@jboss.org Message: -------------------------------------------------------------- I fixed the NPE by throwing an error. I could maybe change the LifeCycle.resolve() methods to return a boolean saying whether the resolve actually worked or not? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529880#529880

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Trivial vfs-3.0.x manifest access fails"

by Thomas Diesler

JBoss development, A new message was posted in the thread "Trivial vfs-3.0.x manifest access fails": http://community.jboss.org/message/529856#529856 Author : Thomas Diesler Profile : http://community.jboss.org/people/thomas.diesler@jboss.com Message: -------------------------------------------------------------- Thanks -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529856#529856

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Trivial vfs-3.0.x manifest access fails"

by Ales Justin

JBoss development, A new message was posted in the thread "Trivial vfs-3.0.x manifest access fails": http://community.jboss.org/message/529852#529852 Author : Ales Justin Profile : http://community.jboss.org/people/alesj Message: -------------------------------------------------------------- > I added this > > MountOwner owner = *new* VirtualFileOwner(root); > Automounter.mount(owner, root); > > > > > which seems to work. > > > > Is this right? > > Is there some cleanup needed? No need for MountOwner, Automounter::mount takes Object, and wraps it -- same as you did explicitly. Yes, you need to preform explicit cleanup as well -- Automounter::mount returns Closeable cleanup handle. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529852#529852

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Trivial vfs-3.0.x manifest access fails"

by Thomas Diesler

JBoss development, A new message was posted in the thread "Trivial vfs-3.0.x manifest access fails": http://community.jboss.org/message/529850#529850 Author : Thomas Diesler Profile : http://community.jboss.org/people/thomas.diesler@jboss.com Message: -------------------------------------------------------------- No, I do not want to see some other bit of undocumented code. Instead, I want to be directed to the jboss-vfs documentation. Perhaps you like to confirm that this is indeed on the roadmap. https://jira.jboss.org/jira/browse/JBVFS-113 -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529850#529850

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Trivial vfs-3.0.x manifest access fails"

by Thomas Diesler

JBoss development, A new message was posted in the thread "Trivial vfs-3.0.x manifest access fails": http://community.jboss.org/message/529846#529846 Author : Thomas Diesler Profile : http://community.jboss.org/people/thomas.diesler@jboss.com Message: -------------------------------------------------------------- I added this MountOwner owner = new VirtualFileOwner(root); Automounter.mount(owner, root); which seems to work. Is this right? Is there some cleanup needed? Please document the correct usage of the API. Good javadoc with code examples on how to use the API is the minimum. Alternatively, you could provide a wiki or docbook. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529846#529846

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Re: Trivial vfs-3.0.x manifest access fails"

by Ales Justin

JBoss development, A new message was posted in the thread "Trivial vfs-3.0.x manifest access fails": http://community.jboss.org/message/529838#529838 Author : Ales Justin Profile : http://community.jboss.org/people/alesj Message: -------------------------------------------------------------- VFS3 requires *explicit* mount of non-plain files; e.g. zip, gzip, ... See AbstractVFSArchiveStructureDeployer in Deployers on how this is done, or VFS tests. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529838#529838

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] New message: "Trivial vfs-3.0.x manifest access fails"

by Thomas Diesler

JBoss development, A new message was posted in the thread "Trivial vfs-3.0.x manifest access fails": http://community.jboss.org/message/529834#529834 Author : Thomas Diesler Profile : http://community.jboss.org/people/thomas.diesler@jboss.com Message: -------------------------------------------------------------- When trying to access the manifest from a jar, I get Caused by: java.io.FileNotFoundException: /home/tdiesler/svn/jboss-osgi/trunk/testsuite/example/target/test-libs/example-simple.jar/META-INF/MANIFEST.MF (Not a directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at org.jboss.vfs.spi.RealFileSystem.openInputStream(RealFileSystem.java:67) at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:225) at org.jboss.osgi.vfs30.VirtualFileAdaptor30.openStream(VirtualFileAdaptor30.java:106) at org.jboss.osgi.vfs.VFSUtils.getManifest(VFSUtils.java:49) at org.jboss.osgi.spi.util.BundleInfo.<init>(BundleInfo.java:109) Essentially I do VirtualFile root = VFS.getChild(url); VirtualFile manifest = root.getChild(JarFile.MANIFEST_NAME); InputStream stream = manifest.openStream(); -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529834#529834

16 years, 1 month

1
0
0 / 0

[jBPM Development] New message: "Re: presumable bug JPDL 4 Graphical Editor, erase <field>"

by Tomas Blohm

JBoss development, A new message was posted in the thread "presumable bug JPDL 4 Graphical Editor, erase <field>": http://community.jboss.org/message/529822#529822 Author : Tomas Blohm Profile : http://community.jboss.org/people/tobl Message: -------------------------------------------------------------- I have the same problem. This is kind of a big issue since one can't let anyone who is not familiar with the source work with processes. Can we expect any feedback on this? /Tomas -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529822#529822

16 years, 1 month

1
0
0 / 0

[EJB 3.0 Development] New message: "Re: lookup for remote bean - failure (only from eclipse)"

by Wolfgang Knauf

JBoss development, A new message was posted in the thread "lookup for remote bean - failure (only from eclipse)": http://community.jboss.org/message/529677#529677 Author : Wolfgang Knauf Profile : http://community.jboss.org/people/WolfgangKnauf Message: -------------------------------------------------------------- Hi, I think for an application client, you need this value for the URL_PKG_PREFIXES property: props.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming.client"); If this does not work: anything special in your unit test setup? I have a small unit test sample without problems (but I lookup the bean in the ENC, not by global name) Hope this helps Wolfgang -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529677#529677

16 years, 1 month

1
0
0 / 0

[JBoss ESB Development] New message: "Re: Camel integration input requested"

by Edgar Silva

JBoss development, A new message was posted in the thread "Camel integration input requested": http://community.jboss.org/message/529672#529672 Author : Edgar Silva Email : edgarsilva(a)gmail.com Profile : http://community.jboss.org/people/edgar.silva Message: -------------------------------------------------------------- Hi David, This is very interesting, and I also vote for this idea. I've been doing some initial working on this at http://code.google.com/p/breakingwoods. What we have done for awhile is basically to listen some routes (URIs) from Apache Camel. I believe some components can be just "Event Producers", but several others can be even the final destinations, for instance, I am figuring out an way to create a kind of "CamelNotifier", that can use the ready Camel infrastructure. Looking from a developer perspective, downloading or building the actual Apache Camel Suppor for JBoss ESB 4.7 hosted at breakingwoods, anybody can just add the "Apache Camel Gateway/Listener" according the following XML config in jboss-esb.xml service section: {code:xml} <listener name="ApacheCamel" busidref="ApacheCamel" is-gateway="true"> <property name="gatewayClass" value="org.jboss.soa.esb.listeners.gateway.camel.ApacheCamelListener" /> <property name="protocol-uri" value="irc:mailto:breakingwoods@irc.freenode.net/#esbtest" /> <property name="destination-category" value="sample-apachecamelESBService" /> <property name="destination-name" value="sample-apachecamelESBServiceListener" /> </listener> {code} The class http://code.google.com/p/breakingwoods/source/browse/trunk/jbossesb-apach... , is the listener based on +AbstractThreadedManagedLifecycle+, which is responsible to interact with Camel, the other properties are useful for the following purposes: * protocol-uri - This is the Apache Camel URI that will receive the Events and the message itself, this message will be forwarded to JBoss ESB Services pipelines. + + * destination-category - Service Category that will receive the message arrived from Camel layer * destination-service - The Service that will handle the message arrived from Camel, this service for instance can be a simple Smooks CBR, or anyother able to marshal or unmarshal the message. As David said, Camel is not an ESB, but I consider it a valuable piece for any solution that aims to promote integration in any kind of architecture. Cheers Edgar -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/529672#529672

16 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 March 2010