[Design of POJO Server] - Re: VirtualFile.toURL() returning vfsfile:
by bill.burke@jboss.com
Found out more things:
* If I read the JarEntries stream into a ByteArrayInputStream, then everything is cool
to be able to read into a BAIS, for some reason, I have to loop on the read or it doesn't work:
| ByteArrayOutputStream baos = new ByteArrayOutputStream((int)size);
| int wasRead = 0;
| byte[] tmp = new byte[1024];
| while( is.available() > 0 )
| {
| int length = is.read(tmp);
| if( length > 0 )
| baos.write(tmp, 0, length);
| wasRead += length;
| }
| is.close();
| byte[] bytes = baos.toByteArray();
|
* A better way to get a unique/copy of the InputStream for the JarEntry. I used URL's for this:
| URLConnection con = jarEntryUrl.openConnection();
| con.setUseCaches(false);
| return con.getInputStream();
|
This works beautifully. Now the question is, how slow is this MOFO?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980823#3980823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980823
19 years, 5 months
[Design of JBoss Eclipse IDE (dev)] - Re: JBoss5 integration
by scott.stark@jboss.org
There are two levels as I see it. There is a jsr88 type of service/profile service for deployment. I think jsr88 is not particularly useful, especially with the addition of annotations, but its something we need to support and there must be some use of the api in the wtp thing. Mostly its the notion of having the vendor ee descriptors be tied into jsr88 as well as having an xpath notion of the deployment metadata that seems out of synch. Regardless, there is a deployment service.
Beyond that, there is the question of controlling how the package deployed through jsr88/profile service is physcally structured. I expect that we want to leverage the vfs to avoid having to create physical ee packages and instead create logical ears/wars that are a union of the ide project files. This is manipulation of the vfs configuration/implementation that we need to flesh out.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980818#3980818
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980818
19 years, 5 months
[Design of JBoss ESB] - Re: Design of a Content Based Routing Service
by mark.little@jboss.com
"daniel.brum(a)jboss.com" wrote : anonymous wrote : Is this done sequentially or concurrently? Do you wait for the receivables to ack before sending to the payroll? If the answer is yes, then there's not really a problem AFAICT. If the answer is no, then we're talking about "asynchronous" interactions and, assuming the sender wants some kind of ack from each, the underlying infrastructure will need to be able to tally responses with "rendezvous" requests from the client, in just the same way it would for any "asynchronous" interaction.
|
| I would say that this is actually not a part of routing, but in fact a BPM process that keeps track of all the routings required for a particular message that comes in. The routing should be fire and forget, and it should be the job of an encompassing business process definition that knows if all parties required have been notified or not. If not, maybe it takes an action to have the message routed again, or if it's an optional recipient (say a statistical analysis system) that can live without the data being there for a real-time process, then it let's the logic continue, etc.
|
| I don't think we should be coupling the routing system to the systems receiving those routed data sets.
I think the example given certainly falls into a traditional BPM scenario. There may be some cross-over between BPM and CBR examples. Enabling users to do the same thing in different ways isn't necessarily a bad thing. I don't think there was/is the intention to tie our CBR implementation to a specific set of use cases.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980810#3980810
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980810
19 years, 5 months
[Design of JBoss jBPM] - Re: status of merge, non persisted script on fork, and n-out
by tom.baeyens@jboss.com
"kukeltje" wrote : Probably the same is needed for making the join configurable as well... correct? With a little beanshell an n-out-of-m join can be created in jdpl for the moment (until it becomes an attribute...., same is true for the 'descriminator')
|
| Next step would be to be able to use drools for this also, at least on the fork..... I'm looking into this now I understand more of the internals of jBPM.
|
making the join configurable is not really my priority. if you want, you can add and maintain it. but i would like to keep the jpdl language stable till 4.0. that's where i want to do a revision of the language constructs. and have all things like n-out-of-m and things like that.
improved drools integration is on the todo list for 3.x. don't know yet how that will look like. feel free to prorotype some ideas. if it is additions without changes to the current jpdl language, i won't have much objections.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980808#3980808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980808
19 years, 5 months