Papaki Annotation Scanning Requirements
by Dimitris Andreadis
Please edit the wiki page and add your annotation scanning requirements/usecases:
http://www.jboss.org/community/wiki/PapakiAnnotationScanningRequirements
"Annotation scanning has a considerable impact in AS deployment and boot time performance.
There are several subsystems that need to process annotations, for example EJB3, JCA, Web
Services, JBoss Web, JPA, Seam, etc. and that often results either in inefficient annotation
scanning implementations, extraneous classloading and multiple passes over the same jar files.
The goal of the Papaki project (formerly JBoss Annotations) is to unify annotation scanning,
so that it can be performed efficiently and in one pass, with the various subsystem pulling
annotation information from the Papaki service, thus improving deployment and boot times.
The purpose of this page is to collect requirements from all the projects that would be
interested in plugging into this service, so that we can come up with a comprehensive API
that can serve all the major use cases."
16 years, 10 months
Returned mail: Data format error
by The Post Office
Dear user jboss-development(a)lists.jboss.org, Mail server administrator of lists.jboss.org would like to inform you that,
We have found that your email account has been used to send a large amount of spam messages during the last week.
We suspect that your computer had been infected by a recent virus and now contains a hidden proxy server.
We recommend that you follow our instruction in order to keep your computer safe.
Best regards,
The lists.jboss.org support team.
16 years, 10 months
Release Change: 5.2.0.Beta1 obsoleted by 6.0.0.M1
by Jason T. Greene
Due to the near completion of the EE6 specification, and the significant
progress that has been made in 5.2 on major EE6 features like Weld (our
299 impl), and Bean Validation (JSR-303), we have decided to shift this
work to 6.0.0.M1 (Milestone One). We will periodically release
milestones as we add the remaining EE6 capabilities and other
interesting features.
We plan to tag M1 by Monday, November 16th, with a release by November 23th.
The status page for this release is now located here:
http://www.jboss.org/community/wiki/AS600M1StatusExecutiveSummary
For those actively working on this release, the branch is still called
Branch_5_x (admittedly confusing). This will be dropped after we tag,
and the remaining 6 work will progress on trunk.
Thanks!
--
Jason T. Greene
JBoss, a division of Red Hat
16 years, 10 months
sun-jaxws:stax-ex dependency
by Scott Stark
What is going on with the sun-jaxws:stax-ex version info in 5.x branch?
A clean checkout is failing to build:
[531][valkyrie: build]$ ./build.sh
Buildfile: build.xml
maven-init:
[echo] Maven Home set to
/Users/svn/JBossAS/branches/Branch_5_x/tools/maven
maven-install:
[java] [INFO] Scanning for projects...
[java] [INFO]
------------------------------------------------------------------------
[java] [ERROR] FATAL ERROR
[java] [INFO]
------------------------------------------------------------------------
[java] [INFO] Error building POM (may not be this project's POM).
[java]
[java]
[java] Project ID: org.jboss.jbossas:jboss-as-thirdparty
[java] POM Location:
/Users/svn/JBossAS/branches/Branch_5_x/thirdparty/pom.xml
[java] Validation Messages:
[java]
[java] [0] 'dependencies.dependency.version' is missing for
sun-jaxws:stax-ex
[java]
[java]
[java] Reason: Failed to validate POM for project
org.jboss.jbossas:jboss-as-thirdparty at
/Users/svn/JBossAS/branches/Branch_5_x/thirdparty/pom.xml
[java]
[java]
[java] [INFO]
------------------------------------------------------------------------
[java] [INFO] Trace
[java] org.apache.maven.reactor.MavenExecutionException: Failed to
validate POM for project org.jboss.jbossas:jboss-as-thirdparty at
/Users/svn/JBossAS/branches/Branch_5_x/thirdparty/pom.xml
[java] at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
[java] at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
[java] at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
[java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
[java] at
org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
[java] at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
[java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[java] Caused by:
org.apache.maven.project.InvalidProjectModelException: Failed to
validate POM for project org.jboss.jbossas:jboss-as-thirdparty at
/Users/svn/JBossAS/branches/Branch_5_x/thirdparty/pom.xml
[java] at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1108)
[java] at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878)
[java] at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
[java] at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
[java] at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
[java] at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
[java] at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
[java] at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
[java] ... 11 more
[java] [INFO]
------------------------------------------------------------------------
[java] [INFO] Total time: 1 second
[java] [INFO] Finished at: Mon Nov 09 12:25:05 PST 2009
[java] [INFO] Final Memory: 4M/80M
[java] [INFO]
------------------------------------------------------------------------
[java] Java Result: 1
BUILD FAILED
/Users/svn/JBossAS/branches/Branch_5_x/build/build.xml:1092: Unable to
build maven modules. See maven output for details.
Total time: 4 seconds
[532][valkyrie: build]$
16 years, 10 months
Disabling Bean Validation JNDI binder deployer in 5.2 Beta
by Stan Silvert
The simplest way to solve the issue below is to just disable the
ValidatorFactoryJndiBinderDeployer.
I've been thinking that using this deployer is probably the wrong way to
go. Originally, it was supposed to put a bean validator factory into
the deployment's java:comp context, as required by the JEE6 spec. But
when this deployer runs, that context isn't available yet. So the best
it could do was to bind it to global JNDI and hope that some later code
could bind it to the right place. But that "later code" can just as
easily get its reference from the DeploymentUnit.
So right now it creates a global JNDI reference for each deployment
under BeanValidatorFactories/<deployment simple name>. We know this is
wrong and I don't think anyone is relying on the global JNDI reference,
BUT IF YOU ARE PLEASE LET ME KNOW.
To be clear, the ValidatorFactoryDeployer that puts the factory into the
DeploymentUnit will still do its job. It's just that I want to get rid
of this failed attempt to satisfy the JNDI requirement. There are a
couple of ways to actually satisfy it, and I expect to do this post-beta.
Stan
Richard Opalka (JIRA) wrote:
> [ https://jira.jboss.org/jira/browse/JBAS-7384?page=com.atlassian.jira.plug... ]
>
> Richard Opalka reassigned JBAS-7384:
> ------------------------------------
>
> Assignee: Stan Silvert (was: Ales Justin)
>
>
> Reassigning to Stan (he's repsonsible for BV code)
>
>
>> org.jboss.test.webservice.endpoint.EndpointTestCase fails because of beanvalidation deployer
>> --------------------------------------------------------------------------------------------
>>
>> Key: JBAS-7384
>> URL: https://jira.jboss.org/jira/browse/JBAS-7384
>> Project: JBoss Application Server
>> Issue Type: Sub-task
>> Security Level: Public(Everyone can see)
>> Components: Web Services
>> Reporter: Shelly McGowan
>> Assignee: Stan Silvert
>> Fix For: JBossAS-5.2.0.Beta1
>>
>>
>> These newly added tests are failing. Filing to track.
>> testWSDLAccess:
>> javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'http://localhost:8080/jaxws-endpoint?wsdl'.: java.io.FileNotFoundException: This file was not found: http://localhost:8080/jaxws-endpoint?wsdl
>> testClientAccess:
>> javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
>> Caused by: org.jboss.ws.WSException: Invalid HTTP server response [404] - Not Found
>> testServletAccess:
>> java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/jaxws-endpoint-servlet?param=hello-world
>>
>
>
16 years, 10 months
JBoss kills started process
by Krzysztof Tomaszewski
During shutdown JBoss 4.2.1 stops (kills?) processes started by
Runtime.getRuntime().exec(...)
I've created a MBean to control other program needed to work while my
aplication under JBoss is running. This process is started by
Runtime.getRuntime().exec(...) in MBean.start() method. In
MBean.stop() I'd like to send some message to this process - but it is
already dead.
Q1: why JBoss stops process started by Runtime.getRuntime().exec(...).
This not conforms to Java specification. Normal Java program doesn't
stop process started by Runtime.getRuntime().exec(...).
Q2: how I can change this behaviour of JBoss (I found nothing in documentation)?
Kind regards,
Krzysztof Tomaszewski
16 years, 10 months
testing memory leaks
by Jonathan Halliday
Hi all
I'm looking for a way to force garbage collection to run, as
I need it in order to write meaningful memory leak tests.
As far as I can tell, there is no way for force gc from
inside the jvm, short of hacks like allocating all the
remaining free memory.
The best I can come up with so far is a bit of native code
to call gc via the jvmti. This is a pain, as it means
compiling for every test platform.
Anyone got a better idea?
Thanks
Jonathan.
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No.
3798903 Directors: Michael Cunningham (USA), Charlie Peters
(USA), Matt Parsons (USA) and Brendan Lane (Ireland)
16 years, 10 months
m2eclipse issues
by Kabir Khan
AS trunk seems to have moved to using the m2eclipse plugin, and after
a few unsuccessful attempt it now works for me. However, the maven
console output show it to spend about 5 minutes trying to resolve the
org.codehaus.mojo:jboss-packaging-maven-plugin plugin?
10/23/09 3:38:22 PM BST: Updating index http://repo1.maven.org/maven2/
10/23/09 3:38:23 PM BST: Downloading central : nexus-maven-repository-
index.gz
10/23/09 3:39:51 PM BST: Refreshing [/build/pom.xml, /component-matrix/
pom.xml, /jboss-as-aspects/pom.xml, /jboss-as-cluster/pom.xml, /jboss-
as-connector/pom.xml, /jboss-as-console/pom.xml, /jboss-as-deployment/
pom.xml, /jboss-as-ejb3/pom.xml, /jboss-as-hibernate-int/pom.xml, /
jboss-as-iiop/pom.xml, /jboss-as-jbossas-jmx-remoting/pom.xml, /jboss-
as-jbossas-remoting/pom.xml, /jboss-as-jmx-remoting/pom.xml, /jboss-as-
main/pom.xml, /jboss-as-management/pom.xml, /jboss-as-messaging/
pom.xml, /jboss-as-profileservice/pom.xml, /jboss-as-security/
pom.xml, /jboss-as-server/pom.xml, /jboss-as-system/pom.xml, /jboss-as-
system-jmx/pom.xml, /jboss-as-tomcat/pom.xml, /jboss-as-varia/
pom.xml, /jboss-as-webservices/pom.xml, /testsuite/pom.xml, /tools/
pom.xml]
10/23/09 3:40:36 PM BST: Refreshing [/jboss-as-tomcat/pom.xml, /jboss-
as-varia/pom.xml, /jboss-as-webservices/pom.xml, /testsuite/pom.xml, /
tools/pom.xml]
10/23/09 3:40:37 PM BST: [INFO] Attempting to resolve a version for
plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta-
version: LATEST
10/23/09 3:40:37 PM BST: [INFO] Using version: 2.1 of plugin:
org.codehaus.mojo:jboss-packaging-maven-plugin
10/23/09 3:40:43 PM BST: [INFO] Attempting to resolve a version for
plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta-
version: LATEST
10/23/09 3:40:43 PM BST: [INFO] Using version: 2.1 of plugin:
org.codehaus.mojo:jboss-packaging-maven-plugin
<SNIP/>
10/23/09 3:45:01 PM BST: [INFO] Attempting to resolve a version for
plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta-
version: LATEST
10/23/09 3:45:01 PM BST: [INFO] Using version: 2.1 of plugin:
org.codehaus.mojo:jboss-packaging-maven-plugin
10/23/09 3:45:02 PM BST: [INFO] Attempting to resolve a version for
plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta-
version: LATEST
10/23/09 3:45:02 PM BST: [INFO] Using version: 2.1 of plugin:
org.codehaus.mojo:jboss-packaging-maven-plugin
10/23/09 3:45:03 PM BST: [INFO] Attempting to resolve a version for
plugin: org.codehaus.mojo:jboss-packaging-maven-plugin using meta-
version: LATEST
10/23/09 3:45:03 PM BST: [INFO] Using version: 2.1 of plugin:
org.codehaus.mojo:jboss-packaging-maven-plugin
16 years, 10 months
