July 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Wiki] - Re: JBOSS WIKI INSTALLATION - HELP NEEDED

by dayal_78

szimano, Thanks for the response. When do you think the next relase for JBoss wiki is going to be? We are trying to deploy it in our company. Thanks Dayal View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957070#3957070 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957070

19 years, 3 months

1
0
0 / 0

[Design of JBoss Wiki] - Re: JBOSS WIKI INSTALLATION - HELP NEEDED

by szimano

The install instruction is available here http://labs.jboss.com/wiki/InstallingJBossWiki Unfortunately beta is and old binary working only with JBoss Portal 2.0.1RC3. Hold on before we prepare binary distro for 2.2 portal. Cheers, Tomek View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957067#3957067 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957067

19 years, 3 months

1
0
0 / 0

[Design of JBoss Wiki] - Re: JBOSS WIKI INSTALLATION - HELP NEEDED

by dayal_78

Hi, Just now, I did the following install.... 1. Downloaded the JBOSS AS + Portal bundle - jboss-portal-2.4.0-CR1 and installed it. 2. Downloaded EJB3 package - JBOSS-EJB3-RC8-FD and completed the install instructions 3. Downloaded the JBoss wiki source bundle - jbosswiki-beta and made the following changes to filedatasource.properties: set 'pathToMedia = C:\TEMP' set 'pathToAttachements = C:\TEMP' After doing the above, I built wiki.ear using maven 1.0.2 by 1. running maven prepare-repo 2. maven wiki:localbuild 4. I then copied the generated wiki.ear file to the deploy directory and started JBOSS 5. When I access 'http://localhost:8080/wiki', the default portal page is getting displayed !! Can someone shed somelight on this???? Thanks -D View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957060#3957060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957060

19 years, 3 months

1
0
0 / 0

[Design of Kosmos] - Re: Config Kosmos Portlet

by aron.gombas

Great news. Plz the answer for your other question in the other forum. Enjoy. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957049#3957049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957049

19 years, 3 months

1
0
0 / 0

[Design of Kosmos] - Re: Kosmos Jira Authentication using Soap

by aron.gombas

Please study the Kosmos Reference Manual. Basically, you have to take care of two things: Configuring the proper "service.url" in portlet.xml anonymous wrote : | JIRA Monitoring portlet | | This portlet monitors projects hosted by JIRA, a popular issue tracking and project management application. It helps you by giving a quick overview about the state of several projects in a single place. | | Please note that Kosmos provides two different service implementations to serve data for this portlet. You can choose between these two implementations simply by specifying different service.url parameters for the portlet: | | 1. http://localhost:8080/kosmos-server/kosmos-services/jira-service: the data will be served by a service that downloads JIRA webpages and analyzes their HTML content. | 2. http://localhost:8080/kosmos-server/kosmos-services/jirasoap-service: the data will be served by a service that uses the JIRA SOAP remote API to download information directly from the JIRA web application. Please note that you have to enable the SOAP interface in the JIRA settings, in this case | ...and... Configuring the proper "monitored.urls" in the portlet.xml anonymous wrote : | JiraSoapMonitoringPortlet: list of colon-separated JIRA SOAP service URL and saved filter names related to the projects to monitor. Username and password is required for proper authentication. For example: http://soaptester:soaptester@jira.atlassian.com/rpc/soap/jirasoapservice-... for unreleased versions. | HTH. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957047#3957047 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957047

19 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: testing the new list server

by sohil.shah＠jboss.com

testing list server View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957040#3957040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957040

19 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: VFSDeploymentScanner questions

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : There should be two types of "hot deployment". | | 1) The original version which is just a way to add urls (with no | chance of overrides by a management tool). | | 2) A more up-to-date version for the management tool | where you can specify a directory rather than a single url to deploy. | This is just a more convenient way of specifying urls. | | In fact, (1) is just a subset of (2) where there is no "GUI" intervention This difference is just convienence of expressing deployments. What I'm asking about is whether the ProfileService is the only source of deployments, or whether the hot deployment service bypasses the ProfileService and uses the MainDeployer directly (as it does today). The latter would effectively eliminate the hot deployment service as usable in prod environments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957026#3957026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957026

19 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: VFSDeploymentScanner questions

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : "scott.stark(a)jboss.org" wrote : | | 2. The ordering of deployments based on suffix is largely useless with the current deployment framework that has any number of deployers operate on a deployment. Correct startup order is a function of deployers adding the correct dependency metadata to the kernel deployments they create. Any deployment package level dependency control would seem to be an aspect/deployer that used its own metadata to create place holder kernel objects (or used equivalents from jsr77) to introduce coarse grained dependencies. The question is, is this assement correct, and do we need such a coarse grained deployment aspect/deployer? | | | | I'm not sure I understand this? | | The deployments contain many pieces of metadata that are deployed | in an aspectized way. They still need an ordering, but based on the | metadata rather than the deployment suffix. | | e.g. aop must be before classloading, classloading before | "instantiation", etc. | | Other dependendencies (between services and entry points) | should be via the microcontainer. We are trying to remove | the implicit dependency of the suffix ordering and replace it | with a semi-implicit (i.e. added by deployer) dependency. | | e.g. If an ejb uses another ejb/datasource then the | "enc/resource/reference" deployer adds this. | e.g.2. Trivially, the above also requires a dependency on naming | e.g.3. A web deployment has a dependency on the web container | etc. Right, this is what I'm saying. The previous notion of ordering the deployment contexts based on the deployment suffix has little meaning since the deployments get passed through the ordered list of deployers/aspects. Only if there are implicit dependencies like a legacy service looking up an ejb via jndi would there be meaning in having the sar depend on the target ejb jar. Such a dependency should an explicit deployment context level dependency rather than some deployment name based ordering. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957015#3957015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957015

19 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: JBAOP-87 - Annotation Dependencies

by kabir.khan＠jboss.com

Is the plan for it to be possible to create nested annotations from the MC xml? e.g some xml like | <bean name="Intercepted" class="org.jboss.test.microcontainer.support.SimpleBeanImpl"> | <annotation ....> | </bean> | which could result in something like | @Containing(dependency=@TestAnnotationDependency(data="Dependency1"), | contained=@Contained(dependencies= {@TestAnnotationDependency(data="Dependency2"), @TestAnnotationDependency(data="Dependency3")})) | public class NestedAnnotatedSimpleBeanImpl extends SimpleBeanImpl | { | | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957011#3957011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957011

19 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 embeddable class folders

by wolfc

"bill.burke(a)jboss.com" wrote : Yes. They are used for the E-EJB3 distribution. FOr testing, these must be built to test the standalone distribution! Please don't remove. Or, move the creation of these to be a dependency of the 'standalone-tests' target. | | Thanks What if we jar the jars and create a jar jars class loader? Then we don't have to unjar any artifacts produced by other projects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957001#3957001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957001

19 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2006