September 2008 - jboss-dev-forums

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

I had misspelled "asintegration" as "asinegration" in thirdparty/pom.xml | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-asintegration-core</artifactId> | <version>${version.org.jboss.aop}</version> | <mapping> | <componentId>jboss.aop</componentId> | </mapping> | </dependency> | Now I get more files, but I do not see the jboss-aop-client jar? | [kabir@~/sourcecontrol/jboss-head/build] | $ls -al ../thirdparty/jboss/aop/lib/ | total 5264 | drwxr-xr-x 16 kabir staff 544 29 Sep 16:08 . | drwxr-xr-x 4 kabir staff 136 29 Sep 16:08 .. | -rw-r--r-- 1 kabir staff 125660 29 Sep 16:08 jboss-aop-aspects-sources.jar | -rw-r--r-- 1 kabir staff 104051 29 Sep 16:08 jboss-aop-aspects.jar | -rw-r--r-- 1 kabir staff 934044 29 Sep 16:08 jboss-aop-sources.jar | -rw-r--r-- 1 kabir staff 1304506 29 Sep 16:08 jboss-aop.jar | -rw-r--r-- 1 kabir staff 18764 29 Sep 16:08 jboss-asintegration-core-sources.jar | -rw-r--r-- 1 kabir staff 22530 29 Sep 16:08 jboss-asintegration-core.jar | -rw-r--r-- 1 kabir staff 36870 29 Sep 16:08 jboss-asintegration-jmx-sources.jar | -rw-r--r-- 1 kabir staff 38918 29 Sep 16:08 jboss-asintegration-jmx.jar | -rw-r--r-- 1 kabir staff 31186 29 Sep 16:08 jboss-asintegration-mc-sources.jar | -rw-r--r-- 1 kabir staff 33154 29 Sep 16:08 jboss-asintegration-mc.jar | -rw-r--r-- 1 kabir staff 1780 29 Sep 16:08 jrockit-pluggable-instrumentor-sources.jar | -rw-r--r-- 1 kabir staff 4140 29 Sep 16:08 jrockit-pluggable-instrumentor.jar | -rw-r--r-- 1 kabir staff 1713 29 Sep 16:08 pluggable-instrumentor-sources.jar | -rw-r--r-- 1 kabir staff 2936 29 Sep 16:08 pluggable-instrumentor.jar | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179405#4179405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179405

16 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

That gets me bit further, but in my as poms I am including the following dependencies: | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-asintegration-core</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-asintegration-jmx</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-asintegration-mc</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-aop</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-aop-aspects</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jrockit-pluggable-instrumentor</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>pluggable-instrumentor</artifactId> | <version>${version.org.jboss.aop}</version> | </dependency> | But the thirdparty/jboss/aop folder only gets the following jars | [kabir@~/sourcecontrol/jboss-head/build] | $ls -al ../thirdparty/jboss/aop/lib/ | total 4880 | drwxr-xr-x 10 kabir staff 340 29 Sep 16:02 . | drwxr-xr-x 4 kabir staff 136 29 Sep 16:02 .. | -rw-r--r-- 1 kabir staff 125660 29 Sep 16:02 jboss-aop-aspects-sources.jar | -rw-r--r-- 1 kabir staff 104051 29 Sep 16:02 jboss-aop-aspects.jar | -rw-r--r-- 1 kabir staff 934044 29 Sep 16:02 jboss-aop-sources.jar | -rw-r--r-- 1 kabir staff 1304506 29 Sep 16:02 jboss-aop.jar | -rw-r--r-- 1 kabir staff 1780 29 Sep 16:02 jrockit-pluggable-instrumentor-sources.jar | -rw-r--r-- 1 kabir staff 4140 29 Sep 16:02 jrockit-pluggable-instrumentor.jar | -rw-r--r-- 1 kabir staff 1713 29 Sep 16:02 pluggable-instrumentor-sources.jar | -rw-r--r-- 1 kabir staff 2936 29 Sep 16:02 pluggable-instrumentor.jar | I am getting some errors that are not making much sense to me. What do they mean? | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Building JBoss Application Server Thirdparty Build | [java] [INFO] task-segment: [package] | [java] [INFO] ------------------------------------------------------------------------ | [java] [WARNING] POM for 'org.jboss.jbossas:jboss-as-system:pom:5.0.0-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project org.jboss.jbossas:jboss-as-system at Artifact [org.jboss.jbossas:jboss-as-system:pom:5.0.0-SNAPSHOT:compile] | [java] [INFO] [enforcer:enforce {execution: enforce-versions}] | [java] [WARNING] POM for 'org.jboss.jbossas:jboss-as-system:pom:5.0.0-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project org.jboss.jbossas:jboss-as-system at Artifact [org.jboss.jbossas:jboss-as-system:pom:5.0.0-SNAPSHOT:compile] | [java] [INFO] [dependency:sources {execution: download-sources}] | [java] [WARNING] POM for 'org.jboss.jbossas:jboss-as-system:pom:5.0.0-SNAPSHOT:compile' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project org.jboss.jbossas:jboss-as-system at Artifact [org.jboss.jbossas:jboss-as-system:pom:5.0.0-SNAPSHOT:compile] | [java] [INFO] [jboss-license:download-licenses {execution: default}] | [java] [INFO] Downloading licenses | [java] [WARNING] Attempting to build MavenProject instance for Artifact (org.jboss.aop:jboss-asintegration-jmx:2.0.0-20080929.135907-2) of type: jar; constructing POM artifact instead. | [java] [WARNING] Attempting to build MavenProject instance for Artifact (org.jboss.aop:jrockit-pluggable-instrumentor:2.0.0-20080929.135907-2) of type: jar; constructing POM artifact instead. | [java] [WARNING] Attempting to build MavenProject instance for Artifact (org.jboss.aop:jboss-aop-aspects:2.0.0-20080929.135907-10) of type: jar; constructing POM artifact instead. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179403#4179403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179403

16 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

Hmmm, I see it is being uploaded under | [INFO] Retrieving previous build number from snapshots.jboss.org | Uploading: https://snapshots.jboss.org/maven2/org/jboss/aop/jboss-aop/2.0.0-SNAPSHOT... | [INFO] Retrieving previous build number from snapshots.jboss.org | Uploading: https://snapshots.jboss.org/maven2/org/jboss/aop/jboss-aop/2.0.0-SNAPSHOT... | [INFO] Retrieving previous build number from snapshots.jboss.org | Uploading: https://snapshots.jboss.org/maven2/org/jboss/aop/jboss-aop/2.0.0-SNAPSHOT... | [INFO] Retrieving previous build number from snapshots.jboss.org | Uploading: https://snapshots.jboss.org/maven2/org/jboss/aop/jboss-aop/2.0.0-SNAPSHOT... | I will try to get rid of this from the as poms and see where that gets me | <dependency> | <groupId>org.jboss.aop</groupId> | <artifactId>jboss-aop-jdk50-client</artifactId> | <version>${version.org.jboss.aop}</version> | <mapping> | <componentId>jboss.aop</componentId> | </mapping> | </dependency> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179399#4179399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179399

16 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why do messages destined for paging not get assigned mes

by clebert.suconic＠jboss.com

You would need to start the server at the exact same millisecond you started 368 days ago, and still have those IDs not consumed to get a duplicated ID (very unlikely). But as I don't really mind, I have changed it to ignore the latest byte instead of the first byte. The ID generator will be valid as long as you can't generate more than 268435455 messages per 250 milliseconds (the FF part at the end). And the IDGenerator will be valid only until 0xEFFFFFFFFFF (Mon Aug 18 04:26:56 GMT-06:00 2492). :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179390#4179390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179390

16 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

Paul, I've deployed an aop snapshot to the snapshot server, and have updated my local as build to use the new artifacts. The client jar seems to be missing: | [java] [INFO] Failed to resolve artifact. | [java] | [java] Missing: | [java] ---------- | [java] 1) org.jboss.aop:jboss-aop-jdk50-client:jar:2.0.0-SNAPSHOT | [java] | [java] Try downloading the file manually from the project website. | [java] | [java] Then, install it using the command: | [java] mvn install:install-file -DgroupId=org.jboss.aop -DartifactId=jboss-aop-jdk50-client -Dversion=2.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file | [java] | [java] Alternatively, if you host your own repository you can deploy the file there: | [java] mvn deploy:deploy-file -DgroupId=org.jboss.aop -DartifactId=jboss-aop-jdk50-client -Dversion=2.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] | [java] | [java] Path to dependency: | [java] 1) org.jboss.jbossas:jboss-as-thirdparty:pom:5.0.0-SNAPSHOT | [java] 2) org.jboss.aop:jboss-aop-jdk50-client:jar:2.0.0-SNAPSHOT | [java] | [java] ---------- | [java] 1 required artifact is missing. | [java] | [java] for artifact: | [java] org.jboss.jbossas:jboss-as-thirdparty:pom:5.0.0-SNAPSHOT | [java] | [java] from the specified remote repositories: | [java] central (http://repo1.maven.org/maven2), | [java] repository.jboss.org (http://repository.jboss.org/maven2), | [java] snapshots.jboss.org (http://snapshots.jboss.org/maven2) | [java] | [java] | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] For more information, run Maven with the -e switch | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Total time: 12 seconds | [java] [INFO] Finished at: Mon Sep 29 14:53:58 BST 2008 | [java] [INFO] Final Memory: 27M/49M | [java] [INFO] ------------------------------------------------------------------------ | [java] Java Result: 1 | What do I do to deploy that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179384#4179384 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179384

16 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: jboss-classload*.xsd appears to be broken

by alesj

"david.lloyd(a)jboss.com" wrote : Oh well. Well I just committed the simple fix - if nothing is using these for validation then at least nothing will break. | You should also port this to Branch_2_0: - http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl/branches/Branch_... "david.lloyd(a)jboss.com" wrote : | But we probably ought to employ (or create) a schema verification tool that compares the annotation-based rules to the xsd and warns about any glaring incompatibilities... I'll do something about this. Probably - as discussed in Neuchatel - adding default validation against .xsd file based schema. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179377#4179377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179377

16 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: jboss.entity.manager.factory.jndi.name

by pete.muir＠jboss.org

There is an easy workaround, use: <persistence:entity-manager-factory name="myPersistenceUnit"/> | | <persistence:managed-persistence-context name="entityManager" auto-create="true" entity-manager-factory="#{myPersistenceUnit}"/> in components.xml View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179345#4179345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179345

16 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - user organization

by devendragera

We are implementing JBoss portal on our Stack. However we have existing organization data to which users belong to. I have seen users assigned to roles on JBoss portal. I want to assign users to organizations as well. Is this possible with JBoss portal? Thanks in Advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179341#4179341 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179341

16 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Nasty bug in new message grouping code

by timfox

I have committed a fix for this View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179338#4179338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179338

16 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Nasty bug in new message grouping code

by timfox

| public static final DistributionPolicy DEFAULT_DISTRIBUTION_POLICY = new RoundRobinDistributionPolicy(); | This means the same distribution policy instance is shared by all queues in the VM! Since this class contains state, this means all concurrent delivery with multiple queues is currently hosed. Each queue must maintain its own instance of DistributionPolicy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179331#4179331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179331

16 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2008