jboss-dev-forums — The jboss development forum posts

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Problem with aop 1.3

[<kab...@jb...>]

There is an example called "injboss" which does loadtime weaving in jboss.

Make sure that you add org.jboss.injbossaop to the "Include" attribute of the aspect manager service

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884101#3884101

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884101

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Problem with aop 1.3

[robert.schwegler <nu...@jb...>]

It took me many many hours and finally here is the right hint! I'm using JDK5, aop1.3 and 4.0.3RC1.

Now as I'm using AspectManagerServiceJDK50, I see much more information in the log, but I'm looking for an example with the JBoss Server. Are there any tricks with the class-loader? I wrote an XMBean and deployed it in a sar-directory:

package xmbeanprimer;
  | import xmbeanprimer.Traceable;
  | import xmbeanprimer.Billable;
  | public class Greeter {
  |     private int greetingsSent = 0;
  |     @Billable
  |     public String hello() {
  |         this.setGreetingsSent(this.greetingsSent+1);
  |         return "Hello World (" + this.greetingsSent + ")!";
  |     }
  |     public int getGreetingsSent() {
  |         return this.greetingsSent;
  |     }
  |     public void setGreetingsSent(int c) {
  |         this.greetingsSent = c;
  |     }
  | }

 I wrote an aspect and put it in a jar called: adp.aop with an advice:
...
  |     @Bind (pointcut="execution(java.lang.String xmbeanprimer.Greeter->@Billable(
  | ))")
  |     public Object methodAdvice(MethodInvocation invocation) throws Throwable {
  | ...

My BillingAdvice got deployed:
22:47:52,119 INFO  [STDOUT] [debug] Looking for aspects in: adp.BillingAdvice
  | 22:47:52,139 INFO  [STDOUT] [debug] Found @Aspect in: adp.BillingAdvice
  | 22:47:52,249 INFO  [STDOUT] [trying to transform] $Proxy54
  | 22:47:52,249 INFO  [STDOUT] [debug] There are no caller pointcuts!
  | 22:47:52,259 INFO  [STDOUT] [debug] was $Proxy54 converted: false
  | 22:47:52,419 INFO  [STDOUT] [trying to transform] $Proxy55
  | 22:47:52,419 INFO  [STDOUT] [debug] There are no caller pointcuts!
  | 22:47:52,429 INFO  [STDOUT] [debug] was $Proxy55 converted: false
  | 22:47:52,549 INFO  [AspectDeployer] Deployed AOP: file:/D:/bin/jboss/jboss-4.0.3RC1/server/default/deploy/adp.aop

But my Advice is not found:
22:47:54,913 INFO  [STDOUT] method matched binding execution(* *->@xmbeanprimer.Billable(..)) public java.lang.String xmbeanprimer.Greeter.hello()
  | 22:47:54,913 INFO  [STDOUT] [debug] added advisor: xmbeanprimer.Greeter from binding: jar:file:/D:/bin/jboss/jboss-4.0.3RC1/server/default/tmp/deploy/tmp51167adp.aop!/META-INF/jboss-aop.xml0
  | 22:47:54,993 ERROR [MainDeployer] Could not create deployment: file:/D:/bin/jboss/jboss-4.0.3RC1/server/default/deploy/greeter01.sar/
  | org.jboss.deployment.DeploymentException: java.lang.ClassNotFoundException: No ClassLoaders found for: adp.BillableInterceptor; - nested throwable: (java.lang.RuntimeException: java.lang.ClassNotFoundException: No ClassLoaders found for: adp.BillableInterceptor)

Thanks for any hints how to package it cleanly. My target is to do runtime weaving! I checked the examples but all of them compile all the files in one directory. Have I overseen an example?

Regards
Robert Schwegler, Amadeus

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884098#3884098

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884098

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: JBoss 4.0.2, JDK 1.4.2, AOP 1.3, EnableLoadtimeWeaving =

[acxsjones <nu...@jb...>]

That bat file line look like 
%JAVA_CMD%  -Xbootclasspath/p:%AOP_FILES% -classpath %USER_CLASSPATH% %AOPPATH% %AOPCLASSPATH% %MAINCLASS_AND_ARGS%

I can not find anything def on MAINCLASS_AND_ARGS

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884095#3884095

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884095

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: JBoss 4.0.2, JDK 1.4.2, AOP 1.3, EnableLoadtimeWeaving =

[acxsjones <nu...@jb...>]

I try to run create-pluggable-jboss-classloader.bat

I get a memory could not be "written" when trying to run the line after
rem Run instrumented program

I click OK and it goes on a produces jboss-classloader-transformer.jar

I have done the rest of the items in the doc and still do not get my aspect to run.

Are there any class loading or packaging issues.  My ejb is packaged in it's own jar and is in the deploy directory

The jboss-aop.xml is in the deploy directory

The aspects are packaged in a jar that is in the lib directory

Scott

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884094#3884094

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884094

[Jboss-dev-forums] [Design of Mail Services] - Re: Working on JBMAIL-10

[<aco...@jb...>]

it removed the spaces.... +4 at each level 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884086#3884086

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884086

[Jboss-dev-forums] [Design of Mail Services] - Re: Working on JBMAIL-10

[<aco...@jb...>]

eliminate tabs.  they are bad.  Code should be readable.  We format like this:

...
public foo() {  //same line { the way GOD HIMSELF intended.
    if (foo != bar) {
    //4 spaces at each.
    }
}
...

But I don't really care so long as its readible and their aren't tabs and CVS does the proper ^M conversion (no samba copies and weird stuff).  Its best if everyone does as above because the bulk of the JBMS code is written that way, but who cares so long as you can read it and the DIFFS aren't all formatting changes.  (If you DO format, do that as a seperate commit than the actual change)

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884085#3884085

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884085

[Jboss-dev-forums] [Design of Mail Services] - Re: Working on JBMAIL-10

[jeff87 <nu...@jb...>]

I'll try. My actual changes were rather small. I just moved the If block that involved verify-identity upwards in the code before the check to see the domain of where the e-mail was being sent and I changed the If statement itself (&& to an || if I remember correctly). I had reformatted it because the indentation seemed to be all over the place, or at least it was for me when I opened it in Eclipse. If there's a standard tab/space configuration you guys use in Eclipse, let me know and I'll be happy to adjust my Eclipse settings accordingly. I don't know if I can get a new patch to you tonight, probably Friday or Saturday.

Jeff

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884071#3884071

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884071

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: JBoss 4.0.2, JDK 1.4.2, AOP 1.3, EnableLoadtimeWeaving =

[acxsjones <nu...@jb...>]

I do not know how I missed that.  I will give it a try.
Thanks

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884051#3884051

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884051

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: JBoss 4.0.2, JDK 1.4.2, AOP 1.3, EnableLoadtimeWeaving =

[<bil...@jb...>]

Please re-read the documentation.  You need to put the jdk14-pluggable-transformer.jar and also the generated jboss-classloader-transformer.jar in your bootclasspath.  See section

10.3.2 JBoss 4.x and JDK 1.4


BTW, the reason we did this is because the old way was not reliable as it relied on a JBoss specific classloader.  Tomcat and other applications use their own customer classloader in many situations which resulted in things like JSPs not getting aspectized.

BTW, the old EnableTransformer switch still works.  So, if you use EnableTransformer instead of EnableLoadtimeWeaving, you can still use the old way.



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884044#3884044

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884044

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: JBoss 4.0.2, JDK 1.4.2, AOP 1.3, EnableLoadtimeWeaving =

[acxsjones <nu...@jb...>]

More information,
I had this working with JBoss 4.0.1 back in late Dec.
when I was doing research.

I am trying to working on adding this to our production branch.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884043#3884043

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884043

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - JBoss 4.0.2, JDK 1.4.2, AOP 1.3, EnableLoadtimeWeaving = tru

[acxsjones <nu...@jb...>]

I must be missing something.  I am trying to get Loadtime weaving working with JBoss 4.0.2 using jdk 1.4.2 and AOP 1.3

I have set EnableLoadtimeWeaving = true but none of my aspects are being exectuted.

Is there a step by step on how to get loadtime weaving working with the environment I listed above.  Have not been able to find anything

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884039#3884039

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884039

[Jboss-dev-forums] [Design of Mail Services] - Re: Working on JBMAIL-10

[mikezzz <nu...@jb...>]

Hi Jeff,

Thank you for the patch.  I have taken a quick look at it.  Unfortunately you appear to have reformatted most of the file.  I.e. either you are using 8 spaces for tabs or have replaces the spaces with actual tab characters.  Would it be possible to do the fix without making changes to the formatting of the file?  It is not possible for me to see the functional changes made.

Cheers,
Mike.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884031#3884031

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884031

[Jboss-dev-forums] [Design of XDoclet Tags on JBoss (XDoclet/JBoss)] - Re: XDoclet dies on stack overflow (Eclipse plugin)

[1ka <nu...@jb...>]

I have had something similar under IBM's WSAD 5.1.2 (eclipse 2.1) when trying to generate EJBs using IBMs wizard.  The problem went away after I changed the settings to use IBM's 1.4 JDK rather than 1.3.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883982#3883982

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883982

[Jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - JBossMessaging 1.0.0alpha PR1 available

[<ovi...@jb...>]

I've just uploaded a JBossMessaging alpha preview release bundle on sourceforge. The archive is available at http://sourceforge.net/projects/jboss/. It will probably possible soon to download it from the JBoss site as well.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883941#3883941

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883941

[Jboss-dev-forums] [Design of JBoss internal QA (Test Suite)] - Re: Testsuite and localhost

[<ad...@jb...>]

We need to revert JBAS-1864. This is a step backwards.
The keyword is *incremental* builds.

Parameterization should be at runtime.
I don't want to have to rebuild the testsuite to change the host I want to run tests against.

I also eventually want a modular/declarative/incremental testsuite build that I can run 
from inside JBoss/IDE on an embedded JBoss server.

What is the issue with the system properties? They should be accepted in all deployments.
If the problem is that the server uses a different a system property (jboss.bind.address) 
to the testsuite (jboss.test.serverhost, nodeN.xxx.yyy) then we need to address this.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883940#3883940

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883940

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Refactoring Instrumentation in AOP 2.0: Iteration 3

[<bil...@jb...>]

* Write a fully optimized instrumentor that inlines before/after, within the
OPtimized MethodInvocation, ConstructorInvocation, etc... classes.  Remember
that old generated code snippet we sent around before? I'll attach some examples.


  | public class Foo
  | {
  |     private float doit(double stuff) throws TypedException
  |     {
  |     }
  | 
  | 
  |     public static abstract class Joinpoint_doit implements MethodJoinpoint
  |     {
  |         protected Foo target;
  |         protected double arg1;
  | 
  |         protected Joinpoint_doit() {}
  | 
  |         protected Joinpoint_doit(Foo target, double arg1)
  |         {
  |             this.target = target;
  |             this.arg1 = arg1;
  |         }
  | 
  |         public Object dispatch()
  |         {
  |             return new Float(target.doit(arg1));
  |         }
  | 
  |         public Object[] getArguments() {...}
  | 
  |         public abstract float doit(Foo target, arg1);
  |     }
  | }
  | 
  | package org;
  | 
  | public class Foo_Joinpoint_doit extends Foo.Joinpoint_doit
  | {
  |     private Security before1;
  |     private TxDemarcation around1;
  |     private LatchedJoinpoint around2;
  |     private SomeAspect after1;
  |     private SomeAspect after2;
  |     Private AnotherAspect afterThrowing1;
  | 
  |     private int currentAdvice;
  | 
  |     public Foo_Joinpoint_doit(TxDemarcation around1, LatchedJoinpoint around2)
  |     {
  |         this.around1 = around1;
  |         this.around2 = around2;
  |     }
  | 
  |     public Foo_joinpoint_doit(Foo target, double arg1, TxDemarcation around1, LatchedJoinpoint around2)
  |     {
  |         super(target, arg1);
  |     }
  | 
  | 
  |     // for dynamic invoke.
  |     public Object invoke(Object target, MethodJoinpoint jp) throws Exception
  |     {
  |         Object[] args = jp.getArguments();
  |         return new Float(doit((Foo)target, ((Double)args[0]).doubleValue()));
  |     }
  | 
  |     public float doit(Foo target, double arg1) throws TypedException
  |     {
  |         float returnValue;
  | 
  | 
  |         before1.authenticate();
  |         try {
  |             Foo_Joinpoint around = new Foo_Joinpoint(target, arg1, around1, around2);
  |             returnValue = = (Float)(around.invokeNext()).floatValue();
  |             // after needs detyped args so get them from the around advice
  |             args = around.getArguments();
  | 
  |             returnValue = (Float)(after1.doAdvice(this, // static joinpoint
  |                                   new Float(returnValue), // return as a generic object
  |                                   args)).floatValue(); // needs generic args
  | 
  |             returnValue = after2.doAdvice(returnValue); // just typed returnValue needed.
  |         } catch (Throwable t) {
  |             t = afterThrowing1.execute(this, t, args);
  |             t = afterThrowing2.execute(this, t, args);
  | 
  |             if (t instanceof TypedException) throw (TypedException)t;
  |             else if (t instanceof RuntimeException) throw (RuntimeException)t;
  |             else throw new RuntimeException(t);
  |         }
  |         return returnValue;
  |     }
  | 
  |     public FooPolicy getAround3()
  |     {
  |         return (FooPolicy)target.getInstanceAdvisor().getPerInstanceAspect("FooPolicy");
  |     }
  | 
  |     public Object invokeNext() throws Throwable
  |     {
  | 
  |         try {
  |             switch (++currentAdvice) {
  |             case 1:
  |                 return around1.doTransaction(this);
  |             case 2:
  |                 return around2.invoke(this);
  |             case 3:
  |                 InvocationStack.push(this);
  |                 try {
  |                     return new Float(getAround3().doit(arg1));
  |                 } finally {
  |                     InvocationStack.pop();
  |                 }
  |             default:
  |                 return dispatch();
  |             }
  |         } finally {
  |             --currentAdvice;
  |         }
  | 
  |     }
  | }
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883937#3883937

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883937

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Refactoring Instrumentation in AOP 2.0: Iteration 2

[<bil...@jb...>]

For iteration 2, we implement before/after returning/after throwing/finally



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883936#3883936

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883936

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Refactoring Instrumentation in AOP 2.0: Iteration 1

[<bil...@jb...>]

Kabir,

This is to Kabir, but anybody else is welcome to contribute to the
discussion.  For AOP 2.0 I want to rearchitect our code instrumentation to
support a variety of things.  This should be an iterative process so that we
can meet various deadlines for the microcontainer.

Iteration 1:

* Should be able to define different advice chains for inherited methods.
http://jira.jboss.com/jira/browse/JBAOP-154

* Should be able to define different class metadata/annotation overrides for
  inherited methods.

  http://jira.jboss.com/jira/browse/JBAOP-155

* Make the instrumentor pluggable so we can have a heavily (risky) optimized
  version of instrumentation.

* Please rename MethodInfo to MethodJoinpoint or something like that.  Also
  create Constructor and Field structurs that hold the same information as
  MethodInfo's as we will eventually want to pass these structures in as
  parameters when we implement before/after throwing, etc...

* Per method, field, call by chains on a per instance basis.  InstanceAdvisor
  API is too limited.  We should be able to attach AdviceBindings on a per
  instance and on a per ClassAdvisor basis.

The idea is that we generate a classadvisor class at instrumentation time that
is specific for the class it is advising. This class has a
org.jboss.aop.Domain member variable.  A Domain as the same interface as an AspectManager.  Except, when you
add/remove from the Domain, you will be recalculating the interceptor
  stacks.  The InstanceAdvisor is also a generated class.  It extends the
  ClassAdvisor generated class.  It also has its own Domain that is a child of
  the generated ClassAdvisor's domain.  The InstanceAdvisor is different than
  the ClassAdvisor in that it must check to see if the ClassAdvisor's
  interceptor stacks have changed (hot deployment) and recalculate its
  own internal interceptor stacks.  So, the InstanceAdvisor's Domain is a
  child of the ClassAdvisor's, the ClassAdvisor's domain is a child of the
  AspectManager.instance().

You have full freedom to refactor, rewrite, or throw out any code you want.

Here's example code for ideas.


  | public class POJO
  | {
  |    private static Advisor classAdvisor = new POJOAdvisor();
  |    protected volatile Advisor currentAdvisor = getClassAdvisor();
  |    protected Advisor instanceAdvisor = null;
  | 
  |    public Advisor getClassAdvisor()
  |    {
  |       return classAdvisor;
  |    }
  | 
  |    public boolean isInstanceAdvised()
  |    {
  |       return instanceAdvisor != null;
  |    }
  | 
  |    public Advisor getInstanceAdvisor()
  |    {
  |       synchronized(this)
  |       {
  |          if (instanceAdvisor == null)
  |          {
  |             instanceAdvisor = ((POJOAdvisor)currentAdvisor).createInstanceAdvisor();
  |             currentAdvisor = instanceAdvisor;
  |          }
  |       }
  |       return instanceAdvisor;
  |    }
  | 
  |    private int method1(int arg)
  |    {
  |       return ((POJOAdvisor)currentAdvisor).method1(this, arg);
  |    }
  | 
  |    private int method1$aop(int arg)
  |    {
  |       return 0;
  |    }
  | 
  |    private static int methodstatic()
  |    {
  |       return ((POJOAdvisor)classAdvisor).methodstatic();
  |    }
  | 
  |    private static int methodstatic$aop()
  |    {
  |       return 0;
  |    }
  | 
  |    protected static class POJOAdvisor extends Advisor
  |    {
  |       protected long versionId = 0;
  |       protected Domain domain = new Domain(AspectManager.instance(), false);
  | 
  |       public POJOAdvisor()
  |       {
  |          // create interceptor stack based on domain member variable.
  |       }
  | 
  |       public Domain getDomain()
  |       {
  |          return domain;
  |       }
  | 
  |       public POJOAdvisor createInstanceAdvisor()
  |       {
  |          return new POJOInstanceAdvisor(this);
  |       }
  | 
  |       protected MethodInfo method1$MethodInfo = new MethodInfo(/*other stuff */);
  |       protected int method1(POJO target, int arg)
  |       {
  |          if (method1$MethodInfo.interceptors != null)
  |          {
  |             MethodInvocation invocation = new MethodInvocation(method1$MethodInfo, method1$MethodInfo.interceptors); // put in the correct constructor
  |             invocation.setTargetObject(target);
  |             invocation.setArguments(...);
  |             return ((Integer)invocation.invokeNext()).intValue();
  |          }
  |          else
  |          {
  |             return target.method1$aop(arg);
  |          }
  |       }
  | 
  |       private MethodInfo methodstatic$MethodInfo = new MethodInfo(/*other stuff */);
  |       private int methodstatic()
  |       {
  |          if (methodstatic$MethodInfo.interceptors != null)
  |          {
  |             MethodInvocation invocation = new MethodInvocation(methodstatic$MethodInfo, methodstatic$MethodInfo.interceptors); // put in the correct constructor
  |             return ((Integer)invocation.invokeNext()).intValue();
  |          }
  |          else
  |          {
  |             return methodstatic$aop();
  |          }
  |       }
  |    }
  | 
  |    protected static class POJOInstanceAdvisor extends POJOAdvisor
  |    {
  |       protected POJOAdvisor classAdvisor;
  | 
  |       public POJOInstanceAdvisor(POJOAdvisor classAdvisor)
  |       {
  |          this.classAdvisor = classAdvisor;
  |          this.versionId = classAdvisor.versionId;
  |       }
  | 
  |       protected int method1(POJO target, int arg)
  |       {
  |          if (versionId != classAdvisor.versionId)
  |          {
  |             versionId = classAdvisor.versionId;
  |             rebuildInterceptors();
  |          }
  |          return super.method1(target, arg);
  |       }
  |    }
  | 
  | }
  | 
  | 
  | public class POJOChild extends POJO
  | {
  |    private static Advisor classAdvisor = new POJOChildAdvisor(AspectManager.instance());
  | 
  |    public Advisor getClassAdvisor()
  |    {
  |       return classAdvisor;
  |    }
  | 
  |    public void method2()
  |    {
  |       ((POJOChildAdvisor)currentAdvisor).method2(this);
  |    }
  | 
  |    public void method2$aop()
  |    {
  |       // actual code
  |    }
  | 
  |    protected static class POJOChildAdvisor extends POJO.POJOAdvisor
  |    {
  |       protected MethodInfo method1$MethodInfo = new MethodInfo(/*other stuff */);
  |       protected void method2(POJOChild target)
  |       {
  |          if (method1$MethodInfo.interceptors != null)
  |          {
  |             MethodInvocation invocation = new MethodInvocation(method1$MethodInfo, method1$MethodInfo.interceptors); // put in the correct constructor
  |             invocation.setTargetObject(target);
  |             invocation.invokeNext();
  |          }
  |          else
  |          {
  |             target.method2$aop();
  |          }
  |       }
  | 
  |       public POJOAdvisor createInstanceAdvisor()
  |       {
  |          return new POJOChildInstanceAdvisor(this);
  |       }
  | 
  |    }
  | }
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883934#3883934

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883934

[Jboss-dev-forums] [Design of Mail Services] - Re: Working on JBMAIL-10

[jeff87 <nu...@jb...>]

OK, so to finally answer Andy's question:

anonymous wrote : 
  | One more twist. If "localhost" and "localhost.localdomain" and "localdomain" are ALL in the local domain list then I should be able to set any of "test@localhost" or "test@localhost.localdomain" or "test@localdomain" as the from address. Does that make sense?
  | 
  | -Andy
  | 

So I had these domains listed in my jboss-service.xml file:
localhost
localhost.com
localhost.localdomain 
localhost.localdomain.com
localdomain.com

I was able to set the from address domain to each of those and send successfully. So I think the patch I uploaded might be ready for review. I think it's fixed. So being optimistic and assuming I fixed it, what's next?

Jeff

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883932#3883932

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883932

[Jboss-dev-forums] [Design of Mail Services] - Re: Working on JBMAIL-10

[jeff87 <nu...@jb...>]

I was using dev-deploy actually and getting the error below. I tried the deploy task and that deployed just fine. Thanks for the help.

Jeff


  | 19:30:53,025 INFO  [EARDeployer] Started J2EE application: file:/C:/java/jboss-4.0.2/server/default/deploy/mail.ear/
  | 19:30:53,025 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
  | 
  | --- MBeans waiting for other MBeans ---
  | ObjectName: jboss.mail:name=PagedStore,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:service=Hibernate
  |   Depends On Me:
  |     jboss.mail:name=MailBodyManager,type=MailServices
  | 
  | ObjectName: jboss.mail:name=MailBodyManager,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=PagedStore,type=MailServices
  |   Depends On Me:
  |     jboss.mail:name=MailboxManager,type=MailServices
  |     jboss.mail:name=SMTPProtocol,type=MailServices
  | 
  | ObjectName: jboss.mail:name=MailboxManager,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=MailBodyManager,type=MailServices
  |   Depends On Me:
  |     jboss.mail:name=POP3Protocol,type=MailServices
  | 
  | ObjectName: jboss.mail:name=SMTPProtocol,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=UserRepository,type=MailServices,uimanageable=true
  |     jboss.mail:group=Local,name=DomainGroup,type=MailServices
  |     jboss.mail:name=MailBodyManager,type=MailServices
  |     jboss.mail:name=MailListenerChain,type=MailServices
  |   Depends On Me:
  |     jboss.mail:name=SMTP,type=MailServices
  | 
  | ObjectName: jboss.mail:name=SMTP,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=SMTPProtocol,type=MailServices
  | 
  | ObjectName: jboss.mail:name=POP3Protocol,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=MailListener,type=MailServices
  |     jboss.mail:name=MailboxManager,type=MailServices
  |     jboss.mail:name=UserRepository,type=MailServices,uimanageable=true
  |   Depends On Me:
  |     jboss.mail:name=POP3SSL,type=MailServices
  |     jboss.mail:name=POP3,type=MailServices
  | 
  | ObjectName: jboss.mail:name=POP3SSL,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=POP3Protocol,type=MailServices
  | 
  | ObjectName: jboss.mail:name=POP3,type=MailServices
  |   State: CONFIGURED
  |   I Depend On:
  |     jboss.mail:name=POP3Protocol,type=MailServices
  | 
  | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
  | ObjectName: jboss.mail:service=Hibernate
  |   State: NOTYETINSTALLED
  |   Depends On Me:
  |     jboss.mail:name=PagedStore,type=MailServices
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883931#3883931

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883931

[Jboss-dev-forums] [Design of JBoss Portal] - Re: Page info in theme, revisited

[<roy...@jb...>]

"legolas" wrote : I wrote 2 tags that could be useful for others. One tag, named isNotEmptyRegion, is doing the exact opposite of Julian's original isEmptyTag, it evaluates the body only if the region has content.
  | The second tag, named navigation, adds 2 objects to the pageContext within the scope of the tag. These objects allow the layout developer to iterate over the defined pages, and detect the currently active page. If you are interested in the code please let me know how I can submit them your repository.

Can you archive this and send it over to julien, martin, or me please?

"legolas" wrote : 
  | What is the actual purpose of it, is it merely to define each page and its layout, or is it meant to define the whole navigation structure of the portal including page layout?
  | 

To define each its page and the portlets assigned to it. 

"legolas" wrote : 
  | What are your plans about this?
  | 

Our ears are open. ;-)

"legolas" wrote : 
  | Is it, or will it be, possibile to define a renderer per window?
  | 

I'm not sure we've discussed this idea, and I'm not really sure how this has real-world application. Martin (which is on vacation) may be able to elaborate his thoughts on it.

"legolas" wrote : 
  | To test my layout, I created a simple portlet. Only showing some default text. I followed the instructions in chapter 2 of the reference guide and included the descriptors portlet.xml, jboss-portlet.xml, jboss-app.xml and portlet-instance.xml.
  | Which of these re mandatory?
  | 

The above 3 are. Until we have dynamicity (2.2 Blade), this is the way to deploy your portlets.

"legolas" wrote : 
  | BTW the reference guide, paragraph 2.6, describes that the first part of the instance-ref is the application name as defined in the jboss-portlet.xml, I think it should be the jboss-app.xml, is that correct?
  | anonymous wrote : 
  |   | 
  |   | You are correct. I will change it.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883917#3883917

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883917

[Jboss-dev-forums] [Design of JBoss Build System] - Re: JBoss Third Party Build

[<sco...@jb...>]

No reason not to move it. The aop used to be a module in the jboss-4.0 but has now been moved to thirdparty and its classpath should be moved there as well.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883908#3883908

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883908

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Problem with aop 1.3

[<kab...@jb...>]

It will be in the docs for 1.3.1, along with some more aggressive comments in jboss-service.xml

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883895#3883895

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883895

[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: Problem with aop 1.3

[Iapetus999 <nu...@jb...>]

That did it! :)

I didn't see that in the docs anywhere.
Also in the jboss-service.xml in the jboss-aop_1.3\jboss-40-install\jboss-aop-jdk50.deployer\META-INF directory it's listed as code="org.jboss.aop.deployment.AspectManagerService"

Maybe I just missed the doc somehow.



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883889#3883889

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883889

[Jboss-dev-forums] [TODO - DEVELOPMENT] - Re: Volunteer for JAXR TestCases

[pvishnu <nu...@jb...>]

Hi All,

 I recently joined in JBoss network. I have few years experience in java development. I would like to help writing some of the testcases or new development works. Please let me know how i can contribute ?  


Thanks & Regards,
PV

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883878#3883878

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883878