anonymous wrote : It looks like it is completely replacing the private native
defineClass0 method on the classloader
It's not replacing the call, just allowing the AspectManager to transform the
loaded bytes before calling defineClass0.
anonymous wrote : IBM's JVM has a similar defineClass0
I hadn't tried the alternate way of using loadtime, thanks for pointing that
out. I think that might be at least part of the solution, but now I'm running
into visibility issues with different classes.
I was looking over the code that creates the new java.lang.ClassLoader
My last message was messed because of the XML stuff of my build file...
Sorry for that.
| path id=competence.compilation.classpath
| pathelement path=${hibernate.lib.dir}/hibernate2.jar/
| pathelement path=${aop.lib.dir}/jboss-aop.jar/
|
Hi,
In the 1.0 release it is currently using the order of the interceptors defined
in jboss-aop.xml, so you could try moving the binding with the traceinterceptor
to the top:
| ?xml version=1.0 encoding=UTF-8?
| aop
|bind pointcut=all(@trace)
|interceptor
I reworked my code in such a way that the invocation for the Configuration
class is out of the scope of the aopc compiler.
Now everything works fine.
Does anyone had any problems like this?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858523#3858523
Reply
Thank you for your advice, kabir.khan!
I solved that issue.
Thanks.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858803#3858803
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858803
[EMAIL PROTECTED] wrote : ...
| The include is a bug though and we'll fix as soon as we can.
|
| Bill
Just remind. I haven't found that on JIRA.. or has it been already fixed
Regards,
Tomasz
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858572#3858572
thanks...added to jira.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858575#3858575
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858575
---
SF email is sponsored by
When you aopc your classes, make sure the hibernate libraries are in the
classpath. This exception gets thrown because you are aspectizing a class that
references the HibernateSessionFactory and the compiler cannot find this class
to determine whether or not any other aspects/pointcuts are
It does not work...
there is a weird thing happening here...
I took of the references to the configuration object in my code, and every
thing works fine. Including code that uses classes of the Hibernate jar.
I use other concrete class for the package, and it worked too.
If I only declare a
I still does not understand what paths am I supposed to put on the task...
And still does not work...
The first two lines of the debug output:
[aopc] [debug] jboss.aop.class.path is NULL
[aopc]
I analysed the hibernate jar and saw that the
sf.net.hibernate.cfg.Configuration contains inner classes.
I tried to use a class of the log4j pack (the ConsoleAppender) and it worked
nice. And it does not have inner classes.
Any clues?
View the original post :
It would help if you could send me an easy example that I can reproduce the
problem. An example with Hibernate would be fine... [EMAIL PROTECTED]
I'm sorry for your problems.
Bill
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858536#3858536
Reply to the
ok.
I will prepare the example with Hibernate and it to you.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858538#3858538
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858538
Add the Hiberante jars to your classpath element of the aopc target. I.e.:
|
| aopc ...
|
|classpath path=${competence.classes.dir}/
|classpath refid=aopc.classpath/
|src path=${competence.classes.dir}/
|aoppath path=${aop.config}/
| /aopc
|
|
Does that
Did you try this?
http://docs.jboss.org/aop/aspect-framework/reference/en/html/running.html#d0e2599
You may be forced to use the precompiler as I've only tested JBoss AOP on JBoss
application server and in standalone plain java programs.
Also,
If you get this to work, can you create a WIKI
Thanks for the response Bill, I had missed that part.
Unfortunately, there seem to be different problems from this approach. I start
getting things like
anonymous wrote : Faild to aspectize class
com.ibm.etools.websphere.tools.internal.util.FileUtil. Could not find class it
references
Hi,
yesterday i had the same problem with the nullpointer exception in my example
after redeploy my application.
Now my interceptors are not executing after redeploy my application. I must
restart the server after each change.
I'm using jboss 4.0.1RC2 and precompile my application with the aop
Yes we're using jboss 4.0.0 too.
JBoss 4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857843#3857843
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857843
Since post editing is disabled i have some infos to provide for better
understanding.
We use jdk 1.5 and aop final 1.0.0. The classes are precompiled(aop'ed) and
then copied into the deploy folder as an *.ear.
thx for help
d.hesse
View the original post :
I'm pretty sure we fixed all the redeployment problems in current CVS by
redesigning how a class binds to its aspects. I'll try to incorporate your
scenario into the testsuite.
Thanks for your patience,
Bill
View the original post :
Is there a CVS tag to use to get the revision of the source corresponding to
release 1.0.0? I was going to fix a bug I found and didn't want to deal with
any new bugs that might be in development.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857441#3857441
'instanceof' springs to mind ;-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857100#3857100
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857100
---
SF email is
Thanks for your reply...I just tried it out to rename the aop-deployer in the
deployer-directory of my all-configuration of
jboss4.0RC1but...unfortunately...it did not help...I still have the same
problem...jboss cannot find the deployeralso my ejb3.0-things cannot be
deployed.I
maxpower25 wrote : I just tried it out to rename the aop-deployer in the
deployer-directory of my all-configuration of jboss4.0RC1
|
As mentioned in one of the threads I posted a link to (ok one of them is pretty
long :-), do not use JBoss 4.0RC1. Either use 4.0 or the latest (4.0.1RC1)
Monitor this instead :-)
http://sourceforge.net/project/showfiles.php?group_id=22866package_id=84165
We'll get the link updated/removed shortly
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856856#3856856
Reply to the post :
To save yourself from further problems down the line, get JBoss 4.0.1RC1 as
that is required for EJB3
http://sourceforge.net/project/showfiles.php?group_id=22866package_id=16942release_id=280264
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856577#3856577
Do these two threads help?
http://www.jboss.org/index.html?module=bbop=viewtopict=56624
http://www.jboss.org/index.html?module=bbop=viewtopict=56564
Once you have got the AspectManagerService working with jdk 1.5, rename the
JBOSS/server/all/deploy/jboss-aop-jdk50.deployer directory to
1) Yes. I can't remember exactly what is already deployed in JBoss 4.0 RC2 (a
jar or a directory). If you can't get it working with JBoss 4.0 RC 2, download
JBoss 4.0, and follow these instructions
http://www.jboss.org/index.html?module=bbop=viewtopict=56564
| Instead of execution: method() and constructor()
| Instead of withincode: withinmethod and withinconstructor
|
| It is easier to read.
|
| Same goes with has and hasfield.
The problem is that you're not being clear on 'within()' usage. I need to know
about the special cases (withinmethod or
The Invocation is either a:
FieldGetInvocation
in that case, you can get the field value by the return of invoke.invokeNext();
or FieldSetInvocation which is when the field is written to. Then the value
would be:
FieldSetInvocation.getValue()
Take a look at the javadocs for all the
Hi Bill,
Thanks a lot!
I can read the values using getValue method.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856106#3856106
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856106
http://docs.jboss.org/aop/aspect-framework/reference/en/html/running.html#jboss
Does that help?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856110#3856110
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856110
thanx for your reply. Is these assumptions right: (I read the link you
suppplied and testet...no go)
1. I can use the supplied directory wich come with the AOP release instead of
jar/unjar the deploy file?
2. I have this file structure
Dmitry,
Please refer to JBoss documentation at
http://docs.jboss.org/aop/aspect-framework/reference/en/html/installing.html
According to the documentation, JBossAOP 1.0.0 should work with JBoss 3.2.6.
I am interesting if it is really possible to run JBossAOP 1.0.0 with JBoss
3.2.6 or it just
Thanks for your reply. Unfortunately it didn't helped, because you described
steps, that I have already done: There is a jboss-aop.deployer directory in the
deploy directory. I post the content:
[EMAIL PROTECTED] all]$ ls -lR deploy/jboss-aop.deployer/
| deploy/jboss-aop.deployer/:
|
Your config is wrong, you should be using AspectDeployer32 instead of
AspectDeployer.
Kev
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855873#3855873
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855873
Are you using JBoss 4.0 or 4.0 RC1 as in your original post? Try JBoss 4.0 if
you haven't already, as there were changes to the deployer architecture between
the two versions.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855880#3855880
Reply to the post :
Hi,
I finally solved my problems now...Thank you, Kabir, for your help. It was
somewhat tricky, although everything was available in tutorials, but some of
them were contradictory etc.
So for those of you, who are beginners of implementing aop, here is what I did
for implementing my first
Kevin
Thank you very much!!!
The JBoss group should update their documentation regarding JBoss 3.2.6 as
following
|
| Edit server/config-name/conf/jboss-service.xml
|
| Add in the beginning of the file
| (after classpath codebase=lib archives=*/ )
| the following configuration:
Thanks for your patience!
I've updated the docs in CVS and will be updated with the next release of JBoss
AOP.
Bill
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855932#3855932
Reply to the post :
It is a snapshot...apologies, this is my bad. I was supposed to at least tag
Javassist's CVS when I released the last AOP, but I didn't.
FYI, you have to use fully-qualified class names with the annotation compiler
when referencing Enums or classes.
Bill
View the original post :
OK.
My problem was that the klass parameter was referring to another class instead
of the annotation class. I have no NPE anymore.
About the fully-qualified names: Will this limitation be lifted in a future
release ? As a programmer I would expect AOP to use the same namespace rules as
the
I don't think this will ever be added. Its not on our TODO list. By the time
we'd have the cycles to implement this, 5.0 may already be widely adopted, then
again, maybe not...
If you were interested in implementing this, please do. I would grant you CVS
access if you did implement it.
I think AOP exists in the 4.0+ versions, not 3.2.x
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855830#3855830
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855830
Hi Kabir,
well, I reinstalled all those things, and I found some mistakes, that's okay.
But unfortunately it does not work completely. I guess it does not make a
difference, if I use server/default/deploy or server/all/deploy, both produce
the same output, when I tried to deploy my
Hi Kabir,
well, I reinstalled all those things, and I found some mistakes, that's okay.
But unfortunately it does not work completely. I guess it does not make a
difference, if I use server/default/deploy or server/all/deploy, both produce
the same output, when I tried to deploy my
The error messages are different now. Previously the problem seemed to be
theAspectManagerService in JBoss was not starting. Can you send me your code
and I'll take a quick look? [EMAIL PROTECTED]
For the standalone stuff, you need to specify the classpaths and path to your
jboss-aop.xml file
BTW, the batch file if you want to run standalone with loadtime instrumentation
for JDK 1.5 is:
bin/run-load15.bat
for running a compiletime intrumented standalone app
bin/run-precompiled.bat
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855569#3855569
Can you post the link for the WIKI POJO example you mentioned?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855571#3855571
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855571
Okay, I've sent the code to your e-mail-address.
I'll try things out as soon as possible.
Thanks
OLLI
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855615#3855615
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855615
When deploying your stuff, I get the same error as you. Your packaging is not
quite there. The jar containing the jboss-aop.xml file must have the suffix
.aop. Also, if this is not the same as your main jar file, it is a good idea
to combine them in an .ear file since loadtime instrumentation
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855541#3855541
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855542#3855542
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855542
Seeing as there was another thread on this problem, just to make sure I
downloaded JBoss 4.0 and JBoss AOP and tried it for myself.
Here are the exact steps I took:
1) Download JBoss 4.0 from
http://prdownloads.sourceforge.net/jboss/jboss-4.0.0.zip?download
2) Download JBoss AOP FINAL
Strange, I am pretty sure there was a way to turn this off last time I checked
(months ago), but it does not appear to be there now unless I am missing
something very obvious.
In any case, I have added a fix to cvs, to allow you to specify an optimize
property on the aopc task. Set it to
Hi,
Can you please provide some more details? E.g, structure of your packages,
jboss-aop.xml file, stacktrace etc.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855332#3855332
Reply to the post :
Sorry the jboss-aop-file was not sent properly:
Here it is:
?xml version='1.0' encoding='UTF-8' ?
Thanks
OLLI
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855347#3855347
Reply to the post :
Okay, I'll try:
Here is the aspect code:
package aspect;
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
import org.jboss.aop.joinpoint.InvocationResponse;
public class myAspect implements Interceptor {
public String getName() {
return
I don't know, why I cannot post the content of that file, maybe I leave out the
tags:
jboss-aop.xml
aop
bind pointcut=execution(public void HelloOliver-work())
interceptor class=aspect.myAspect
bind
aop
Again, very sorry for that
OLLI
View the original post :
Well, I am sure to have used the right jboss-aop-jdk50.deployer-directory. I
put it into jboss-4.0.0/server/default/deploy.
Where does the file jboss-common.jar have to be placed? It is not contained in
the .deploy directory, I simply copied it there. Is this wrong?
Anyway, I changed the
OK, now I am confused. I've had a look in our cvs repository, and
org.jboss.aop.InterceptorPointcut appears to have been deleted about nine
months ago. So it looks like you have some incompatible versions of stuff
somewhere? Make sure you are using the latest JBoss release and the final AOP
Okay, I will try...
Thank you!! Maybe I can ask again later on :-)
OLLI
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855423#3855423
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855423
It works.
Thanks.
[EMAIL PROTECTED]
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855452#3855452
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3855452
---
This SF.Net
Specify the jboss.aop.optimized system property and set it to false, i.e:
| aopc compilerclasspathref=classpath classpathref=classpath
verbose=true
| sysproperty key=jboss.aop.optimized value=true/
|
| classpath path=./bin/
| src path=./bin/
|
I will let Bill comment as to whether or not this is a design feature.
Could you use a mixin class for Externaliable and do the serialization there?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855196#3855196
Reply to the post :
We'll have to add this as a configuration option.
Mixins have the ability to be serialized, but the aspects are not.
The reason for this is that you may be serializing the class across the network
to a node that does not have an aspectized class or does not have the exact or
different aspects
Thanks for the quick responses guys. I guess that might be the reason, and it
makes the sense but as a fundamental java concept it might also make the case
for it.
I mean conceptually speaking this raises the question of what is an object? The
more functionality you push to the aspects the
the following error message occure:
[aopc] BUILD FAILED:
The task doesn't support the nested sysproperty element.
[EMAIL PROTECTED]
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3855289#3855289
Reply to the post :
hi,
could you tell me how to turn JBOSS AOP optimization off in the build.xml of
ant?
|target name=compile depends=prepare
| javac srcdir=.
| destdir=./bin
| debug=on
| deprecation=off
| optimize=off
| includes=**
|
Did you mean this page
http://www.jboss.org/wiki/Wiki.jsp?page=AOPTransactionDemarcation?
annotation has been renamed to metadata, and I have updated the wiki to
show this. If there are any other occurrences, please let me know.
Sorry for the confusion!
View the original post :
It should be possible to change method arguments at call joinpoints.
Your example works with the call joinpoint if you turn optimization off
(-Djboss.aop.optimized=false).
Cheers,
Francisco
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854990#3854990
Looks like there's a bug in optimized CallBy invocations?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854991#3854991
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854991
Yes.
Francisco
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854994#3854994
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854994
---
This SF.Net email is sponsored
Hi
It works.
You must use execution joinpoint instead. It won't work with call joinpoint
as it doesn't make sense. Even if it works with AspectJ, when I think about
call type it looks strange to change called method's arguments from caller
context.
Is there some special reason you can't use
Michael, ask for AspectWerkz support on AspectWerkz mailing list
(subscribe by browsing there: http://aspectwerkz.codehaus.org)
Alex
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854773#3854773
Reply to the post :
hi,
what i really want to do is try to change the arguments of method for a system
class by interceptor. so i can only use the call joinpoint. it is possible to
get the argument of the caller, but i do not know how to set (change) the
argument of the callee.
[EMAIL PROTECTED]
View the
Bill Burke wrote : nope, never got around to implementing it although it would
be pretty easy to add.
|
| You need it? Or is it just a checklist for you?
|
It is not a must-have feature, but it would help me a little bit. But I think I
can achieve my goal (per-thread logging across
Can we specify timeout for Asynchronous Aspect ? How to do that in weblogic ?
Regards,
Ravi
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854676#3854676
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854676
1/Yes.The asynchronous aspects does support timeout value.
With jdk1.4,u have two options to specify the value:
* In your code,when u flag the method as an asynchronous method
/** @@org.jboss.aspects.asynchronous.aspects.jboss.Asynchronous
(timeout=5000)*/
public long myProcess(){...}
Any plan to support per class scope for Introduction in the near future ?
Thx Claude
FYI.,what Aspectwerkz does in this area :
introduction-def name=mixin
interface=examples.introduction.Mixin
implementation=examples.introduction.MixinImpl
Not anytime soon, but come to think of it you could probably implement it with
the current mechanisms, but you'd have to do it yourself...
|
constructionSomeIntroductionFactory.yourPerClassAspect(this.getClass())/construction
|
| |
| | Get me?
| |
| | Bill
View the
I tried it with JBoss EJB 3 and found that jboss-service.xml was missing in
jboss-aop_1.0.0-FINAL\jboss-40-install\jboss-aop-jdk50.deployer\META-INF. I
figured the problem out by copying the same file from RC2.
Thanks,
Ias
View the original post :
This should be fixed in the download...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854420#3854420
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854420
---
This
Running the Asynchronous Aspect or any others aspects outside of JBOSS server
is quite straitghforward.
They are differents options of deployment based on your requirements (See
Reference doc Chap 10)
I personally tested two configurations with Tomcat 5.0
JDK 1.4 using the precompiler.
Use JBossAOP, not AspectWerkz.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854502#3854502
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854502
---
This SF.Net email
Simply check out all of jboss-head, and create a project called thirdparty,
that points to the jboss-head/thirdparty module, as outlined here:
http://www.jboss.org/developers/guides/eclipse-howto/index (the ordering of the
projects might be somewhat out of date, but should give you the general
Just wanted to respond back to this thread what the problem is and potential
resolutions, so it is useful to other people.
This problem with redeployment stems from the fact the the AspectManger inside
of the AOP framework in certain cases can be loaded inside a different
ClassLoader than the
Is this an anonymous inner class or just an inner class? I'm pretty sure there
is a test in the testsuite somewhere for inner classes.
If you send me a testcase, I can try it out. [EMAIL PROTECTED]
Bill
View the original post :
I'd be satisfied with that. That's exactly what I meant.
Tomasz
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854045#3854045
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854045
I will take a look at today.
I do want to give you an update on what I have found. It is definetly a classloading
issue.
If in my scoped WAR File, I incldue the jboss-aop*.jar's, the issue does not happen. I
can redeploy all day long. THat makes sense, because at that point I am using my
Thanks very much !!
Rajiv
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854072#3854072
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854072
---
This SF.Net email is
Ok, this is implemented in CVS. It will be in next release.
Bill
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854075#3854075
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854075
nope, never got around to implementing it although it would be pretty easy to add.
You need it? Or is it just a checklist for you?
Bill
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854085#3854085
Reply to the post :
I take that backincluding the aop jar files does not solve the problem.
When incuding the jar files, the intercepted code is, for all purposes ignored.
It looks like when using your own scoped version of those jar files, either the
aop$classAdvisor$aop or the _instanceAdvisor returns that
The console is a little weird...
It will only show bindings for LOADED classes. If you execute the code, you should
see the bindings.
If you execute the code, and the aspect is is UNBOUND in the webconsole, then there is
a bug in the webconsole.
ANOTHER THING:
By default, class load time
Of course, J2EE TCK may not explicitly reference Aspects or AOP instrumentation. I
even wonder if J2EE will ever talk about AOP as it may sound a little too
invasive/disruptive to let bean developers to play with.
But does JBoss plan to implement the strict constraints of J2EE constructs
Bill Burke wrote : It will only show bindings for LOADED classes. If you execute the
code, you should see the bindings.
|
You are right, my advice is bound when I instantiate a class and everything works as
expected.
Bill Burke wrote : I suggest using the precompiler because currently,
anonymous wrote : I suggest using the precompiler because currently, load-time
transformation is a HUGE memory hog.
I'm nearly finished an alternative load-time which has a much better memory footprint.
I've been working on a different version of the classpool that doesn't store the same
JBoss has passed certification awhile ago now.
The J2EE TCK tests do not test the behavior in question and there are no plans to
implement any strict constraints or stricter verifier.
FYI, it seems Chiba has implemented synchronized blocks, so your fix is scheduled for
the next AOP release.
The memory is not released. What is created is Javassist data structures. I can't
release the memory because class transformation happens at class load time. A class
may be transformed, then another class that references that transformed class may have
joinpoints affected by that
1 - 100 of 643 matches
Mail list logo
