On Wed, 30 Jan 2002, marc fleury wrote:
Bill got my hear yesterday where he pitched the interceptor design on the 3.0 client
side.
Instant love.
We are not that far from it in fact, it a bit of renaming and factory game on the
server. Essentially the client does
Generic Proxy -
|OK. So that's the current state? What's the Handler in this context - is
|that the JRMPInvokerProxy, for example?
no we are talking about 3.0 the handler is one of the proxy classes with
EJB behavior but disconnected from the transport (JRMP-Proxy was 2.0).
The current state is that this has
Bugs item #511164, was opened at 2002-01-31 04:25
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511164group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 7
Submitted By: Christian Riege (lqd)
Assigned to:
Bugs item #511172, was opened at 2002-01-31 04:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511172group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 7
Submitted By: Christian Riege (lqd)
Assigned to:
Bugs item #511172, was opened at 2002-01-31 04:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511172group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Open
Resolution: Duplicate
Priority: 7
Submitted By: Christian Riege (lqd)
Assigned to:
User: lqd
Date: 02/01/31 05:01:39
Removed: src/main/org/jboss/mq/pm/file Tag: Branch_2_4 TxLog.java
Log:
- this class is never used
___
Jboss-development mailing list
[EMAIL PROTECTED]
User: lqd
Date: 02/01/31 05:14:42
Modified:src/main/org/jboss/mq/server Tag: Branch_2_4
QueueManager.java
Log:
- re-setup logger to use the Queue's name in logging output
Revision ChangesPath
No revision
No
Bugs item #511172, was opened at 2002-01-31 04:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511172group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Open
Resolution: Duplicate
Priority: 7
Submitted By: Christian Riege (lqd)
Assigned to:
Bugs item #510397, was opened at 2002-01-29 14:36
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=510397group_id=22866
Category: JBossServer
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: William A. Kaufman (wkaufman)
Assigned
olger Engels wrote:
I'm glad to see, that jboss will support pluggable interceptors on the
client side, now. You can do cool things with that. Think of:
...
o caching interceptor (for getters)
How will that work in practice? Aren't the interceptors stateless,
without being
Greg, Jules, Luke!
thx much for your replies. Indeed, the '*' role authentication constraint
seems to match my issue very well if it also lets through
null-authenticated/credential calls ...
If I can help to patch SecurityHandler (jetty4 or backport to jetty3,
perhaps), please let me know.
It actually goes a little furthur than that. I first tried to take out
the security interceptor in the MDB interceptior chain. This works fine
util your message bean then tries to call another EJB. So it would seem
that the Security Interceptor needs to just act as a login for the MDB.
Scott
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Luke
Taylor
Sent: Thursday, January 31, 2002 9:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] TODO: client side interceptors
olger Engels wrote:
I'm glad to see, that jboss will
Which is what I mean by MDBs needing a different SecurityInterceptor.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Dave Smith [EMAIL PROTECTED]
To: Scott M Stark [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Bugs item #511280, was opened at 2002-01-31 08:49
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511280group_id=22866
Category: JBossSX
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Annegret Sternagel (annegret)
Assigned to:
So then in JMSContainerInvoker add the code to read the jboss metadata
and then invoke the inteceptor chain with the appropreate princpal and
credidentals? Or should the JMS message actually set properties in the
message itself and a new Security Invoker to read this info and set the
On Thu, 31 Jan 2002, Bill Burke wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Luke
Taylor
Sent: Thursday, January 31, 2002 9:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] TODO: client side interceptors
olger Engels
Authentication and Authorization need to be two seperate security
interceptors. Authentication needs to validate the principal and associate
the Subject with the MethodInvocation. The Authorization interceptor
will handle role based permissions and run-as identities. The default
MDB interceptor
Bugs item #511343, was opened at 2002-01-31 10:40
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511343group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Matt (mpetteys)
Assigned to:
Maybe I missed a message about this. But I am wondering, is war
deployment broken?
Here is all that gets logged about the war (when inside an EAR, or when
placed directly in deploy)
Auto deploying: file:/home/david/proxeno/jboss/tmp/deploy/proxeno.war
New UCL with url
No, the standard JMS Message interface needs to be used to obtain
a configurable principal and credential property. Any JMS provider
may be used with MDBs.
- Original Message -
From: Dave Smith [EMAIL PROTECTED]
To: Scott M Stark [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday,
OK. So I had a quick peek at the SpyMessage and there is a field called
producerClientId that should do the trick. So I add an interceptor in
front of the security interceptor that takes the first argument of the
invoke , casts to a SpyMessage, grabs the id and sets the Principal in
the
Holger Engels wrote:
On Thu, 31 Jan 2002, Bill Burke wrote:
You're right here. EJBs have no asynchronous interface like CORBA object do.
Arrgh! You mean the dreaded oneway keyword? I'd forgotten all about that.
Plus, in EJB the request is not exposed like in CORBA as well.
Some
|only the last one is directly implemented by the dynamic proxy. security
|and transactions are somewhat transcendent/magic. A drawback of multiple
|interfaces is that you have to cast the object to these particular
|interfaces in order to use them.
These apis are not exposed in the dynamic
Guys,
enough talking,
To the slew of new developers looking for fame and glory... this is a neat
little advanced assignement, make the interceptor stack for the EJB client
real and configurable from jboss.xml OKA? shouldn't be that hard nor that
simple. Couple of days. Bill you are banned from
Also, it should be the JMSContainerInvoker, not the Athorization interceptor
that is dealing with obtaining the principal info from the JMS layer.
- Original Message -
From: Scott M Stark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 31, 2002 11:04 AM
Subject: Re:
could be let me check
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of David
|Budworth
|Sent: Thursday, January 31, 2002 10:55 AM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] Is WAR deployment broken?
|
|
|Maybe I missed a message about this.
If you are having offline JBoss deploying Petstore, and getting error in regards to:
(1) http://java.sun.com/dtd/application_1_3.dtd or
(2) http://java.sun.com/dtds/web-app_2_3.dtd
Make sure when you re-build PetStore to point the J2EE_HOME to version j2sdkee1.2.1
why is there a lock on the cvs manual out there? it is from yesterday any
ideas? it prevents me from updating the website
marcf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
It happens occasionally when a cvs client hangs. You have to ask the
sourceforge admins to remove the lock.
- Original Message -
From: marc fleury [EMAIL PROTECTED]
To: Jboss-Development@Lists. Sourceforge. Net
[EMAIL PROTECTED]
Sent: Thursday, January 31, 2002 5:04 PM
Subject:
Why is cvs all locked up suddenly? I am also seeing a lock preventing
a co of jboss-all currently. I have asked for this lock to be removed.
cvs server: Updating jboss-all/server/src/etc/beaninfo
cvs server: Updating jboss-all/server/src/etc/beaninfo/jaws
cvs server: [14:30:08] waiting for
cvs server: Updating manual/lib
cvs server: [14:33:01] waiting for anoncvs_jboss's lock in
/cvsroot/jboss/manual/lib
cvs server: [14:33:31] waiting for anoncvs_jboss's lock in
/cvsroot/jboss/manual/lib
cvs server: [14:34:01] waiting for anoncvs_jboss's lock in
/cvsroot/jboss/manual/lib
cvs
Bugs item #474977, was opened at 2001-10-25 10:59
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=474977group_id=22866
Category: JBossServer
Group: v2.4 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Matthew Bishop (mattbishop)
I have put a request as well, priority was bumped up by support
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Thursday, January 31, 2002 2:47 PM
|To: JBoss Dev
|Subject: [JBoss-dev] Now I also see a lock
|
|
|Why is cvs all
I don't see any of the mdb-xxx fields you are talking about in the current
code so these are all elements you added? I'm looking at version 1.42
of the JMSContainerInvoker.java.
What is needed is the names of the JMS properties from which the
principal and credentials are obtained. The princpal
I've just updated my tree (swerving around manual/lib and server/etc
manually).
cleaned and rebult from scratch.
everything runs up nicely, but then I try to deploy an ear that deployed no
problem a couple of weeks ago (last time I dared update my tree).
I'm not sure what is going on.
My
User: jules_gosnell
Date: 02/01/31 16:32:24
Modified:jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
Log:
some way further to configurable snapshot strategies and intervals,
Revision ChangesPath
1.13 +4 -2
User: jules_gosnell
Date: 02/01/31 16:32:24
Modified:jetty/src/main/org/jboss/jetty/util NaiveTimeOutManager.java
Log:
some way further to configurable snapshot strategies and intervals,
Revision ChangesPath
1.4 +5 -3
User: jules_gosnell
Date: 02/01/31 16:32:24
Modified:jetty/src/main/org/jboss/jetty
JBossWebApplicationContext.java Jetty.java
JettyService.java JettyServiceMBean.java
Log:
some way further to configurable snapshot strategies and
User: jules_gosnell
Date: 02/01/31 16:32:24
Modified:jetty/src/main/org/jboss/jetty/session
DistributedHttpSession.java
DistributedHttpSessionManager.java
Log:
some way further to configurable snapshot strategies and intervals,
yeah that is a bug I am seeing as well, I don't know what is going on but I
got a reproducible case
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jules
|Gosnell
|Sent: Thursday, January 31, 2002 4:23 PM
|To: marc fleury
|Cc:
Bugs item #511461, was opened at 2002-01-31 14:50
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511461group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Åsmund Hjulstad (ahjulsta)
Assigned
Bugs item #511503, was opened at 2002-01-31 16:02
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=511503group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Ken Sipe (kensipe)
Assigned to:
User: dsundstrom
Date: 02/01/31 17:26:58
Modified:src/etc/conf/default standardjbosscmp-jdbc.xml
Log:
Changed type-mapping element in defaults to datasource-mapping as is
required in the new dtd.
Revision ChangesPath
1.15 +2 -2
User: dsundstrom
Date: 02/01/31 17:47:09
Modified:src/resources/cmp2/ejbselect/META-INF jbosscmp-jdbc.xml
Log:
Updated to new dtd.
Revision ChangesPath
1.2 +14 -15
jbosstest/src/resources/cmp2/ejbselect/META-INF/jbosscmp-jdbc.xml
Index: jbosscmp-jdbc.xml
User: dsundstrom
Date: 02/01/31 17:47:09
Modified:src/resources/cmp2/readonly/META-INF jbosscmp-jdbc.xml
Log:
Updated to new dtd.
Revision ChangesPath
1.2 +15 -16jbosstest/src/resources/cmp2/readonly/META-INF/jbosscmp-jdbc.xml
Index: jbosscmp-jdbc.xml
User: dsundstrom
Date: 02/01/31 17:47:09
Modified:src/resources/cmp2/relationship/META-INF jbosscmp-jdbc.xml
Log:
Updated to new dtd.
Revision ChangesPath
1.3 +14 -14
jbosstest/src/resources/cmp2/relationship/META-INF/jbosscmp-jdbc.xml
Index:
User: dsundstrom
Date: 02/01/31 17:43:52
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata
JDBCRelationMetaData.java
JDBCRelationshipRoleMetaData.java
Log:
Moved ejb-relationship-role element outside of the mapping element.
JBoss daily test results
SUMMARY
Number of tests run: 259
Successful tests: 106
Errors:128
Failures: 25
[time of test: 1 February 2002 2:46 GMT]
[java.version:
I found this on the apache web site. I interpret this statement slightly
different the Jakarta guys. To me it looks like the J2EE licensees are
getting nervous about the high quality of the open source J2EE
implementations (i.e., JBoss), and feel the only way to distinguish them
selves in the
JBoss daily test results
SUMMARY
Number of tests run: 259
Successful tests: 107
Errors:128
Failures: 24
[time of test: 1 February 2002 3:7 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 259
Successful tests: 107
Errors:128
Failures: 24
[time of test: 1 February 2002 3:39 GMT]
[java.version:
User: schaefera
Date: 02/01/31 19:52:59
Modified:src/bin Tag: Branch_2_4 run.sh
Log:
Added Cygwin support
Revision ChangesPath
No revision
No revision
1.19.4.1 +11 -0 jboss/src/bin/run.sh
Index: run.sh
This is now implemented in both Jetty4 and Jetty3_1 CVS branches.
Hopefully I'll get a release of both of these out in the next week
cheers
Jung , Dr. Christoph wrote:
Greg, Jules, Luke!
thx much for your replies. Indeed, the '*' role authentication constraint
seems to match my
JBoss daily test results
SUMMARY
Number of tests run: 259
Successful tests: 107
Errors:128
Failures: 24
[time of test: 1 February 2002 4:9 GMT]
[java.version:
ignore the noise, focus on the work
marcf
PS: I agree with your analysis, the J2EE certified brand is weaker for
every download we have and we are not certified. Having the most downloaded
server not certified takes a lot of credibility out of the brand. I was
reading the forum this was
56 matches
Mail list logo
