Non-native zip file handling
by David M. Lloyd
Spurred by the design call, I whipped up a pure Java zip file reader. I
threw it into the common repository right here:
https://svn.jboss.org/repos/common/jzipfile/trunk
Feel free to check it out and mess with it (you can install it locally via
maven). The API is really simple. Next week if I have time I'll try to
integrate this into VFS.
- DML
16 years, 12 months
Re: [jboss-dev] AS Embedded and The Full AS Dependency Set
by Robb Greathouse
Will this enable test driven development to work inside JBoss Developer Studio?
We talked about this a few months ago and the general agreement was that true TDD would be dependent on having AS Embedded working.
Robb Greathouse
JBoss
CELL 505-480-4639
OFFICE 505-255-2652
FAX 505-554-2834
----- Original Message -----
From: "Andrew Lee Rubinger" <andrew.rubinger(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Friday, June 12, 2009 12:45:28 AM GMT -06:00 Central America
Subject: [jboss-dev] AS Embedded and The Full AS Dependency Set
With Branch_5_x starting off the newer jboss-bootstrap, I've been
prototyping a bit with an Embedded launcher for AS. Goals are:
* User defines one dependency upon org.jboss.embedded:someArtifact
* Entire AS dependency set (==all JARs used in the runtime) are brought
in and are available for use in tests and upon the runtime test classpath
The key here is that the AS dependency set wholly ends up on the
application ClassLoader. Later on child>parent delegation takes place
and the app CL is the defining CL for everything (except webapps or
other things which define explicit scoping).
What I need is a mechanism to bring in the AS dependency tree in one
fell swoop. Most of this is accomplished by:
org.jboss.jbossas:jboss-as-build (All AS modules and *most* 3rdparty deps)
But that doesn't account for everything. I also need to explicitly
define, at a minimum:
org.jboss.jbossas:jboss-as-management:jsr77
jboss.web:jsp-api
jboss.web:el-api
...probably more stuff I haven't yet discovered.
I'd be much cleaner if AS itself could provide one POM artifact which
held all deps. Then Embedded could bring in this one dependency and get
everything else transitively. Embedded versions then become tied to AS
releases.
Can we add this? Is there a better way that occurs to anyone?
BTW I've got a series of docs in progress for the Wiki soon, but have
preferred to do proof-of-concept before posting it. I'll ping back here
when there's docs and source to comb through.
* Alternative Boot Method *
There is another way to boot AS, which is to be selective about the
classes allowed upon the application ClassLoader. This is the current
solution taken by AS Main, and the specialized assembly which
cherry-picks eligible classes is provided by run.jar.
This gives us another Embedded mode which uses a similar assembly on the
application ClassLoader, and then the rest of the classes are brought in
via the standard jboss-cl models as we normally do.
The drawback to this approach is that the user is not able to reference
classes such as the MC Kernel because this imposes invalid parent>child
ClassLoader delegation resulting in NCDFE. So it's, at the moment, good
for little more than starting and shutting down AS.
S,
ALR
--
Andrew Lee Rubinger
Sr. Software Engineer
JBoss by Red Hat
http://exitcondition.alrubinger.com
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
16 years, 12 months
Developer javadoc is essential!
by Jason T. Greene
Hi Guys,
The javadoc/code comments in our core modules are VERY lacking, so it is
incredibly difficult for new folks to understand how anything is
supposed to work (I have been hearing some groaning about this recently).
All of our code, especially SPI or API classes must have javadoc which
explains in detail the following things:
1) How the module is supposed to be used (and how it is actually used if
known)
2) The intended behavior, and any aspect of it that is known to be
broken or a hack (so that someone can differentiate between a design
problem and just an unimplemented section that needs to be fixed)
3) Crticial preconditions (e.g. "this class expects that the same vfs
handle instance be reused during a redeploy")
4) Thread-access design (e.g. "this class is thread-safe and can be
accessed from multiple threads", "this class is not thread-safe, and all
callers must use a shared lock to access", "this class is intended to
have an instance-per-thread")
If we can't answer these simple questions, then it is likely our design
is flawed.
--
Jason T. Greene
JBoss, a division of Red Hat
17 years
AS Embedded and The Full AS Dependency Set
by Andrew Lee Rubinger
With Branch_5_x starting off the newer jboss-bootstrap, I've been
prototyping a bit with an Embedded launcher for AS. Goals are:
* User defines one dependency upon org.jboss.embedded:someArtifact
* Entire AS dependency set (==all JARs used in the runtime) are brought
in and are available for use in tests and upon the runtime test classpath
The key here is that the AS dependency set wholly ends up on the
application ClassLoader. Later on child>parent delegation takes place
and the app CL is the defining CL for everything (except webapps or
other things which define explicit scoping).
What I need is a mechanism to bring in the AS dependency tree in one
fell swoop. Most of this is accomplished by:
org.jboss.jbossas:jboss-as-build (All AS modules and *most* 3rdparty deps)
But that doesn't account for everything. I also need to explicitly
define, at a minimum:
org.jboss.jbossas:jboss-as-management:jsr77
jboss.web:jsp-api
jboss.web:el-api
...probably more stuff I haven't yet discovered.
I'd be much cleaner if AS itself could provide one POM artifact which
held all deps. Then Embedded could bring in this one dependency and get
everything else transitively. Embedded versions then become tied to AS
releases.
Can we add this? Is there a better way that occurs to anyone?
BTW I've got a series of docs in progress for the Wiki soon, but have
preferred to do proof-of-concept before posting it. I'll ping back here
when there's docs and source to comb through.
* Alternative Boot Method *
There is another way to boot AS, which is to be selective about the
classes allowed upon the application ClassLoader. This is the current
solution taken by AS Main, and the specialized assembly which
cherry-picks eligible classes is provided by run.jar.
This gives us another Embedded mode which uses a similar assembly on the
application ClassLoader, and then the rest of the classes are brought in
via the standard jboss-cl models as we normally do.
The drawback to this approach is that the user is not able to reference
classes such as the MC Kernel because this imposes invalid parent>child
ClassLoader delegation resulting in NCDFE. So it's, at the moment, good
for little more than starting and shutting down AS.
S,
ALR
--
Andrew Lee Rubinger
Sr. Software Engineer
JBoss by Red Hat
http://exitcondition.alrubinger.com
17 years
JBOSS Class File Conflict
by sridhar veerappan
Hi,
Jboss is loading the httpClient jar and spring framework jar, I don't want
to load the jar from jboss, I want to load from my ear.
Is there anything I can do to avoid loading both the jars from jboss from
run.bat or from vm arguments in eclipse.
I tried couple of options
option 1:
<attribute name="Java2ClassLoadingCompliance">false</attribute>
<attribute name="UseJBossWebLoader">false</attribute>
<loader-repository>
com.example:archive=unique-archive-name
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
option 2:
<attribute name="Exclude">httpclient.wire</attribute>
but both the options are not working.
I am using separate slf4j for logging, I dont what jboss common-logging to
log the http client and spring framework log to write in server.log, I want
to write the logs in my own log created by slf4j,.
I am new you slf4j, I am trying to integrate with jboss and spring web
service, i am getting the debugger log, but
DEBUG httpclient.wire.header and
[org.springframework.web.
servlet.DispatcherServlet]
are going into server.log of jboss, i have configure logback.xml
<logger name="httpclient.wire" additivity="false">
<appender-ref ref="FILE"/>
<level value="info" />
</logger>
<logger name="httpclient.wire.header" additivity="false">
<appender-ref ref="FILE"/>
<level value="debug"/>
<level value="info" />
</logger>
<logger name="org.springframework" additivity="false">
<appender-ref ref="FILE"/>
<level value="ERROR"/>
</logger>
<logger name="org.springframework.web">
<level value="ERROR"/>
</logger>
<logger name="org.springframework.ws">
<level value="ERROR"/>
</logger>
but not reflecting in log.
Could you please help me.
Thanks in Advance
17 years
findbugs + jbossas5.1
by Ales Justin
This was mentioned at this year's JavaOne:
http://www.cs.umd.edu/~pugh/MistakesThatMatter.pdf , page 33
How do we find this issues?
Or, who's gonna run FindBugs on 5.1?
Could we do this as part of some build report? Paul?
Probably useful for all projects, to issue some warning about bad code
usage, as reported by Findbugs.
17 years
mistakes that matter
by Ales Justin
Testing ...
Changing the subject, since I don't see previous email on the www ui.
-------- Original Message --------
Subject: findbugs + jbossas5.1
Date: Wed, 10 Jun 2009 09:25:11 +0200
From: Ales Justin <ales.justin(a)gmail.com>
To: JBoss.org development list <jboss-development(a)lists.jboss.org>
This was mentioned at this year's JavaOne:
http://www.cs.umd.edu/~pugh/MistakesThatMatter.pdf , page 33
How do we find this issues?
Or, who's gonna run FindBugs on 5.1?
Could we do this as part of some build report? Paul?
Probably useful for all projects, to issue some warning about bad code
usage, as reported by Findbugs.
17 years
Fwd: Jboss + sLF4j + Spring logger issue
by sridhar veerappan
Hi,
I am new you slf4j, I am trying to integrate with jboss and spring web
service, i am getting the debugger log in jboss server.log, but I want this
log which i configure in logback.xml that is csm.log.
How to configure slf4j and logback.xml attached with this mail, any jar file
i need place in jboss/conf or lib?
DEBUG httpclient.wire.header and
[org.springframework.web.servlet.DispatcherServlet]
are going into server.log of jboss, i have configure logback.xml
<logger name="httpclient.wire" additivity="false">
<appender-ref ref="FILE"/>
<level value="info" />
</logger>
<logger name="httpclient.wire.header" additivity="false">
<appender-ref ref="FILE"/>
<level value="debug"/>
<level value="info" />
</logger>
<logger name="org.springframework" additivity="false">
<appender-ref ref="FILE"/>
<level value="ERROR"/>
</logger>
<logger name="org.springframework.web">
<level value="ERROR"/>
</logger>
<logger name="org.springframework.ws">
<level value="ERROR"/>
</logger>
but not reflecting in log.
Could you please help me.
Thanks in Advance
Sridhar
17 years
AS trunk build is failing
by Jaikiran Pai
The AS trunk is failing with a banned dependency error:
[java] [INFO] [enforcer:enforce {execution: enforce-plugin-versions}]
[java] [INFO] [enforcer:enforce {execution: ban-bad-dependencies}]
[java] [WARNING] Rule 0:
org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
[java] Found Banned Dependency: javax.xml.bind:jaxb-api:jar:2.1
[java] Found Banned Dependency: javax.xml.stream:stax-api:jar:1.0-2
Seems to be coming from webbeans logging (http://pastebin.com/m1894e846)
+- org.jboss.webbeans:webbeans-logging:jar:1.0.0.PREVIEW1:compile
[INFO] | \- javax.xml.ws:jaxws-api:jar:2.1:compile
[INFO] | +- javax.xml.bind:jaxb-api:jar:2.1:compile
[INFO] | | \- javax.xml.stream:stax-api:jar:1.0-2:compile
regards,
-Jaikiran
17 years
Abstract classes?
by Jaikiran Pai
I have seen many classes in some JBoss core projects whose names start
with "Abstract" but the classes are *not* abstract. Just to cite an
example, there's AbstractInjectionValueMetaData - not picking on this
specific class, but this is just an example. Any reason why we are
naming them Abstract?
regards,
-Jaikiran
17 years
