August 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Portal] - Re: Virtual hosts and multiple portal server instances

by lukin

Hi, guys! Who can say clearly what is going on with virtual host feature implementation? I'm new to JBoss portal source, but it seems there's no such beast in in svn "trunk". Is something done already from last year when this tread started? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074865#4074865 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074865

18 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - WISE 0.1 released (generic web based ws invoker)

by maeste

We are proud to announce this release. This is the first release of wise based on wsconsume tool api of jbossws. In fact the client is generated using on the fly wsconsume api and compiling generated code. Take a look to this post on our blog: http://www.javalinux.it/blogs/index.php?title=wise_0_1_released&more=1&c=... Any comment is welcome View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074862#4074862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074862

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using jdocbook

by steve.ebersole＠jboss.com

"nbhatia" wrote : That worked like a charm! Thanks. Either should work. The lookup uses the following paradigm to determine the classloader to use: | ClassLoader loader = Thread.currentThread().getContextClassLoader(); | if ( loader == null ) { | loader = ResourceHelper.class.getClassLoader(); | } | So maven seems to not be setting up the classloader the way I would expect. Not too sure about that one. I'll have to ask the maven folks. "nbhatia" wrote : | One more question. Are these plugins intended for document generation only or also for a project site (replacing maven's site plugin and the xdoc format)? | I only intend to use it for our reference manuals. I am sure it could be fitted to render sites pretty easily. In fact, Jason and I discussed that at one point. BTW, the maven site generation facility allows other forms besides xdoc... There is even early support for simplified docbook. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074861#4074861 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074861

18 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: portletbridge/web-clipping

by cdelashmutt

I'm so frustrated trying to work with the portletbridge project, that I'm seriously considering either hacking up portletbridge to allow alternate tranformation chains or reimplementing it altogether. Do you think there is value in trying to modify portletbridge to allow alternative (and possible simpler) transformers? Would it still make sense to try and enhance portletbridge if we want to provide the more enhanced UI for clipping partial pages? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074857#4074857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074857

18 years, 7 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Warning when trying to use a deployment context in error

by adrian＠jboss.org

The way this works has been completely redone: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114516 You'll never be asked to process a context that is in error (or one of its related contexts in the same context errored). It's not in jboss-head yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074840#4074840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074840

18 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Common package update to rev 7949

by julien＠jboss.com

see http://jboss.org/index.html?module=bb&op=viewtopic&p=4074836#4074836 [/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074838#4074838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074838

18 years, 7 months

1
0
0 / 0

[QA of JBoss Portal] - HTTPTestRunner update

by julien＠jboss.com

I have updated the test runner so that it does not require to be subclassed to specify the file that will be deployed for the tests. Before we had to have: | public class MyTest extends HTTPTestRunner | { | public MyTest() | { | super("mytest.war"); | } | } | now we can use: | <zest todir="${test.reports}" | name="org.jboss.portal.test.framework.runner.HTTPTestRunner" | outfile="TEST-MyTest" | id="MyTest"> | <parameter name="archive" value="mytest.war"/> | </zest> | the id will just be used by the XML report generator to identify the test name (until we write a test runner not based on JUnit ant tasks). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074836#4074836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074836

18 years, 7 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Warning when trying to use a deployment context in error?

by wolfc

Can we have a warning when we use a deployment context in error? In normal operation this condition should never occur, but I'm seeing some problems in EJB3Deployment in regards to unwinding a deployment. So the context ends up in error and test fails. From a clients perspective the symptons are the same as a deployment failure. So I try the run again to spot the deployment failure. Allas nothing happens (I mean nothing at all shows up in the log about this deployment). Only when I turn on tracing I see a meak message scroll by: ignoring deployment context in error. So spending an entire day staring at EARStructure was wasted (apart from spotting other problems). So can we have a warning in nice friendly letters with the words: "Don't Panic" somewhere? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074834#4074834 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074834

18 years, 7 months

1
0
0 / 0

[Design of JBoss ESB] - Message Body simplication

by mark.little＠jboss.com

We had some discussions around simplifying the way in which most developers could use the Message Body. Here's what the updated Programmers Guide says on the subject: Extensions to Body Although you can manipulate the contents of a Message Body directly in terms of bytes or name/value pairs, it is often more natural to use one of the following predefined Message structures, which are simply different views onto the data contained in the underlying Body. As well as the basic Body interface, JBossESB supports the following interfaces, which are extensions on the basic Body interface: i. org.jboss.soa.esb.message.body.content.TextBody: the content of the Body is an arbitrary String, and can be manipulated via the getText and setText methods. ii. org.jboss.soa.esb.message.body.content.ObjectBody: the content of the Body is a Serialized Object, and can be manipulated via the getObject and setObject methods. iii. org.jboss.soa.esb.message.body.content.MapBody: the content of the Body is a Map<String, Serialized), and can be manipulated via the setMap and other methods. iv. org.jboss.soa.esb.message.body.content.BytesBody: the content of the Body is a byte stream that contains arbitrary Java data-types. It can be manipulated using the various setter and getter methods for the data-types. Once created, the BytesMessage should be placed into either a read-only or write-only mode, depending upon how it needs to be manipulated. It is possible to change between these modes (using readMode and writeMode), but each time the mode is changed the buffer pointer will be reset. In order to ensure that all of the updates have been pushed into the Body, it is necessary to call flush when finished. You can create Messages that have Body implementations based on one of these specific interfaces through the XMLMessageFactory or SerializedMessageFactory classes. The need for two different factories is explained in the section on Message Formats, which is described later in the document. For each of the various Body types, you will find an associated create method (e.g., createTextBody) that allows you to create and initialize a Message of the specific type. Once created, the Message can be manipulated directly through the raw Body or via the specific interface. If the Message is transmitted to a recipient, then the Body structure will be maintained, e.g., it can be manipulated as a TextBody. The XMLMessageFactory and SerializedMessageFactory are more convenient ways in which to work with Messages than the MessageFactory and associated classes, which are described in the following sections. Note: these extensions to the base Body interface are provided in a complimentary manner to the original Body. As such they can be used in conjunction with existing clients and services. Message consumers can remain unaware of these new types if necessary because the underlying data structure within the Message remains unchanged. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074819#4074819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074819

18 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using jdocbook

by nbhatia

That worked like a charm! Thanks. Now the only remaining problem is the MalformedURLException, which I mentioned earlier. I have the following parameter defined in my stylesheet and FOP doesn't seem to like it. | <xsl:param name="html.stylesheet">../shared/css/html.css</xsl:param> | One more question. Are these plugins intended for document generation only or also for a project site (replacing maven's site plugin and the xdoc format)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074814#4074814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074814

18 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2007