July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-1557) WAB support for servlet 3.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-1557?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1557: -------------------------------- Assignee: Thomas Diesler Fix Version/s: 7.2.0.Alpha1 Git Pull Request: https://github.com/jbossas/jboss-as/pull/2570 (was: https://github.com/jbossas/jboss-as/pull/2570) Forum Reference: http://community.jboss.org/message/619443#619443 (was: http://community.jboss.org/message/619443#619443) > WAB support for servlet 3.0 > --------------------------- > > Key: AS7-1557 > URL: https://issues.jboss.org/browse/AS7-1557 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.2.0.Alpha1 > > > Bruno says, > ... in JBoss AS 7, how can I make the DemoServlet work with Servlet 3.0 annotations? I've tried this, but it does not work. The JBoss OSGi deployment interceptor is expecting a web.xml, which is not required with WebServlet 3.0 specs. > > Caused by: org.jboss.osgi.deployment.interceptor.LifecycleInterceptorException: Cannot obtain web.xml from: vfs: > Am I missing something here or WebServlet 3.0 is not yet supported in JBoss AS 7 WABs? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-4842) Verify that OSGi subsystem runs on Windows

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4842: ----------------------------------- Summary: Verify that OSGi subsystem runs on Windows Key: AS7-4842 URL: https://issues.jboss.org/browse/AS7-4842 Project: Application Server 7 Issue Type: Task Affects Versions: 7.1.2.Final (EAP) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (AS7-1488) Document how Extension-List works in the class loading guide

by Stuart Douglas (JIRA)

Document how Extension-List works in the class loading guide ------------------------------------------------------------ Key: AS7-1488 URL: https://issues.jboss.org/browse/AS7-1488 Project: Application Server 7 Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
1
0 / 0

[JBoss JIRA] (AS7-5074) @Inject'ed bean at another @Singleton is null on @PostConstruct (both with @Startup)

by Bruno Borges (JIRA)

Bruno Borges created AS7-5074: --------------------------------- Summary: @Inject'ed bean at another @Singleton is null on @PostConstruct (both with @Startup) Key: AS7-5074 URL: https://issues.jboss.org/browse/AS7-5074 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld, EJB Affects Versions: 7.1.1.Final Reporter: Bruno Borges Assignee: Stuart Douglas module-a.jar and module-b.jar are both TL (top-level) delpoyments on JBoss AS 7.1.1 * module-a.jar has a @Singleton/@Startup named SharedBean * module-b.jar has a @Singleton/@Startup named Bootstrap module-b.jar depends on module-a.jar through jboss-deployment-structure.xml: <jboss-deployment-structure> <delpoyment> <dependencies> <module name="deployment.module-a.jar" /> </dependencies> </deployment> </jboss-deployment-structure> When I enable module-a.jar, SharedBean is started fine (it has a @PostConstruct that logs its state) When I enable module-b.jar, Bootstrap fails checking the @Inject'ed SharedBean on its @PostConstruct Files: ------------------------- # module-a.jar @Startup @Singleton public class SharedBean { @PostConstruct public void started() { LOGGER.info("SharedBean has started"); } } ------------------------- # module-b.jar @Startup @Singleton public class Bootstrap { @Inject private SharedBean sharedBean; @PostConstruct public void started() { LOGGER.info("sharedBean is null? " + (sharedBean == null)); } } There's no ClassNotFoundException or NoClassDefFoundError. The bean is just not injected correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
6
0 / 0

[JBoss JIRA] (AS7-3804) Singletons start/stop in the MSC thread

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-3804: ----------------------------------- Summary: Singletons start/stop in the MSC thread Key: AS7-3804 URL: https://issues.jboss.org/browse/AS7-3804 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.1.Final This could cause MSC thread pool starvation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
3
0 / 0

[JBoss JIRA] (AS7-5088) Weblogic EJB Lookup fails from JBoss AS

by Badal Pradhan (JIRA)

Badal Pradhan created AS7-5088: ---------------------------------- Summary: Weblogic EJB Lookup fails from JBoss AS Key: AS7-5088 URL: https://issues.jboss.org/browse/AS7-5088 Project: Application Server 7 Issue Type: Bug Environment: JBoss AS 7.1.0.Final EJB Deployed in Weblogic 10 OS - Windows XP JDK - jdk160_05 (Used by jboss) Reporter: Badal Pradhan I am trying to access EJB deployed in Weblogic 10 by its RemoteInterface from JBoss. My initial context config for lookup is as below: Hashtable<String,String> wlContextEnv = new Hashtable<String,String>(); wlContextEnv.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"); wlContextEnv.put(Context.PROVIDER_URL, "t3://localhost:7001"); wlInitialContext = new InitialContext(wlContextEnv); During access the bean it throws the below exception: java.lang.LinkageError: Failed to link weblogic/corba/client/cluster/ORBSocketFactory ..... Caused by: java.lang.ClassNotFoundException: com.sun.corba.se.spi.legacy.connection.ORBSocketFactory Since the above class belongs to jdk rt.jar then what is the issue here? Am I missed any config for it. Note: I have wlclient.jar in my ear/lib. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2012