February 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Backport to 1_0_1_SP1 has broken the test suite

by timfox

Ok I have fixed the tests in 1_0_1_SP (one was also failing in TRUNK because of this). Also the fix itself was incomplete - the client ID was only being checked when set programmatically but client ids can also be set via a connection factory or when preconfigured in the database. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010130#4010130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010130

18 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - FYI: Latest ClassInfo changes.

by adrian＠jboss.org

PackageInfo I've added support for retrieving package info for a class. This is mainly so you can get at the annotations. This doesn't work for javassist which doesn't provide package annotations. Enum Constants You can now retrieve the underlying real enum constant. Also, you can retrieve the annotations against the constants. BeanInfo property accessors I've fixed this new code to delegate to the PropertyInfo such that the property can decide how to get/set the property. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010129#4010129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010129

18 years, 11 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: scanning unpacked deployment units outside the jboss ser

by bill.burke＠jboss.com

so you're using your IDE with a remote jboss instance? If you ran JBoss locally, you'd have no problems with unexploded. But... In JBoss 4 kernel you can only watch one file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010124#4010124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010124

18 years, 11 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JBoss Build Status Meeting Notes Feb 1, 2007

by pgier

I couldn't think of a situation where you would be looking at the jar outside of its jboss directory. If other projects are using jboss common for example, they could specify the dependency in their pom.xml and the jar gets downloaded into their local repository, and they never see it. If we are packaging up jboss common with the app server for example, there is a maven assembly plugin that can be used to package a project with its dependencies, so you would never have to worry about the actual name of the jboss common jar file. One situation where it probably would be useful to have the full name jboss-common-core.jar is for external non-maven projects that want to just extract the jars into their lib directory. But for this case we could produce a different name for the file (including the groupId) for non maven distribution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010111#4010111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010111

18 years, 11 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - scanning unpacked deployment units outside the jboss server

by joris77

Hi, I'm developing war deployment units for JBoss 4.0.2 all the time. One of the bottlenecks for developer productivity is the code deploy test cycle (probably most people feel this). Jetty now has this plugin for maven2 which automatically reloads the jetty server when something changes in your source directory. It looks directly at the src/main/webapp folder and the target/classes folder. Very handy and it would save me a lot of time. I tried to have the same effect with jboss by pointing the deployment scanner to my web folder in my workspace, changing the jboss-service.xml. Letting eclipse compile directly to the web-inf/classes folder I was able to deploy the exploded war from my workspace. But the only problem is, I quote from the comment in the jboss-service.xml: anonymous wrote : URLs may be local (file:) or remote (http:). Scanning is supported | for remote URLs but unpacked deployment units are not. So redeployment is not possible !? Another problem was that I had to rename my web folder to web.war. My questions are: Are there currently any plans to support such functionality (I don't mean the maven plugin)? Is it very difficult to implement/contribute a deployer or deploymentscanner that does such a thing for development purposes? Such a thing = configure a directory where the exploded war lives and reload it when: option 1 the way jboss does it currently with exploded wars in the deploy directory when the web.xml is touched option 2 the jetty way scanning the WEB-INF classes or another class directory configured Thanks anyway, Joris View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010110#4010110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010110

18 years, 11 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JBoss Build Status Meeting Notes Feb 1, 2007

by scott.stark＠jboss.org

It may be redundent in terms of the repo structure, but you said this also determines the artifact name. common-core.jar vs jboss-common-core.jar is a good use of the jboss prefix, so that redundency is a good thing. I suppose it could be reintroduced by overriding the artifact name via a combination of groupId and artifactId. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010087#4010087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010087

18 years, 11 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JBoss Build Status Meeting Notes Feb 1, 2007

by pgier

"pgier" wrote : | Project artifact naming convention | Project groupId will be "jboss" for all projects. | artifactId will be the name of the project or subproject | | We talked yesterday about using the "jboss" prefix for the project names. For example jboss/jboss-common-core vs. jboss/common-core. After thinking about it a little bit, I think that Scott is right that we really don't need the jboss prefix on the maven artifactId. Since the jars will always be downloaded into their appropriate subdirectory, there really isn't an issue of possible name conflicts with other organizations. The jboss prefix on the artifactId seems redundant. The drawback is that there are already a lot of projects in the repository with jboss prefix in the name so it will take a little bit of work to change them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010078#4010078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010078

18 years, 11 months

1
0
0 / 0

send parameter

by m.heidari

Hi, I want to send language parameter from "jbossweb-tomcat55.sar/ROOT.war/ index.html "to index.jsp of portal-core.war. How can I do this? Thanks very much

18 years, 11 months

1
0
0 / 0

[Design of JBoss Build System] - JBoss Build Status Meeting Notes Feb 1, 2007

by pgier

Remaining tasks to complete before micro container mavenization is complete Add a snapshot version of JBossTest to the maven2 repository. (JBoss Test can also be mavenized soon). JBossRetro will be called by the antrun plugin until a maven2 plugin version can be created. POM structure There should be a single parent pom that all JBoss proejcts will inherit default configuration from. Microcontainer and JBoss common will initially each use the build/pom.xml as the parent pom. Later will be re factored to share a single parent. Project artifact naming convention Project groupId will be "jboss" for all projects. artifactId will be the name of the project or subproject Synchronization of jboss maven repository with main maven repo. All JBoss project builds should be dependent only on the JBoss repository. Uploading JBoss artifacts to main maven repository is low priority and can be manually done as needed. Cleanup of Maven2 repository Paul will begin removing old stuff from the jboss repository. Maybe we can create something automated to find artifacts that are not depended upon. We will look into using ant tasks to pull artifacts from the maven2 repository instead of the current one for existing builds. This would allow us to merge the two repositories before fully converting to maven. Subversion Migration Will work with IT to migrate remaining projects from CVS to subversion. Starting with JBoss Serialization and then Seam, JBoss Remoting, and maybe JBossRetro and the maven repository. Other notes We will have a bi-weekly meeting to provide an update of the status of the build system. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010067#4010067 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010067

18 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Backport to 1_0_1_SP1 has broken the test suite

by timfox

Naming no names, but the person who backported http://jira.jboss.com/jira/browse/JBMESSAGING-791 (duplicate client ids) to the 1_0_1_SP obviously didn't run the test suite since the fix has broken several other tests. Please, lets remember to run the test suite before committing. There's no excuses on the 1_0 branches it only takes 47 minutes to run the whole thing. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010061#4010061 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010061

18 years, 11 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 February 2007