April 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Build System] - Re: mvn deploy should have a precondition check for availabl

by pgier

Ok, I see the problem. Yes, there should be a way to check that dependencies are available remotely when deploying. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141056#4141056 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141056

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: mvn deploy should have a precondition check for availabl

by wolfc

But the artifacts are probably resolvable from a local repo. The scenario in the other thread clearly shows the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141052#4141052 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141052

18 years

1
0
0 / 0

[Design of JBoss Build System] - jboss metadata pom

by dimitris＠jboss.org

I'm making some changes to the jboss-metadata pom, for getting closer to a Beta7 release: - Updated to org.jboss.microcontainer:jboss-container:jar:2.0.0.Beta9 (was Beta6) - and removed the jboss:jbossxb exclusion (AFAICT, not needed anymore) - Updated to org.jboss:jboss-vfs:jar:2.0.0.Beta10 (from Beta4) - Updated to org.jboss:jbossxb:jar:2.0.0.CR8 (from CR5) - Update to org.jboss.javaee:jboss-javaee:jar:5.0.0.Beta3Update1 (from Beta3) - Update to org.jboss:jboss-test:jar:1.0.5.GA:test (from 1.0.4.GA) Possible Inconsistencies ------------------ - Shouldn't the groupId for jboss-vfs be changed to 'org.jboss.vfs' (or org.jboss.virtual), rather than org.jboss ? - Same for jbossxb. Shouldn't groupId be 'org.jboss.xb'? - Same for org.jboss.jaxws - Same for metadata project itself - common-logging-spi appears with 2 names: jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile jboss:jboss-logging-spi:jar:2.0.3.GA:compile View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141051#4141051 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141051

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by anil.saldhana＠jboss.com

Alexey, do you want us to create a JIRA issue for this in JBossXB project? Or is this an issue related to any of the class loader changes (I am not sure what they were) in recent times? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141049#4141049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141049

18 years

1
0
0 / 0

[Design of JBoss Build System] - New repository locations

by pgier

I created two new directories on repository.jboss.org. http://repository.jboss.org/maven2_legacy/ http://repository.jboss.org/maven2_central/ The idea is that the first one could be a place to put stuff that we need for old builds, but should not be used in newer builds. Things like artifacts that were moved or renamed. Or stuff that shouldn't have been put in the repository, but might be used in an old build. The second one is a place for stuff that we copy from central. This one will hopefully be temporary until we can set up our own mirror so that we don't need to copy these dependencies all the time. Let me know if this sounds like a bad idea. Otherwise, I'll bring it up on the dev list and then start moving stuff as needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141041#4141041 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141041

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NPE with new parsing in aop-mc-int tests

by kabir.khan＠jboss.com

| addJaxbSchema("urn:jboss:aop-beans:1.0", "org.jboss.aop.microcontainer.beans.metadata.AOPDeployment"); | is correct, I moved this out for the release 2 weeks ago as mentioned on another thread. The org.jboss.aop.microcontainer.beans.beanmetadatafactory stuff is old and uses the AOPBeanSchemaInitializer. The way it uses the JAXB annotations is wrong as used on another thread. My question was mainly a warning that I will introduce the beans.metadata package again and switch to doing it that way. What is in mc trunk will only work with JBossXB 2.0.0.CR7 What I want to put in will only work with JBossXB 2.0.0.CR8 The "old" way and the "new" way can probably live side by side for a while, but if the target version of JBossXB in AS trunk is 2.0.0.CR8 I might as well get rid of the "old" way once and for all. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141025#4141025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141025

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: AOPConstructorJoinpoint::methodHasAnnotations is wrong

by kabir.khan＠jboss.com

OK having read that thread, I agree. The test I mentioned is there for legacy reasons, and works using the KernelControllerContextAware introduction + a binding + pointcut intercepting that. I think that this test can be removed since it is superseded by JMXLifecycleTest anyway (which uses lifecycle-configure) I have reverted the change I made to the @JMX annotation View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141018#4141018 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141018

18 years

1
0
0 / 0

[Design of JBoss ESB] - Re: About authentication / authorization on ESB services?

by lihui_pang

Thanks for your quick reply. In most of quick start samples, there are two client programs: one is sendJMSMessage, one is sendESBMessage. Can you please let me know the justification on using these two, e.g. in which case the client should use sendJMSMessage, or sendESBMessage? I find there is sample jms_secured, wondering if I can use this to pass user credential instead of programming authentication in my action class (if it's sendESBMessage). Thanks for your help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141013#4141013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141013

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: mvn deploy should have a precondition check for availabl

by pgier

If the project is building with maven you cannot deploy an artifact with missing dependencies because maven will try to resolve deps and build the project first. If you are using mvn deploy:deploy-file and just deploying the jar and pom manually, then the dependencies are not resolved first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141011#4141011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141011

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Dependency conflicts lost during AS mavenization

by pgier

Another benefit to having a separate location for legacy stuff is that it will be very easy to see if a build is depending on something that it shouldn't be depending on. With the legacy repo off, the build will fail when it can't find the old artifact. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141004#4141004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141004

18 years

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 April 2008