Some documentation about AOP Asynchronous Method Invocation
available on the WIKI.
http://jboss.org/wiki/Wiki.jsp?page=AOPAsynchronousMethodInvocation
Rgds,Claude
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831238#3831238
Reply to the post :
http://www.j
As you said, JavaScript is probably adequate for the task and more admin friendly. It
may be possible to support multiple scripting languages provided they support limiting
their domain. Meaning I only want you to script what I expose to you nothing more.
JavaScript (aka ECMA) is probably a m
"Until you get" -- and I thought you were planning to be one of us? Membership in the
us is low, just send real good code :-)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831234#3831234
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=post
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
I like the idea of a mail solutions framework. Until you get the Exchange
functionality going that will probably be the bread and butter.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831222#3831222
Reply to the post :
http://www.jboss.org/index.html?module
Have you heard of Groovy? Apparently it's a newer Java-based scripting language that
doesn't have the funkiness of Jython syntax. Javascript would be adequate I think.
Probably more "admin" friendly.
WWMCSED? What would MCSEs do? ;-)
Hit my blog here: Links for Andy's links all together in link
Pretty much the tcl is set whenever a call enters into a container, be it jmx, ejb,
web. Its needed when transitioning from the microkernel into a deployment context that
can introduce new classes or class versions due to a deployment.
It would generally seem that the TCL is the more typical lev
Ok, thanks.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Adrian Brock
> Sent: Saturday, April 17, 2004 6:01 AM
> To: [EMAIL PROTECTE
Hi, Stan.
Nothing special about this Fibo tutorial. I just followed the instructions step by
step and it woked. I even changed the internal code from UTF-8 to Big5(Chinese,
Taiwan) and it woked too. Can you tell me how to attach my files to this post or I
just send an email attached with my fil
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Bugs item #877172, was opened at 2004-01-14 22:59
Message generated for change (Comment added) made by anders5737
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=877172&group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Take a look at this: http://james.apache.org/provided_matchers_2_1.html, and this:
http://james.apache.org/provided_mailets_2_1.html.
James has an API called the "Mailet API". Its a great idea but kind of an abortive
impelmentation: http://james.apache.org/mailet_api_2_1.html.
"
The Mailet API
View results here -> http://tck2.jboss.com/cc/?log=log20040417134819Lbuild.18
BUILD COMPLETE - build.18Date of build: 04/17/2004 13:48:19Time to build: 18 minutes 29 secondsLast changed: 04/17/2004 13:35:15Last log entry: Use logging from the common module not jmx logging
I'm doing my pre-testing for M1RC1 and I have to say, I'm impressed. The TLS and SSL
support is awesome. Also sending mail feels remarkably faster than JAMES (which I use
presently) even using SSL!!! I feel really good about this release. Everyone
especially: Eric, MikeA, MikeK and Kabir sho
Hi albertfang,
Some of your message could not be seen. Can you tell me any trick to follow the
Tutorial? What's wrong in our code?
Thanks,
-stan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831193#3831193
Reply to the post :
http://www.jboss.org/index.h
this tx observable pattern is everywhere in Jboss
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831184#3831184
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831184
---
go ahead. See the TestServer and all for how I think we should set up. Just start
the pieces we need inside of the unit tests. Later we'll have multinode tests. Right
now we need basic tests like "if there is user XYZ in the respository and I send him a
mail from himself, does it get deliver
GOF does it my way.
It would be trivial to write an alternate ObservableLight :-)
Transaction synchronization would also help to avoid multiple fine grained
fireChanged() events inside a transaction. Similar to JBossCacheAOP
View the original post :
http://www.jboss.org/index.html?module=bb&op
Blogged about this:
http://jboss.org/jbossBlog/blog/bburke/?permalink=Fluid+AOP.html
Thoughts anybody? I still need to understand when/how context classloader gets set in
JBoss.
Bill
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831181#3831181
Reply to t
I'll have JDK 1.5 annotation support sometime next week in CVS. Doing another beta of
JBoss AOP soon too.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831180#3831180
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=383
I hear you on the usage of Subject. I saw it is the way the GOF named it. I still
prefer "Observable".
Getting at the state is done by passing the reference to the subject in your
implementation. It makes for a great and simple implementation. If we could pass
some metainformation as to wh
this is great work adrian,
Bill, I think what I hear you say is that we can now deploy a self contained aspect.
The aspect knows where he wants to be bound. The aspect could export its pointcuts,
he knows he wants to listen on set* etc. It will make for superior deployment formats
for aspec
Bugs item #936962, was opened at 2004-04-17 15:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936962&group_id=22866
Category: JBoss-IDE
Group: None
Status: Open
Resolution: N
Bugs item #936924, was opened at 2004-04-17 17:20
Message generated for change (Comment added) made by eprst
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936924&group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitt
Hi,
same here :-(
I just started Eclipse from c/l and got:
---
Process:
jar:file:/usr/opt/eclipse3.0M8/plugins/org.jboss.ide.eclipse.xdoclet.core_1.2.230/./xdoclet-ejb-module-1.2b3-dev.jar!/META-INF/xtags.xml
| Exception while reading: ejb.home null Attention: Can't add
org.jboss.ide.eclipse
Thomas or Tom,
A lot of the JMX testsuite tests for JBossMX are failing.
Either the tests should be fixed or the reason why they
fail analysed.
Last time I ran it, there were three "known issues"
non of them important.
Regards,
Adrian
On Sat, 2004-04-17 at 14:00, Adrian Brock wrote:
> I'll fix i
Bugs item #936924, was opened at 2004-04-17 17:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=936924&group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
P
I'll fix it in both 3.2 and head
My fault for not keeping head in line.
Regards,
Adrian
On Sat, 2004-04-17 at 13:42, Adrian Brock wrote:
> The JMX logging framework was removed from 3.2.0 but never
> from head. When Tom backported jmx from head into 3.2.4RC1
> he also copied the old jmx logging f
It wouldn't even be testing what I thought it'd be testing. I wonder what the real
cutoff points are between
1. The VM developer
2. The Container developer
3. The container user (using JSP, other services on top of the container)
Anyways, I'll be quiet about things now :)
View the original post
The JMX logging framework was removed from 3.2.0 but never
from head. When Tom backported jmx from head into 3.2.4RC1
he also copied the old jmx logging framework.
Regards,
Adrian
On Sat, 2004-04-17 at 13:25, Scott M Stark wrote:
> In trying to cleanup the logging for bug [ 936465 ] JCA layer has
Bug Fix:
Catch unchecked exceptions generated by the ping operations
Catch unchecked exceptions from the user's ExceptionHandler
Avoids uncaught Runtime exceptions killing the ping task/clock daemon
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831167#38311
Okay. I'm glad the VM is good at that. Like your JCA FAQ says, "Are you *sure* you
want JCA?"
Steve
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831168#3831168
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831168
In trying to cleanup the logging for bug [ 936465 ] JCA layer has
invalid assumption about Log4jLoggerPlugin
https://sourceforge.net/tracker/index.php?func=detail&aid=936465&group_i
d=22866&atid=376685
I see that we have two seperate frameworks:
jmx org.jboss.mx.logging
comon org.jboss.logging
I don't like nifty or cool. It just over complicates things and makes things buggy.
10 is nothing like enought for a test. The JIT doesn't even kick in until you
thousands of repetitions. JITs are bettter at this than you could ever be and
will only get better over time.
View the original post :
Supporting multiple selectors is too complicated for an initial version.
Rebuilding the HashMap (don't use a hashtable or vector or any collection that does
synchronization unless you are lazy - often you are already synchronized on some other
object) should be optimized in conjunction with this
great news for M1RC1. i'm minimally tidying up/filling out some of the code (mainly
script runner) and plan to commit shortly. but i noticed in another forum thread you
mentioned not to commit till after RC1, and i wasn't sure that would apply here. (just
let me know if so and i'll postpone).
"[EMAIL PROTECTED]" wrote : Generically it is a callback interface like
MBeanRegistration
| for services that want to know about their container and their configuration
|
|
| | public interface ContainerRegistration
| | {
| |void setContainer(Container container);
| |
Mine is working smoothly. Unfortunately, I don't know how to attach my files to this
post. Maybe
I can e-mai you if you give me your email address.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831158#3831158
Reply to the post :
http://www.jboss.org/index.
Genman,
With regard to your proposal, what's happenning on server's restart? Is the hashtable
rebuilt at startup?
Regards,
Stephane
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831154#3831154
Reply to the post :
http://www.jboss.org/index.html?module
42 matches
Mail list logo