Hi Paul,
Thanks for the input. I'm using the latest Dojo source
from their svn repo. I haven't looked at Dojo's IO
library but I will definitely check it to compare
differences with DWR. BTW, Im already using JSON for
the Tree widget nodes.
Thanks,
Chris
--- Paul McMahan <[EMAIL PROTECTED]> wro
Does it make sense to specify the import element for a configId?
For example:
com.foo
myartifact
123
car
??
com.foo
myartifact
123
car
classes
I'll defer my movement of the cram the defects in by Friday until we see how bad CTS is. Kevan
thinks he might have some initial thoughts on where we stand this week.
Yes, I know the results are secret, that we run them is not :-P
Matt
Aaron Mulder wrote:
I vote we plan to freeze on a Monday
[ http://issues.apache.org/jira/browse/GERONIMO-1824?page=all ]
John Sisson reassigned GERONIMO-1824:
-
Assign To: John Sisson
> geronimo-config-1.0.xsd incorrectly documents that classes can be
> comma-separated inside a filter element
> ---
[ http://issues.apache.org/jira/browse/GERONIMO-1825?page=all ]
John Sisson closed GERONIMO-1825:
-
Resolution: Fixed
> Only one filter element can be specified inside a hidden-classes or
> non-overridable-classes element in plans
>
Only one filter element can be specified inside a hidden-classes or
non-overridable-classes element in plans
Key: GERONIMO-1825
URL: http://issues.apache.org/jira/browse/
Should we just update the documentation in the schema to reflect the
code? Should we be avoiding having XML elements that require further
parsing (e.g. for comma-separated values) so that other tools can
process the XML easily?
John
John Sisson (JIRA) wrote:
geronimo-config-1.0.xsd incorrec
[ http://issues.apache.org/jira/browse/GERONIMO-1824?page=all ]
John Sisson updated GERONIMO-1824:
--
Summary: geronimo-config-1.0.xsd incorrectly documents that classes can be
comma-separated inside a filter element (was: geronimo-config-1.0.xsd
incorr
geronimo-config-1.0.xsd incorrectly documents that classes can be
comma-separated inside a a filter element
---
Key: GERONIMO-1824
URL: http://issues.apache.org/jira/browse/GE
Aaron Mulder wrote, On 4/10/2006 10:33 AM:
I vote we plan to freeze on a Monday rather than a Friday, so we get
the weekend to cram in the last bits. :) I know there are a still
ton of JIRAs with my name on them for 1.1.
I'm a little worried that there have been some showstopper bugs in 1.1
t
[ http://issues.apache.org/jira/browse/GERONIMO-1790?page=all ]
John Sisson reassigned GERONIMO-1790:
-
Assign To: Dain Sundstrom (was: John Sisson)
> Long Geronimo path and file names cause problems on Windows
> -
Aaron Mulder wrote, On 4/8/2006 5:06 PM:
So I'm putting some stuff into 1.1, some of which is related to config
IDs and some of which is not.
My question is, for the stuff unrelated to config IDs, should I be
merging to HEAD right away? Or is it going to be easier if I don't
and we merge "ever
Thanks Rainer. But I think 5.5.15 will be the one for 1.1. But
possibly 5.5.17 for 1.2 ;-)
Jeff
Rainer Jung wrote:
> Just for your information: 5.5.16 was released a couple of weeks ago,
> but has some problems with de delivered packaginf of examples app under
> windows.
>
> 5.5.17 is expected
Just for your information: 5.5.16 was released a couple of weeks ago,
but has some problems with de delivered packaginf of examples app under
windows.
5.5.17 is expected to be cut on friday and voted stable eventually 1-2
weeks later.
Jeff Genender wrote:
Yep...need to update the plan. Its
Yep...need to update the plan. Its updated in trunk.
Dave Colasurdo wrote:
> It appears that G1.1 is still using Tomcat 5.5.9
>
> http://svn.apache.org/repos/asf/geronimo/branches/1.1/etc/project.properties
>
>
>
> Wasn't a tomcat upgrade to 5.5.15 in plan for G1.1?? Perhaps I am
> confused
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-77?page=all ]
Daniel S. Haischt updated GERONIMODEVTOOLS-77:
--
Attachment: geronimo-simple-jsp.7z
The attached flash movie shows how to exactly reproduce the issue. You have to
use Seve
The WTP adapter for Geronimo resists to add a simple web project
Key: GERONIMODEVTOOLS-77
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-77
Project: Geronimo-Devtools
Type: Bug
Components
It appears that G1.1 is still using Tomcat 5.5.9
http://svn.apache.org/repos/asf/geronimo/branches/1.1/etc/project.properties
Wasn't a tomcat upgrade to 5.5.15 in plan for G1.1?? Perhaps I am
confused with the plans for trunk.. ??
Thanks
-Dave-
Chris Cardona wrote:
Hello All (Aaron, Joe, Paul),
I would like to work on a new portlet for the console
which can be used to view/explore the contents of the
embedded LDAP server (Apache DS). This can be added
under Misc > Embedded LDAP Server. I plan to use Dojo
javascript toolkit and DWR to a
Hi Guillaume,
I have tried all that you suggested but I still get the following error.
Any idea when does this happen.
Thanks
Soumadeep
ERROR:
java.lang.Exception:
http://java.sun.com/xml/ns/jbi/management-message";
version="1.0
">
deploy
FAILED
ERROR
http://java.sun.com/xml/ns/jbi/mana
On 4/10/06, ErinO <[EMAIL PROTECTED]> wrote:
>
> Hi, James:
>
> Thanks for the explanation. The configuration flag will do for my case.
>
> But I thought the purpose for the durable topic is to remove the order
> dependency between the producer and the consumer.
To loosely couple producers and con
I vote we plan to freeze on a Monday rather than a Friday, so we get
the weekend to cram in the last bits. :) I know there are a still
ton of JIRAs with my name on them for 1.1.
I'm a little worried that there have been some showstopper bugs in 1.1
that were only found and addressed in the last
Hi All,
for those struggling with Windows file naming limitation. I found deleting those file is a royal
pain as Windows can not point directly to the files already generated.
To delete those files and directories exceeding the 254 chars you can use the old DOS command
"subst". This command wi
I have used the "provided" scope in almost all the application poms.
The scope prevents from bundling all dependencies jars from the pom
into app's WEB-INF/lib. Only those jars that are really needed to be
bundled are explictly specified in the pom with no scope element set.
Cheers
Prasad
On 4/9/
Multiple durable topics don't work with network of brokers
--
Key: AMQ-687
URL: https://issues.apache.org/activemq/browse/AMQ-687
Project: ActiveMQ
Type: Bug
Components: Broker
Versions: 4.0 RC 2
E
I'm very excited about introducing AJAX functionality into the admin
console so I'm glad you brought this up. I think Dojo's BSD license
makes it OK for Geronimo and IIUC Apache Myfaces is planning to use it
for their AJAX controls. We should also keep an eye on kabuki, which
is a project in the Ap
Kevan,
How are we doing with CTS? Any news (good or bad) ?
Matt
+1
Guillaume Nodet wrote:
Hi everybody,
I have compiled a M1 release yesterday. Please take some time to
download and test it under your environment before voting it.
The maven artifacts are available at
http://people.apache.org/~gnodet/incubator-servicemix-3.0-M1/incubator-servicemix/dist
I was travelling yesterday so apologies for the late reply.
Aaron Mulder wrote:
So I'm putting some stuff into 1.1, some of which is related to config
IDs and some of which is not.
My question is, for the stuff unrelated to config IDs, should I be
merging to HEAD right away? Or is it going t
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-76?page=all ]
Daniel S. Haischt updated GERONIMODEVTOOLS-76:
--
Attachment: geronimo-axis-err.7z
The attached flash movie shows how to exactly reproduce the issue. You have to
use Seven
[ http://issues.apache.org/jira/browse/GERONIMO-1740?page=all ]
Anita Kulshreshtha updated GERONIMO-1740:
-
Attachment: m2-plugins.patch
geronimo.patch
>From the discussion at :
http://us.f317.mail.yahoo.com/ym/ShowLetter?MsgId=73_
Geronimo Fails if deploying a 'Bottom Up Web Service'
-
Key: GERONIMODEVTOOLS-76
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-76
Project: Geronimo-Devtools
Type: Bug
Components: eclipse-plugin
Jacek, and others
I have been thinking about what to include in the plan.xmls that
will provide an overview of the dependencies needed by a configuration.
Earlier I was leaning towards only listing the direct dependencies, but
that would not be a great documentation! For example in system
config
[ http://issues.apache.org/jira/browse/GERONIMO-1804?page=all ]
Andrey Pavlenko updated GERONIMO-1804:
--
type: Bug (was: Improvement)
> The name of JNDI/RMI service provider is hardcoded in the sources.
>
Hi Jeff,
On 6 Apr 2006, at 17:31, Jeff Genender wrote:
But I *think*, you can shut off the gbean as I explained in my last
email, then redeclare it in the config.xml.
Here is an example of a new ConnectorGBean that is declared in the
Tomcat configuration section of the config.xml:
Thanks fo
Project: Apache Geronimo
Status: Open
Assignee: Unassigned
Geronimo Info: Patch Available
Total: 25 items
DATE UPDATED KEY SUMMARY
Dec 18 2005 - GERONIMO-1381 - [Daytrader] Removed unused code
Dec 22 2005 - GERONIMO-1400 - modularize daytrader deployment plan
Jan 3 2
Hi David,
Sorry, I must not have explained myself well enough. The problem is
in the generation of the xmlbeans:
The first thing to note is that the namespace has changed in javaee5. It was:
http://java.sun.com/xml/ns/j2ee
but is now:
http://java.sun.com/xml/ns/javaee
If you generate
37 matches
Mail list logo
