September 2007 - jboss-dev-forums

[Design of Clustering on JBoss (Clusters/JBoss)] - HA-JMS - master node

by rarondini

Hi all, When JBoss is deployed in a cluster environment with HA-JMS, which is the politics to choose the master node (JBoss 4.0.5) ?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083650#4083650 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083650

17 years, 1 month

1
0
0 / 0

[Design of Security on JBoss] - Security Integration in JBAS5

by anil.saldhana＠jboss.com

I want to jot down the current effort at integrating security into AS5. At the container level (web/ejb), I am injecting 3 things via the deployers: a) ISecurityManagement instance - this is just a interface to obtain the SecurityManager(AuthenticationManager,AuthorizationManager,AuditManager etc) given a security domain. (The default implementation that will be injected will be based on JNDI. So if I say securityManagement.getAuthenticationManager, that is internally going to do a JNDI lookup). b) DefaultSecurityDomain - a security domain string to fall back on. c) SecurityContextClassName - The Container creates a security context in the thread of execution. This FQN tells which SecurityContext implementation needs to be created. The container after creating the SC, injects the SecurityManagement instance into the SC, such that whenever any code asks the SC for a SecurityManager, it can delegate it to the SecurityManagement instance. war-deployer-beans.xml | |  | <bean name="WarDeployer" class="org.jboss.web.tomcat.service.deployers.Tomcat | Deployer"> | ... |  | <property name="securityManagement"> | <inject bean="JNDIBasedSecurityManagement"/> | </property> | |  | <property name="securityContextClassName">org.jboss.security.plugins.JBos | sSecurityContext</property> | Similar case exists for the EJB deployer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083648#4083648 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083648

17 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Re: Maven Migration Status

by wesleyhales

I just checked in the maven config and successfully built the ant and maven build for common. Let me know if I missed anything. To build common using maven: - Make sure you checkout the toplevel pom in jboss portal root. - Checkout modules and from the common or module directory run: mvn install or mvn install -Dmaven.test.skip=true (this will skip the tests and build the jar no matter what) - The only test failing is URLNavigatorTestCase and I was hoping someone could help me out with it. I see that it is traversing different files using the URLNavigator but have no idea why? - I also had to copy the junit jar from downloaded thirdparty and replace the one in tools/lib. Otherwise tests would not run. They are a few kb in size difference, but didn't look any further once it started working. - I was able to find most of the 3rd party stuff already in the jboss maven repo, but will have to add these: tools/lib/cargo-core-uberjar-0.8.jar tools/lib/ant-launcher.jar tools/lib/ant-nodeps.jar tools/lib/junit.jar I was unsure about adding the custom junit jar, does it change much? - Finally, not too important, but in the root portal pom.xml there is a place to add project & developer information so everyone feel free to add theirs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083640#4083640 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083640

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: DeployerConfig vs. WebMetaData

by scott.stark＠jboss.org

WebMetaData should be the application specific metadata. According to Brian the DeployerConfig elements he is talking about are really web app specific. Technically there should not be anything other than config like what the descriptor names are, packages to exclude from the web app class loader config, etc. that should be at the deployer config level that would be concerns with regard to leaking to the WebMetaData. If they did it would just be noise. Its reasonable to have WebMetaData defaults at the deployer level though. This is no different than the shared web.xml/context.xml descriptors. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083637#4083637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083637

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Handling component references

by scott.stark＠jboss.org

No, we need an EarIntegrationDeployer that has as inputs the various container metadata that needs ear level metadata merging into it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083635#4083635 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083635

17 years, 1 month

1
0
0 / 0

[Design of JBoss Build System] - Re: Modules depend on jboss-j2ee instead of jboss-javaee

by pgier

I guess eclipse was picking it up from a different place. Anyway, I will change the maven poms to use the correct dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083628#4083628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083628

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: DeployerConfig vs. WebMetaData

by anil.saldhana＠jboss.com

Is it right, if I say that the WebMetaData is the glorified view of settings emanating from web.xml, jboss-web.xml and deployer custom settings? I am still uncomfortable with the deployer custom settings leaking into the WebMetaData. DeployerConfig was for that particular reason. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083626#4083626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083626

17 years, 1 month

1
0
0 / 0

[Design of the JBoss Web Container] - Re: UseJBossWebLoader=false causes JSF to fail

by patwary_shiva

I am also having same issue . we are not using jsf . we are using 4.02 version of jboss 2007-09-12 14:51:58,276 DEBUG [org.jboss.web.tomcat.tc5.jasper.TagLibCache] Failed to scan: jsf-libs/myfaces-impl.jar java.io.FileNotFoundException: C:\jboss-4.0.2\server\custom\deploy\jbossweb-tomcat55.sar\jsf-libs\myfaces-impl.jar at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80) at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89) at org.jboss.web.tomcat.tc5.jasper.TagLibCache.scanJar(TagLibCache.java:309) at org.jboss.web.tomcat.tc5.jasper.TagLibCache.loadStandardTlds(TagLibCache.java:229) at org.jboss.web.tomcat.tc5.jasper.TagLibCache.init(TagLibCache.java:99) at org.jboss.web.tomcat.tc5.jasper.TagLibCache.getLocation(TagLibCache.java:88) at org.apache.jasper.JspCompilationContext.getTldLocation(JspCompilationContext.java:519) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:417) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1543) at org.apache.jasper.compiler.Parser.parse(Parser.java:126) at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:100) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:146) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:267) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:255) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:293) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:238) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083624#4083624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083624

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: DeployerConfig vs. WebMetaData

by bstansberry＠jboss.com

For the clustering bit, http://jira.jboss.com/jira/browse/JBAS-4708 . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083622#4083622 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083622

17 years, 1 month

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: DeployerConfig vs. WebMetaData

by scott.stark＠jboss.org

The DeploymentUnit should just the way for accessing deployment specific metadata, the WebMetaData being the typical piece. At some point we should just completely pojoize the web deployer layer and throw out the legacy stuff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083621#4083621 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083621

17 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2007