December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6072) Automate creating EAP 6.x public API Javadoc

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6072?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-6072 at 12/5/12 1:50 AM: ------------------------------------------------------------ Jenkins script {code} mv upstream/build/src/main/resources/modules upstream/build/src/main/resources/modules_ cp -r eap/build/src/main/resources/modules upstream/build/src/main/resources/ cd $WORKSPACE/upstream/build/ mkdir javadoc/target ### Includes and excludes. javadoc/extractPublicApiArtifactsList.sh --batch > javadoc/target/dependencySourceInclExcl.xml ### Groups. javadoc/extractPackageGroupsByModules.sh > javadoc/target/groups.xml ### Copy <includes>, exclude errorneous .jar's #xsltproc --output pom2.xml javadoc/pomSetIncludes.xsl pom.xml ## xsltproc doesn't work well with namespaces. Let's try Xalan. mkdir -p target cd target wget -nc http://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar wget -nc http://repo1.maven.org/maven2/xalan/serializer/2.7.1/serializer-2.7.1.jar cd .. #mvn dependency:get -Dartifact=xalan:xalan:2.7.1 -DxremoteRepositories=central::default::http://repo1.maven.apache.org/maven2 -DrepoUrl=http://repo1.maven.apache.org/maven2 -Dmaven.repo.local=foo #mvn dependency:copy-dependencies -DincludeGroupIds=xalan -DoutputDirectory=target/jars #java -cp serializer-2.7.1.jar -jar xalan-2.7.1.jar -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl ## Doesn't work for some reason. java -cp target/serializer-2.7.1.jar:target/xalan-2.7.1.jar org.apache.xalan.xslt.Process -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding="$BRANDING"; {code} was (Author: ozizka): Jenkins script {code} mv upstream/build/src/main/resources/modules upstream/build/src/main/resources/modules_ cp -r eap/build/src/main/resources/modules upstream/build/src/main/resources/ cd $WORKSPACE/upstream/build/ mkdir javadoc/target ### Includes and excludes. javadoc/extractPublicApiArtifactsList.sh --batch > javadoc/target/dependencySourceInclExcl.xml ### Groups. javadoc/extractPackageGroupsByModules.sh > javadoc/target/groups.xml ### Copy <includes>, exclude errorneous .jar's #xsltproc --output pom2.xml javadoc/pomSetIncludes.xsl pom.xml ## xsltproc doesn't work well with namespaces. Let's try Xalan. mkdir -p target cd target wget -nc http://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar wget -nc http://repo1.maven.org/maven2/xalan/serializer/2.7.1/serializer-2.7.1.jar cd .. #mvn dependency:get -Dartifact=xalan:xalan:2.7.1 -DxremoteRepositories=central::default::http://repo1.maven.apache.org/maven2 -DrepoUrl=http://repo1.maven.apache.org/maven2 -Dmaven.repo.local=foo #mvn dependency:copy-dependencies -DincludeGroupIds=xalan -DoutputDirectory=target/jars #java -cp serializer-2.7.1.jar -jar xalan-2.7.1.jar -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl ## Doesn't work for some reason. java -cp target/serializer-2.7.1.jar:target/xalan-2.7.1.jar org.apache.xalan.xslt.Process -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl {code} > Automate creating EAP 6.x public API Javadoc > -------------------------------------------- > > Key: AS7-6072 > URL: https://issues.jboss.org/browse/AS7-6072 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System, Documentation > Affects Versions: 7.1.3.Final (EAP) > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Fix For: 7.2.0.CR1 > > > First attempt: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/EAP6-javadoc/ > What's needed: > * Blacklist of skipped .jar's (cause exceptions when generating) > * XSLT to put <include>'s to pom.xml > * XSLT to put <groups> to pom.xml > See also https://docspace.corp.redhat.com/docs/DOC-105009 (bottom) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6072) Automate creating EAP 6.x public API Javadoc

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6072?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-6072: ----------------------------------- Jenkins script {code} mv upstream/build/src/main/resources/modules upstream/build/src/main/resources/modules_ cp -r eap/build/src/main/resources/modules upstream/build/src/main/resources/ cd $WORKSPACE/upstream/build/ mkdir javadoc/target ### Includes and excludes. javadoc/extractPublicApiArtifactsList.sh --batch > javadoc/target/dependencySourceInclExcl.xml ### Groups. javadoc/extractPackageGroupsByModules.sh > javadoc/target/groups.xml ### Copy <includes>, exclude errorneous .jar's #xsltproc --output pom2.xml javadoc/pomSetIncludes.xsl pom.xml ## xsltproc doesn't work well with namespaces. Let's try Xalan. mkdir -p target cd target wget -nc http://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar wget -nc http://repo1.maven.org/maven2/xalan/serializer/2.7.1/serializer-2.7.1.jar cd .. #mvn dependency:get -Dartifact=xalan:xalan:2.7.1 -DxremoteRepositories=central::default::http://repo1.maven.apache.org/maven2 -DrepoUrl=http://repo1.maven.apache.org/maven2 -Dmaven.repo.local=foo #mvn dependency:copy-dependencies -DincludeGroupIds=xalan -DoutputDirectory=target/jars #java -cp serializer-2.7.1.jar -jar xalan-2.7.1.jar -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl ## Doesn't work for some reason. java -cp target/serializer-2.7.1.jar:target/xalan-2.7.1.jar org.apache.xalan.xslt.Process -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl {code} > Automate creating EAP 6.x public API Javadoc > -------------------------------------------- > > Key: AS7-6072 > URL: https://issues.jboss.org/browse/AS7-6072 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System, Documentation > Affects Versions: 7.1.3.Final (EAP) > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Fix For: 7.2.0.CR1 > > > First attempt: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/EAP6-javadoc/ > What's needed: > * Blacklist of skipped .jar's (cause exceptions when generating) > * XSLT to put <include>'s to pom.xml > * XSLT to put <groups> to pom.xml > See also https://docspace.corp.redhat.com/docs/DOC-105009 (bottom) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6071) Split up XML reading and writing in the EJB subsytem

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6071: ----------------------------------- Summary: Split up XML reading and writing in the EJB subsytem Key: AS7-6071 URL: https://issues.jboss.org/browse/AS7-6071 Project: Application Server 7 Issue Type: Feature Request Components: EJB Reporter: Stuart Douglas Assignee: Stuart Douglas As the moment we have a lot of dead code in terms of writing out old versions of subsystems. This code is no longer functional as the model has changed, and I don't see any benefit to keeping it around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
1
0 / 0

[JBoss JIRA] (AS7-5926) EJB system exceptions not wrapped as EJBException when tx attribute NEVER

by Cheng Fang (JIRA)

Cheng Fang created AS7-5926: ------------------------------- Summary: EJB system exceptions not wrapped as EJBException when tx attribute NEVER Key: AS7-5926 URL: https://issues.jboss.org/browse/AS7-5926 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.2.0.CR1 Reporter: Cheng Fang Assignee: jaikiran pai EJB spec has requirements that system exceptions be wrapped as EJBException before throwing it to the client. The problem I'm seeing is, when the ejb business method has tx attribute NEVER, any runtime exceptions thrown from the method currently are directly propagated to the client. The exception handling should work with all types of tx attributes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
3
0 / 0

[JBoss JIRA] (JGRP-1548) UNICAST2: send STABLE message after 'last received' message

by Bela Ban (JIRA)

Bela Ban created JGRP-1548: ------------------------------ Summary: UNICAST2: send STABLE message after 'last received' message Key: JGRP-1548 URL: https://issues.jboss.org/browse/JGRP-1548 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 Contrary to UNICAST, which acks every message, UNICAST2 never acks messages, but only asks the sender to retransmit a message when a gap has been detected. However, the drawback of this (negative ack) mechanism is the so called last-message-dropped problem: when A sends messages [1..5] to B, but 5 is dropped by the transport, as A doesn't retransmit messages until it gets an ack, B only gets messages [1..4]. B will *not* ask A to retransmit message 5, as B doesn't know A *sent* message 5 in the first place. If A doesn't send message 6 for B to detect 5 is missing and asking A for retransmission, B won't get that message. The way this is currently handled is with stable messages. A STABLE message is sent from B to A every stable_interval ms or whenever M bytes from A have been received. In the worst case, B will have to wait stable_interval ms until it finally receives message 5 from A. SOLUTION: In addition to time and size based STABLE messages, we could send a STABLE message whenever the batch of messages removed from the receive window has completed and the receive window is empty. This would send a STABLE message immediately when a single message has been received (and no other messages from A are in the receive window), but it would only send another STABLE message only when all (e.g.) 200 messages from A have been processed and the receive window is empty. With this new mechanism, we could even remove the time-based STABLE messages ! Example: - At time T0, messages M1 and M2 are received. A STABLE message for M2 is sent. - At T+500 (ms), messages M3-M100 are received. A STABLE message for M100 is sent - At T+1500, M101 is received. A STABLE message for M101 is sent. - At T+2000, M102 is received. A STABLE message for M102 is sent. - At T+2010, M103-M500 are received. A STABLE message form M500 is sent This is similar to the ACK based scheme in UNICAST where we only send an ack for the last message in a batch (or for a single message if not batch has been received). This new mechanism needs to be configurable: if enabled, the time-based STABLE mechanism would be disabled. If the -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
5
0 / 0

[JBoss JIRA] (AS7-4610) Interface not found when deploying an EJB of class A that extends B and B implements an Interface

by Christoph Gutmann (JIRA)

Christoph Gutmann created AS7-4610: -------------------------------------- Summary: Interface not found when deploying an EJB of class A that extends B and B implements an Interface Key: AS7-4610 URL: https://issues.jboss.org/browse/AS7-4610 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Christoph Gutmann Assignee: jaikiran pai The class hierarchy is as follows: -class EJBClient extends class Client (POJO) -class Client implements interface MyInterface (POJO) When deploying EJB 'EJBClient', JBoss does not resolve indirectly implemented interface by an EJB via a superclass. This did work in JBoss5. When deploying such an EJB you get the error message {code} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Bean class org.foo.EJBClient specifies @Local annotation, but does not implement 1 interface {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
3
0 / 0

[JBoss JIRA] (AS7-6082) EJbLogger contains messages that should be in EjbMessages

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6082: ----------------------------------- Summary: EJbLogger contains messages that should be in EjbMessages Key: AS7-6082 URL: https://issues.jboss.org/browse/AS7-6082 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Stuart Douglas Assignee: jaikiran pai Priority: Minor The EjbLogger class also contains exception messages, not just log messages. It also has two loggers (ROOT_LOGGER and EJB3_LOGGER) with the same package name, it would be good to get rid of one of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBAS-9525) Upgrade to JBoss Transactions 4.17.3.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBAS-9525: ----------------------------------- Summary: Upgrade to JBoss Transactions 4.17.3.Final Key: JBAS-9525 URL: https://issues.jboss.org/browse/JBAS-9525 Project: Application Server 3 4 5 and 6 Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
2
0 / 0

[JBoss JIRA] (AS7-6081) Provide a management operation to discover servers in a server group in domain mode

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-6081: ---------------------------------------- Summary: Provide a management operation to discover servers in a server group in domain mode Key: AS7-6081 URL: https://issues.jboss.org/browse/AS7-6081 Project: Application Server 7 Issue Type: Feature Request Components: CLI, Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Richard Achmatowicz Assignee: Alexey Loubyansky Priority: Minor Fix For: 7.2.0.Alpha1 In domain mode, an end user might want to start one or more servers by hand in a named server group. Obtaining the list of servers in a server group is not readily available: the "group" attribute is embedded in server-config, so we have to drill down into every /host=*/server-config=* combination to find out which servers belong to a specific server group. It would improve the user experience to have an operation which shows which servers are in a given server group. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
5
0 / 0

[JBoss JIRA] (LOGTOOL-62) Log filtering tool

by Jesper Pedersen (JIRA)

Jesper Pedersen created LOGTOOL-62: -------------------------------------- Summary: Log filtering tool Key: LOGTOOL-62 URL: https://issues.jboss.org/browse/LOGTOOL-62 Project: Log Tool Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jesper Pedersen Assignee: James Perkins It would be nice to have a log filtering tool, which can help to extract / highlight log statements in huge log files. An idea could be to have a SQL like language in order to limit the number of lines as much as possible {noformat} SELECT * FROM server.log WHERE CATEGORY = 'org.jboss.as' AND SEVERITY IN {FATAL OR ERROR OR WARN} AND TIMESTAMP >= '12:42:00,000' AND CONTENT CONTAINS 'Something went wrong' {noformat} Having functions to select all / a defined number of lines after each hit, between timestamps, and so on would be good. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012