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

[Design of POJO Server] - Re: Getting the whole cause stack of the deployment exceptio

by pete.muir＠jboss.org

Thanks guys. One of my open tasks is to make sure that the Web Beans TCK is running ok on Branch_5_x. You just gave me a good reason to move to it :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250009#4250009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250009

16 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Deploying ValidatorFactory

by pete.muir＠jboss.org

I wasn't precise, this is another of the "services" that WB, in an EE env, requires: http://fisheye.jboss.org/browse/JBossAS/projects/webbeans-ri-int/trunk/ej... http://fisheye.jboss.org/browse/JBossAS/projects/webbeans-ri-int/trunk/de... Currently my approach was to write this as an MC Bean (like other services we have), and then tell the WebBeansBootstrap about it in the deployer View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250006#4250006 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250006

16 years, 7 months

1
0
0 / 0

[Design of JBoss Tools (dev)] - Re: Validation onlyh for last modified files (and maybe rela

by akazakov

Most validators already validate only changed files. But there is a lot of validators for xhtml pages from vendors. What version of JBoss Tools do you use? Is your project Seam project? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249997#4249997 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249997

16 years, 7 months

1
0
0 / 0

[Design of JBoss Tools (dev)] - Validation onlyh for last modified files (and maybe related

by luxspes

Hi! Validation is still too slow, (we have a project with around 2000 .xthml files, and, frankly, to make it usable, most of the team plain goes to Preferences->Validation and unchecks all the checkboxes in the "Build" column (and our computers are not that slow, see Environment). The problem then is that validation is only manual (and it is easy to forget to call it) What I would like is an option to have validation called only on the files that had changes since the last validation (even if I have opened the project for the first time, or if I made a "Clean" of all the projects in the workspace). If I have not made a change, I do not want validation to waste my time. If have a small project, and I feel like it is necessary, it should be possible (and easy) to configure validation to validate related files to predefined depth... and only if I have a really small project (or a super huge multicore workstations with lots of RAM) have validation work the way it does now. Environment: 1.86Ghz Cored 2 Duo with 4Gbytes of RAM, 150Gbytes HDD, WinXP SP3, JDK1.6u14 What do you think? would it be doable? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249995#4249995 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249995

16 years, 7 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: MCMP Documentation Issues

by bstansberry＠jboss.com

Thanks; I forwarded your post to the mod_cluster-dev mail list (mod_cluster-dev(a)lists.jboss.org) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249992#4249992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249992

16 years, 7 months

1
0
0 / 0

[Design of OSGi Integration] - OSGI/MC General

by adrian＠jboss.org

The main other todo is whether we provide a standalone OSGi release. You can see how this would work by looking at the bootstrap support within the testsuite, but there is probably a case for JBoss bootstrap so that it is more in line with what needs to be done for embedded testing etc.? As I mentioned elsewhere, without the profile service, this would require a seperate persistence/run level implementation and maybe some other things? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249985#4249985 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249985

16 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: interested in contributing ?

by caleb.powell

Hi, I signed the corporate contributor agreement about 3-4 days ago, but my employer did not receive their version of the agreement to sign. I'm trying to determine if something went wrong (e.g. I provided JBoss with an invalid email address for my employer) or whether the process just takes longer than I expected. I have sent an email to JBoss help (last Thursday) but I haven't received a response. Is the contribution approval process automated , or is someone on the JBoss side reviewing everything? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249984#4249984 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249984

16 years, 7 months

1
0
0 / 0

[Design of OSGi Integration] - OSGi/MC Security todos

by adrian＠jboss.org

The main thing that's not implementated is the AdminPermission and the Bundle.hasPermission() This requires some link with not yet written PermissionAdmin service. Besides that, the main work is testing. I've done some tests, but not committed them. They do work, but there's some issue with the VFS not initialising itself properly, see the HACK at the top of OSGiTestDelegate. Without that hack you get security errors when you try to use the VFS and it lazily inits itself. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249983#4249983 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249983

16 years, 7 months

1
0
0 / 0

[Design of OSGi Integration] - OSGi/MC Service todos

by adrian＠jboss.org

Services are also largely complete. What's missing is that we want to expose MC pojos and JMX MBeans etc. as OSGi services. The proper way to do this would be to push the OSGi Filter into kernel project and use the MDR INSTANCE scope as the attributes. There would be a gotcha in that OSGi expect attributes to have case insensitive names, but we would only have to enforce that for OSGi created services. The big problem with doing this now is that it would make it difficult to drop the OSGi layer into existing jboss releases since we can't change their MC implementations to do this. There's probably some compromise we can reach between the two extremes and leave the proper solution to a future major release of JBoss. We definitely need to do some service/mc integration to get the declarative service stuff working. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249981#4249981 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249981

16 years, 7 months

1
0
0 / 0

[Design of OSGi Integration] - OSGi/MC Filter todos

by adrian＠jboss.org

The parsing code for this was largely take from Felix. The runtime is a mainly a rewrite since it looked overly complex and unnecessary. I've kept the Apache license headers on the code I "copied" for that reason. OBJECT CONSTRUCTION There's a part in the filters where it needs to do Object construction. This should really use the JBoss Reflect TypeInfo.convertValue() stuff. APPROXIMATE This is the ~ operator. I haven't tried to implement this. I guess we could also borrow the Felix code? Or we could just do the minimum required by the spec which is to remove white space and do a case insensitive comparison. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249980#4249980 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249980

16 years, 7 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 August 2009