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

[Embedded JBoss Development] - Re: ShrinkWrap Export to File

by ALRubinger

"aslak" wrote : Hey Jaikiran! | | Looks like we have user # 2.. :) | | We're trying to make the apis as convenient as possible to use, so a export option directly to file is probably not a bad idea. | | There is a 'Container' API under development that will have direct support for the Archives themselves. For instance using Jboss Embedded you can deploy the created Archive, so no need to export it to file first. | | ps: The ShrinkWrap API is under change at the moment, as outlined here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161756 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261020#4261020 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261020

16 years, 5 months

1
0
0 / 0

[Embedded JBoss Development] - ShrinkWrap Export to File

by ALRubinger

"Jaikiran" wrote : | I happened to try out the ShrinkWrap (1.0.0-alpha-1) this weekend. | Pretty useful stuff, especially in test case environments :) I read | through the project wiki http://www.jboss.org/community/wiki/ShrinkWrap | and even tried out my own few testcases. Works great! | | One of things that i noticed in my tests was that i kept repeating a | piece of boilerplate code. As shown in the example in your wiki for | exporting jars (wars, ears etc...) we get hold of the InputStream from | the ZipExporter. However, the step of writing out to the file system | using an output stream is left to the client of the API: | | // Export to the Filesystem as a real JAR | | InputStream zipStream = ZipExporter.exportZip(archive); | | // Get a FileOutputStream and then write the contents of "zipStream" to it | | | Was this intentional? In my tests, after exporting, i had to almost | always write out the stream to the file. Although it's not complicated, | clients of the API could probably avoid this extra code if the | ShrinkWrap API added a new API which accepts the File to which the | archive has to be exported? | | Something like: | | void ZipExporter.exportZip(archive, File outputFile) | | | Thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261019#4261019 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261019

16 years, 5 months

1
0
0 / 0

[JBoss Microcontainer Development POJO Server] - Re: Adding a ClassLoader import exclusion filter

by alesj

"jason.greene(a)jboss.com" wrote : What I am talking about would be something like a new excludeImport value which would take precedence over any import (either importAll or via module imports). Where and how would this excludeImport fit in? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261016#4261016 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261016

16 years, 5 months

1
0
0 / 0

[JBoss Transactions Development] - Re: beanifying the config

by adinn

anonymous wrote : | comments? | All sounds utterly reasonable to me. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260992#4260992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260992

16 years, 5 months

1
0
0 / 0

[JBoss ESB Development] - Re: SOAPProxy initialization and deployment ordering

by mvecera＠redhat.com

What about making the lazy initialization optional using a property in the action definition, or even make it possible to read the target WSDL URL from the message? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260987#4260987 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260987

16 years, 5 months

1
0
0 / 0

[JBoss Remoting Development] - Re: JBoss RMI + Serialization performance issue

by ron.sigal＠jboss.com

I moved this question to the Remoting users forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=162611 . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260915#4260915 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260915

16 years, 5 months

1
0
0 / 0

[JBoss Remoting Development] - JBoss RMI + Serialization performance issue

by ron.sigal＠jboss.com

"ravi_eze" wrote : | hi, | | This is w.r.t. http://labs.jboss.com/jbossremoting/docs/benchmark/performance_benchmark.... where comparision between diffarent protocols is done. The page also gives the JUnit code that generated the graphs. we are trying out with 2.5.2. version. | | We are evaluating Java RMI and JBoss RMI over socket + Jboss serialization. We see that Java RMI with Java serialization is always atleast 20% faster than Jboss RMI + socket + Jboss serialization. | | i am unable to understand the below from the test cases. | | 1. The payload uses byte[1024] empty array always. and the object is never serialized. | 2. why byte[] as theres not thing there to serialize in it | 3. Even on using byte[1024] to be sent across using jboss and java rmi we see java rmi is superior on our machines. | | If this is the case then how ar the graphs generated? Or am i missing something very important. Please help. | | -- | ravi | Actually, the byte array gets wrapped in some Remoting objects, which do indeed get serialized. By "Java RMI with Java serialization" I assume you mean the "raw_socket" results, or maybe the "raw_rmi" results, and by "Jboss RMI + socket + Jboss serialization" I assume you mean "socket transport with jboss serialization". Is that right? If so, then I can't explain why you're seeing results different than ours. Who knows? Different machines, different jdk's, etc. By the way, before I released version 2.4.0.GA, I did a lot of testing and tuning, and, in the end, the performance of 2.4.0.GA and whatever the latest 2.2.x release was at the time were very close, within a few percentage points. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260913#4260913 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260913

16 years, 5 months

1
0
0 / 0

[JBoss ESB Development] - [Jboss-esb] - Fault tolerance and dead letter queue

by forker01

We are three students and this is our first time with jboss-esb. We are trying to add a more powerful fault tolerance to jboss-esb, for this we are "picking" the messages from the Dead Letter Queue (the delivery of this messages has failed) and based on the fault information of each message need to make a decision (do something, invoke another service, try to invoke the same service again...), but the fault information is empty, like the fault reason or the fault code. The question is: Does Jboss-esb set the fault information to this delivery-failed messages? Sorry for my poor English, I tried to give an introduction to our problem and then ask the question. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260882#4260882 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260882

16 years, 5 months

1
0
0 / 0

[jBPM Development] - Re: Question about jbpm session and jobexecutor in jbpm3.3.0

by kukeltje

1: wrong forum, use the user forum 2: incorrect format for posting (use code tags) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260873#4260873 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260873

16 years, 5 months

1
0
0 / 0

[jBPM Development] - Re: Some bugs and feature requests on jBPM 4.1

by sebastian.s

Wow that's quite a lot of valueable feedback. :) How do we ensure these issues are all in JIRA? The issue with reversed values is already in JIRA. I updated the name of the issue to ensure it's easier to find: https://jira.jboss.org/jira/browse/GPD-372 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260869#4260869 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260869

16 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 2009