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

[Design of JBossCache] - Re: Name change for PojoCache annotation

by ben.wang＠jboss.com

So looks like we should just provide @Replicable (or @Replicated) and give the semantics of it applies to all subclass as well. Later on when AOP can provide attribute matching, we can then add the attribute (subclass=true) to distinguish it. One other possible way to break the closure is actually to comment out the prepare...instanceof... statement in pojocache-aop.xml. But it applies to all POJOs so not a permanent solution. Ideally, I'd like to get this done before Brian start the integration into 5.0. This is becuase there are tedious changes for the testing POJOs there (unless he doesn't object). OK, it is between @Replicated and @Replicable. Elias has convinced me to switch over to @Replicable (like I mentioned). So looks like it is 2 agaisnt 2. Anyone else wants to cast the switching vote? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986376#3986376 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986376

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: What is the status of the server integration code?

by ovidiu.feodorov＠jboss.com

I've completed the integration. JBM deploys unscoped under default/deploy/messaging (or all/deploy/messaging). The original deployment descriptors are stored in jboss-head/messaging/src/etc/deploy. The only artifact required to be present in repository is jboss-messaging.jar. Just update from the head and rebuild. I'll be standing by if you have any problems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986373#3986373 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986373

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: web console feedback

by david.lloyd＠jboss.com

Here's a list of things that are done and not done, as well as my ranking of how important they are. You are free to decide what the actual importance is, because I'm not totally clear on your goals for this release (mine are to provide at least minimal functionality without any major crash issues). Some major things that are done (not an exhaustive list): 1. Generally no on-screen exceptions from regular navigation (I'm squashing them as I find them) 2. New task forms rendering 3. Process source 4. Task form source (just because I had that nice little XML formatter written, so I thought, why not) Things that need to be done: 1. More work on navigation (I also don't like the mix of action and navigation in the menu). I could keep busy for several days on this one, but I think it's pretty important. 2. Action feedback - right now, some actions move you to a new view, some keep you on the same view, but none of them give you any feedback to tell you what happened. I have an idea of how to do this but I'd need a day or two to do it. This is pretty important from a usability perspective, but maybe not so important if the goal is to just demo the app? 3. Search Filters - should be moved to be inline with the table columns. Maybe 3-4 hours of work. 4. Reports and Dashboard - Many of the view screens could be enhanced to show simple dashboard-like things, and even keep them updated real-time with relatively small effort. This would help fill out the content of these screens. The ones that are there just have a couple attributes that I grabbed more to test the navigation than to provide the final content. This could range from simple to complex, depending on how fancy I want to get with it. 5. Validation - Validation feedback is primitive right now. To see what I mean, put a text string such as "hello" in one of the numeric search fields, like process version or task priority. This is maybe a half-day of work, if I do #2 first. 6. Cosmetic stuff - There's a lot I could do here, and I probably will, eventually, but it's obviously less important. 7. Task Form Outcomes - I'd like to have task form transition buttons bring you to a completion screen for the "next step". It should tell you if there are tasks outstanding, and to whom they are assigned. You should be able to choose a task to work on next, and possibly the options should be restricted by security role at some point. This is more of a design effort than implementation, but my gut feeling is that I'll want to finish fixing up the navigation first, otherwise I'll probably end up redoing some of this after I do the navigation stuff. 8. Robustness - The web application can fail in some places when there is unexpected or incorrect data in the process definition or in the database. I'd like to be robust against this case and give sensible error messages. Again this isn't so important from a demonstration perspective - just don't feed it bad data. :-) My editor actually crashed while I was typing this and so I had to start over again. Grrr. I'm sure I left something out. Feel free to add things you think are important... especially content-related items. I'm not always sure what the most useful information to display would be. In many cases, adding content is really simple so feel free to mention anything you can think of. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986369#3986369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986369

19 years, 4 months

1
0
0 / 0

[Design of JBossXB] - Re: jboss5 version synchronization

by scott.stark＠jboss.org

Also, when building the https://svn.jboss.org/repos/common/jbossxb/tags/1.0.0.CR7/ tag this is claiming to be a 1.0.1.TEST version: | [INFO] Installing C:\home\svn\Common\Tags\jbossxb-1.0.0.CR7\target\jboss-xml-bin | ding.jar to \usr\Repository\repository.jboss.com\maven2\jboss\jbossxb\jbossxb\1. | 0.1.TEST\jbossxb-1.0.1.TEST.jar | [INFO] Installing C:\home\svn\Common\Tags\jbossxb-1.0.0.CR7\target\jbossxb-1.0.1 | .TEST-sources.jar to \usr\Repository\repository.jboss.com\maven2\jboss\jbossxb\j | bossxb\1.0.1.TEST\jbossxb-1.0.1.TEST-sources.jar | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986354#3986354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986354

19 years, 4 months

1
0
0 / 0

[Design of JBossXB] - jboss5 version synchronization

by scott.stark＠jboss.org

the current jbossxb trunk (or the 1.0.0.CR7 being pulled into jbossas trunk) is not being built with the same level of jboss common jars as is used in jbossas: | <componentref name="jboss/common-core" version="2.0.2.CR1"/> | <componentref name="jboss/common-logging-log4j" version="2.0.1.GA"/> | <componentref name="jboss/common-logging-jdk" version="2.0.1.GA"/> | <componentref name="jboss/common-logging-spi" version="2.0.1.GA"/> | the jbossxb trunk pom.xml is referring to 1.0: | <dependency> | <groupId>jboss.logging</groupId> | <artifactId>jboss-logging-spi</artifactId> | <version>1.0</version> | </dependency> | <dependency> | <groupId>jboss.logging.log4j</groupId> | <artifactId>jboss-logging-log4j</artifactId> | <version>1.0</version> | </dependency> | <dependency> | <groupId>jboss.common.core</groupId> | <artifactId>jboss-common-core</artifactId> | <version>1.0</version> | <scope>compile</scope> | </dependency> | For what its using this may be ok, but we really need a separate version for jboss5 to ensure that we can maintain a jbossxb without affecting jboss4.x usage. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986349#3986349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986349

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Oracle scripts don't terminate lines with ;

by jeffdelong

Oracle scripts in jBPM 3.2 don't terminate lines with ; View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986340#3986340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986340

19 years, 4 months

1
0
0 / 0

[Design of JBossCache] - Re: Name change for PojoCache annotation

by bela＠jboss.com

Actually, while I like @Replicated more, you've got a point there... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986324#3986324 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986324

19 years, 4 months

1
0
0 / 0

[Design of JBossCache] - Re: Name change for PojoCache annotation

by bela＠jboss.com

Regarding extending @Replicated to subclasses: if you want to cut transitive closure of @Replicated to the subclass hierarchy, use @Transient for a class. Then instances of this class, plus subclasses will *not* be @Replicated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986323#3986323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986323

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Missing jars from JBoss AS 4.0.4GA Patch1 EJB Profile

by david.lloyd＠jboss.com

It's really more a question of build.xml spitting out two war files instead of one... it's very easily accomplished. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986316#3986316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986316

19 years, 4 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - 2 NICS 2 Networks, slow results

by jblaze

Is there a way to specify 2 network cards for a specific purpose, I know using the -b option will bind jboss to the NIC that uses that address, but is there a way to configure the database to talk out a different NIC? Basically private database info over NIC A and public client/server over NIC B ? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986314#3986314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986314

19 years, 4 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 November 2006