[JBoss JIRA] Created: (JBAS-3969) IOException: unknown protocol: vfsfile
by Thomas Diesler (JIRA)
IOException: unknown protocol: vfsfile
--------------------------------------
Key: JBAS-3969
URL: http://jira.jboss.com/jira/browse/JBAS-3969
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossAS-5.0.0.CR1
All webservice tests fail because of
Caused by: java.io.IOException: unknown protocol: vfsfile
at java.net.URL.readObject(URL.java:1217)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.ws.core.jaxrpc.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:112)
An application client is bound into JNDI. At lookup time and object is deserialized that contains a URL property with the vfsfile protocol. It seems that the JNDI layer is not aware of the URLStreamHandlerFactory
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBBUILD-326) JBossRetro missing getDeclaredAnnotations; getAnnotations implementation is deficient
by David Lloyd (JIRA)
JBossRetro missing getDeclaredAnnotations; getAnnotations implementation is deficient
-------------------------------------------------------------------------------------
Key: JBBUILD-326
URL: http://jira.jboss.com/jira/browse/JBBUILD-326
Project: JBoss Build System
Issue Type: Bug
Components: JBossRetro
Affects Versions: JBossRetro-1.0.4.GA
Reporter: David Lloyd
Priority: Minor
Fix For: JBossRetro-1.0.5.GA
I put in a fix to JBossRetro to add support for getDeclaredAnnotations on Method, Field, Constructor, and AccessibleObject. In doing this I realized that getAnnotations seems to be doing what getDeclaredAnnotations is supposed to be doing; according to the JDK javadocs, getAnnotations is supposed to return inherited annotations as well as declared annotations, whereas getDeclaredAnnotations only returns annotations on the specific object.
I committed a change to implement getDeclaredAnnotations which essentially duplicates the current getAnnotations behavior, but someone may want to go in and enhance getAnnotations.
I'm attaching the patch that I committed in case I'm wrong and someone wants to revert it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBAS-3781) Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present
by Anil Saldhana (JIRA)
Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present
----------------------------------------------------------------------------------------
Key: JBAS-3781
URL: http://jira.jboss.com/jira/browse/JBAS-3781
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1, JBossAS-5.0.0.Beta
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2, JBossAS-4.0.6.CR1
The following Subject Context push (with null Subject) to establish client security context should not be performed if the user has configured a RunAsIdentity in the caller bean.
/* The security context must be established before the cache
lookup because the activation of a session should have the caller's
security context as ejbActivate is allowed to call other secured
resources. Since the pm makes the ejbActivate call, we need to
set the caller's security context. The only reason this shows up for
stateful session is that we moved the SecurityInterceptor to after
the instance interceptor to allow security exceptions to result in
invalidation of the session. This may be too literal an interpretation
of the ejb spec requirement that runtime exceptions should invalidate
the session.
*/
SecurityActions.pushSubjectContext(mi.getPrincipal(), mi.getCredential(), null);
The resolution is:
if(SecurityActions.peekRunAsIdentity() == null)
SecurityActions.pushSubjectContext(mi.getPrincipal(), mi.getCredential(), null);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months