There have been several posts recently asking how one might plug a CORBA
servant into JBoss as a method to wrap EJB calls behind customized IDL or to
just utilize extant servants as is. Given this interest, it seems like
writing an MBean that could load/manage any CORBA servant class would be
The distributed test case framework for JMS using jgroups has been
implemented(Based on remoting DTF source base)
Scenario covered
1.One producer
2.One synchronous consumer
Its based on the distributed test framework developed by Tom for remoting
org/jboss/dtf/**
I copied it into
Looks interesting. At the very least, it could be used as a skeleton for people
that want to do this sort of things.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874059#3874059
Reply to the post :
Following a talk with the cheif architecture of WebSphere, Bob High, they are
now pushing a new container, which works with EJB in a batch mode.
Mainly a batch is a non interactive operation, that take a long time on big set.
You usually do a loop on a set, creating a checkpoint every x
Hi,
Trying to remember to use the dev-forum instead of direct mails for this jboss
ide dev stuff ,)
I have now updated the jsp.ui plugin to be compilable against 3.1M6, but
unfortunately I could not find a easy way to filter out _jspx field and
method names - so that will be a small regression
And where is the spec behind this?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874109#3874109
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874109
---
SF email is
Ben Wang has created a web container aspect for fine-grained replication of
session data. This brings up a previous issue of where aspects live and how
they are deployed in non-trivial environments like JBAS.
Currently there are aspects like security living in the aspects module which do
not
setHarURL was needed simply to allow the deployer to inject this value into the
mbean. Use of this at runtime or through the console is highly discouraged ;)
Another thought is that in the scheme y'all are proposing (provided multiple
interceptors can process the deployer init stuff) we could
Correct, and this is certainly the future deployment process architecture as a
deployment is just a packaging with instructions on how to configuration the
various aspects.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874114#3874114
Reply to the post :
[EMAIL PROTECTED] wrote : One issue that is not clear in this discussion is
do I have sufficient info to go obtain the source for every jar I find in the
dist? Ultimately I want this for patches as well. The ideal roundtrip behavior
is that I would point a ant task to a release and have it spit
[EMAIL PROTECTED] wrote :
| 1. Iterate over all the jars in a release, collecting the component id
version from each jar manifest.
|
This assumes we add the compoent id to the manifest.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874117#3874117
anonymous wrote :
| * This does not address non-archive artifacts, such as text files. We would
need to add manifests to these text files if we wanted to be able to resolve
their source components. Is this necessary for this use case (or in general)?
|
No. In general configuration files
Quote from Roy:
Clean co from CVS today. I noticed changes to the window behaviour as many
people including Scott have suggested.
A few questions:
1. Is this configurable? Can we set the old behaviour or new one in a
descriptor? Not important for me. I like the new way better.
2. I have to
sorry this is a result of the changes I checked in yesterday. I guess I should
have explained those better ahead of everyone running into them ;)
I had a hard time to get rid of the old behavior, where the portlet in 'main'
was automatically maximized. Since maximized now actually works ;) the
Well, this is not exactly as an Aspect. But rather an switch inside Tomcat.
Still, I have a tc5-clutster.aop jar that needs to deploy under all/deploy. In
addition, I need to access it from testsuite so my POJO can precompile with
annotationc and aopc.
What's the best practice?
View the
Just wondering if you ever solved this problem. I am experiencing the same issue
Running Solaris 10, j2se 1.4.2_07, JBOSS3.2.1/TomCat 4.2.x
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874125#3874125
Reply to the post :
I like the new behaviour. I think it is in keeping with other portal vendors
and is more windows-like.
Point 2: The cmsportlet and forumsportlet were the default portlets in their
assigned pages. They were always in normal mode. Since they showed nothing in
normal mode, this needs to be
Thanks Max =)
I am moving over and re-structuring the JBossIDE CVS as I type this, so I will
probably need to merge your changes. Are they very severe?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874130#3874130
Reply to the post :
The CVS repository of JBossIDE is going to be undergoing a major restructure
and move today.
We hope to address these concerns:
1) JBossIDE needs to be moved to the top level of the JBoss' CVS
structure (no longer under contrib/)
2) A new directory hierarchy:
| $JBOSS_CVS_ROOT/
|
looks good. Is the structure like how wtp/eclipse is doing their stuff ? (i'm
too lazy to check ,)
Shouldnt the update site be there somewhere too ?
The eclipse30/eclipse31 looks like a good comprimise.
View the original post :
No - just two classes. You will detect them very quickly if you dont have the
right version when you use M6 ,)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874134#3874134
Reply to the post :
Sorry, the update site is considered another top level component called
update-site. =)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874137#3874137
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874137
[EMAIL PROTECTED] wrote : The important part here is that it remains
configurable, either by a deployer or end-user. I'd like to see exactly how
configurable it can be. For instance, when I maximize a portlet, can I still
have side-bar navigation to its left? Some people may elect to not have
Thanks Adrian, that's a lot clearer now.
I've now moved the transaction handling logic into the interceptor stack.
So far, I've put it into TransactionInterceptor.
TransactionInterceptor does the following:
It intercepts ConnectionDelegate.createSessionDelegate() and creates a new
local tx
Finally I managed to make Xerces schema infrastructure to help me create a test
schema object graph as shown by this testcase - test:
| /**
| * Test Xerces ability to create XML schema
| * @throws Exception
| */
|public void testSchemaCreation() throws Exception
|
The WS-I is working on a security profile. It is based off of WS-Security.
The link is here:
http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0-2005-01-20.html
It is currently in working draft.
-Jason
View the original post :
The CVS Restructure / initial import has been finished. I will be running both
repositories simultaneously over the weekend to try and sync up anything that
isn't finished updating and make sure the new modules are working as they
should.
If anyone else wants to test feel free =)
View the
Over the weekend and Monday I will be implementing automated builds for
JBossIDE. We are doing this so that component developers can depend on nightly
and integration builds for the latest code / integration targets. Currently,
The JBossIDE Core, JBossAOP Developer, and EJB3 Tools are hosted
This forum is meant specifically for the development of JBossIDE. If you have
any questions or support issues related to the use of JBossIDE, please visit
our users forum:
http://jboss.com/index.html?module=bbop=viewforumf=201
View the original post :
To start, since this is probably going to be a long thread, will state how the
test cases work using the benchmark decorators.
ThreadLocalDecorator (and all the other decorators that accept number of
threads and loops) - for each thread specified in the number of threads, there
will be a new
I think that they way things work in the previous post should remain and would
be a natural extension of the base JUnit TestCase.
However, I think there should be some changes to this behavior if running a
TestCase that is specifically a server TestCase (when talking about having
[EMAIL PROTECTED] wrote :
| Also, another change to the default JUnit test case behavior is that there
will NOT be a new instance of the server test created when it moves to the next
test method. This is due to not knowing where the clients will be in their
test run, so can't tear down a
32 matches
Mail list logo
