[Design of JBoss ESB] - Handling Large Files in JBossESB FileGateway
by mussab.sharif
Dear All,
I need to make JbossESB work as a file gwatey for files supplied by other system.
The files normally are large in size (10MB in average) and are in a binary format (ASN.1 Basic Encoding Rules (BER)).
I have built the decoder In a previous application using a multi threaded stand alone application, and I need to use the same logic to process the files and then store it in a database after its decoded.
My previous application reads the files using the BufferedInputStream to read the large file in a small pieces, and process the file and then continue reading by using (byte)input.read() method.
Just note I need to read the file byte by byte to do the appropriate decoding.
My question is how can configure the ESB to handle the large files in and make it read byte by bye and then putting the output in some kind of database without having a memory problem (which I had when I used the defulet file composer which take the file contents and put it in a message object)?
what that be solved by building a custom file composer? or there are other ways?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136595#4136595
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136595
18 years
[Design of JBoss Web Services] - Re: Integration metro
by thomas.diesler＠jboss.com
If the metro build depends on a certain version of jax-ws, that is published in the repository. How do we verify that
| sun-jaxws=2.1.3
|
is correct?
If these jars
| <!-- Metro 3rd party thats not available through repo.jboss.com -->
|
| <fileset dir="${lib.runtime.dir}">
| <include name="jaxws-local-transport.jar"/>
| <include name="stax-utils.jar"/>
| <include name="txnannprocessor.jar"/>
| <include name="wstx-asl-3.2.1.jar"/>
| <include name="xmldsig.jar"/>
| <include name="xws-security.jar"/>
| <!-- a custom jarjar resolver package -->
| <include name="resolver.jar"/>
| </fileset>
|
are all part of jax-ws (like this one)
| [tdiesler@tddell glassfish-metro]$ find . -name wstx-asl-*.jar
| ./wsit/wsit/lib/runtime/wstx-asl-3.2.1.jar
|
they should all come from the repository.
My issue is that wsit's dependency on jax-ws should be properly defined and verified.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136575#4136575
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136575
18 years