Hi!
I again read through chapter 8.4 of the spec
Passivating scopes must be explicitly declared
@ScopeType(passivating=true).
For example, the built-in session and conversation scopes defined
in Section 8.5, “Context management for built-in
scopes” are passivating scopes.
The reason is
allow passivation of scopes @SessionScoped and @ConversationScoped
--
Key: OWB-83
URL: https://issues.apache.org/jira/browse/OWB-83
Project: OpenWebBeans
Issue Type: Bug
can we assume ordinary java objects also have a place on JNDI tree?
just as EJB 3.1 components names have become standard?
that's some thing we can propose to be added web-beans (Java Dependency
Injection) standard.
On Fri, Mar 13, 2009 at 12:30 PM, Matthias Wessendorf mat...@apache.orgwrote:
dunno.
Since Gavin is OS experienced I'd have thought that the complete
process of that spec is much more open than it really is today...
-M
On Tue, Mar 10, 2009 at 3:59 PM, Mark Struberg strub...@yahoo.de wrote:
Matthias,
I was just wondering if there is also a readonly JSR-299 EG list one
On Thu, Mar 12, 2009 at 10:34 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
The (EJB centric) Spec of @Resource says that the resource will always be
looked up via JNDI [1]. I guess mainly because the whole J2EE stuff is really
JNDI centric.
Otoh in environments where no or only a
Hi Mark,
correct me if I am wrong.
as 2009-01-22 the new name for web-beans is Java Contexts and Dependency
Injection
JNDI is a mechanism for naming and discovery of Java Objects in a
distributed system.
it lets components (complex heavy objects) to be discovered with a mechanism
other than
I'm facing a really naughty problem while I try to add the
implements Serializable
to all @SessionScoped test beans:
First I thought that Javassist has a bug with reading some _valid_ classes
because I found a few sources which insist on using cglib instead of javassist
in this case
defining a bean @Serializable will case javaassist exceptions
-
Key: OWB-84
URL: https://issues.apache.org/jira/browse/OWB-84
Project: OpenWebBeans
Issue Type: Bug
Proxy objects are always Serializable in the specification
From: Mark Struberg strub...@yahoo.de
To: openwebbeans-dev@incubator.apache.org
Sent: Friday, March 13, 2009 9:02:20 PM
Subject: problems with @Serializable
I'm facing a really naughty problem while I
[
https://issues.apache.org/jira/browse/OWB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-84.
--
Resolution: Fixed
fixed by checking if Serializable is already in the interface list before
adding it
oki thanks!
So my fix is ok I guess.
Still I'm not sure if I like it to be forced to have each and every
@SessionScoped and @ConversationScoped bean to be serializable!
Usually it's a good idea for clusters etc, but otoh there are some good
arguments against it in some cases. But thats a
uff, should be fixed now.
please retest.
txs and LieGrue,
strub
--- Mark Struberg strub...@yahoo.de schrieb am Fr, 13.3.2009:
Von: Mark Struberg strub...@yahoo.de
Betreff: Re: [jira] Created: (OWB-83) allow passivation of scopes
@SessionScoped and @ConversationScoped
An:
[
https://issues.apache.org/jira/browse/OWB-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OWB-83.
--
Resolution: Fixed
Fix Version/s: M2
Assignee: Mark Struberg (was: Gurkan Erdogdu)
fixed
13 matches
Mail list logo
