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

[Design of EJB 3.0] - Maven Version Resolution Differences 2.0.8 / 2.0.9

by ALRubinger

This is by far the worst I've seen to date. As of Revision 73768, EJB3 Build is broken in Maven 2.0.8 and working in 2.0.9. "Maven 2.0.8" wrote : core $> mvn clean install | ... | Rule 0: org.apache.maven.plugin.enforcer.BannedDependencies failed with message: Found Banned Dependency: org.jboss.microcontainer:jboss-container:jar:2.0.0.Beta10 | Found Banned Dependency: org.jboss:javassist:jar:3.6.0.GA | | $> /opt/apache/maven/apache-maven-2.0.8/bin/mvn dependency:tree -Dincludes=org.jboss.microcontainer:jboss-container | [INFO] [dependency:tree] | [INFO] org.jboss.ejb3:jboss-ejb3-core:jar:0.1.2-SNAPSHOT | [INFO] \- org.jboss.jbossas:jboss-as-system-jmx:jar:5.0.0.Beta4:provided | [INFO] \- org.jboss.jbossas:jboss-as-jmx:jar:5.0.0.Beta4:provided | [INFO] \- org.jboss.microcontainer:jboss-container:jar:2.0.0.Beta10:provided (version managed from 2.0.0.Beta6) | | $> /opt/apache/maven/apache-maven-2.0.8/bin/mvn -Dplugin=dependency help:describe | Group Id: org.apache.maven.plugins | Artifact Id: maven-dependency-plugin | Version: 2.0 | Goal Prefix: dependency Fantastic. Dependency Plugin version 2.0. Let's try the same thing in 2.0.9, where the build succeeds. "Maven 2.0.9" wrote : $> /opt/apache/maven/apache-maven-2.0.9/bin/mvn dependency:tree -Dincludes=org.jboss.microcontainer:jboss-container | {nothing} | | $> /opt/apache/maven/apache-maven-2.0.9/bin/mvn -Dplugin=dependency help:describe | Group Id: org.apache.maven.plugins | Artifact Id: maven-dependency-plugin | Version: 2.0 | Goal Prefix: dependency WTF? No dependency on org.jboss.microcontainer:jboss-container, yet the Dependency Plugin is the same version. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154158#4154158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154158

16 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2174] Cannot Obtain Destination for Request

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : You fix is fundamentally wrong, because it creates a dependency on the container. How to do it right? Give me an idea and I'll do it. As I said before I don't like my current fix. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154153#4154153 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154153

16 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2174] Cannot Obtain Destination for Request

by thomas.diesler＠jboss.com

You fix is fundamentally wrong, because it creates a dependency on the container. WS stack integration must stay clear of container details. Container integration must stay clear of stack details. If the problem only pertains to AS50Beta4, we can resolve it as "Won't fix" With the old build system your fix should not even have compiled. I'm looking into how this can be enforced in maven. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154151#4154151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154151

16 years

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 Plugin Broken

by ALRubinger

The EJB3 Build is Broken in Maven 2.0.8, see upcoming Thread for details. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154150#4154150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154150

16 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by thomas.diesler＠jboss.com

build,deploy,test is only a two step process http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source#Che... Reproduction of this issue would probably only add complication. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154149#4154149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154149

16 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2187] javax.xml.ws.Service handlers and thread saf

by thomas.diesler＠jboss.com

How about making a copy of the handler chain on port creation and scope that copy on the port? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154145#4154145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154145

16 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Some serious issues with new journal code for AIO

by timfox

Further to what Clebert and I discussed yesterday, and in the process of making some small changes to the journal I have discovered several major bugs / issues in the changes that were added to the journal when integrating the AIO journal. 1) appendAddRecord(final long id, final byte recordType, final EncodingSupport record): Why bother with a callback - much easier just to call write with sync = true? (less code) 2) public void appendAddRecord(final long id, final byte recordType, final byte[] record) throws Exception same as 1) 3) public void appendDeleteRecord(long id) throws Exception same as 1) 4) public void appendAddRecordTransactional(final long txID, final byte recordType, final long id, final byte[] record) throws Exception Previous code was always using callbacks - even if the journal didn't support callbacks 5) public void appendUpdateRecordTransactional(final long txID, byte recordType, final long id, final byte[] record) throws Exception same as 4) 6) public void appendDeleteRecordTransactional(final long txID, final long id) throws Exception Same as 4) 7) public void appendPrepareRecord(final long txID) throws Exception Two bugs in this one a) Previous code was always using callbacks - even if the journal didn't support callbacks b) Not waiting for completion on prepare 8) public void appendRollbackRecord(final long txID) throws Exception The bug here is that it doesn't wait for completion of all the transactional operations that came before it. It only waits for completion if the current operation Some of these are pretty critical bugs, I can only asume the new functionality test coverage isn't sufficient since these weren't caught. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154143#4154143 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154143

16 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Publish ESB services to web services

by burrsutter

A thought on where in the ESB Message should the SOAP stuff go... I think the raw XML as a string should go into message.getBody().add(soap_message); This is the "default location" which might be interesting to the action chain/pipeline. The marshaled request & response should be at message.getBody().add(SOAP_REQUEST,request); and message.getBody().add(SOAP_RESPONSE,response); respectively where SOAP_REQUEST is specified in the jboss-esb.properties file It is very likely that the user will take the POJOs and map them into jBPM or Drools using the techniques shown in quickstart bpm_orchestration4 By "marshaled", I mean the POJO (not XML) of the request & response objects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154130#4154130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154130

16 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: remove timer session bean altogether?

by alex.guizar＠jboss.com

The merging of CommandListenerBean and JobListenerBean, as in PVM, is another point to consider. Neither the timer bean nor the job listener bean are meant to be invoked directly by clients, unlike the command service and command listener, which makes compatibility concerns moot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154115#4154115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154115

16 years

1
0
0 / 0

[Design of EJB 3.0] - JBossSessionBeanMetadataCreator a la EjbJar30Creator

by ALRubinger

Team Metadata: I'm looking for something analogous to EjbJar30Creator which will also take into consideration JBoss-specific annotations. Want to do something like: AnnotationFinder<AnnotatedElement> finder = new DefaultAnnotationFinder<AnnotatedElement>(); | Collection<Class<?>> classes = new HashSet<Class<?>>(); | classes.add(beanImplClass); | JBossSessionBeanMetaData metaData = new JBossSessionBeanMetadataCreator(finder).create(classes); Couldn't find it in jboss-metadata presently; does this exist or are there plans to provide one? For the time being I'm mocking it for tests, but this will be helpful for non-JBossAS EJB3 Environments. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154111#4154111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154111

16 years

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