message-destination-link elements with path info don't work.
Key: GERONIMO-767
URL: http://issues.apache.org/jira/browse/GERONIMO-767
Project: Geronimo
Type: Bug
Components: deployment
Versions:
[
http://issues.apache.org/jira/browse/GERONIMO-768?page=comments#action_12315970
]
David Jencks commented on GERONIMO-768:
---
Should this go into M4?
doc/lit wrapped ws operation results in NPE if method has no parameters
So I took a look at the web console. There are two main changes I'd like
to make before we go live with it.
1) Combine the framework and standard web apps into one. Currently
the framework holds the Pluto engine and page framing and so on,
while the standard holds all the actual portlets.
A tagged version of the TranQL connector has been uploaded to the
Codehaus repo.
tranql-connector-1.0-20050716.rar
--
Jeremy
So after looking at the web console code and the JSR-77 spec, I
got the idea in my head that we could use a management API made up of
actual classes and interfaces, instead of object names and attribute
names. This is not meant to replace JSR-77 as a portable interface across
servers
Attempting to download tranql-connector-1.0-20050716.jar.
WARNING: Failed to download tranql-connector-1.0-20050716.jar.
The build cannot continue because of the following unsatisfied dependency:
tranql-connector-1.0-20050716.jar
Thanks,
Aaron
On Sat, 16 Jul 2005, Jeremy Boynes wrote
Aaron Mulder wrote:
Can you put up a JAR as well as the RAR? I think they need to
have the same version String. I got the RAR OK, but I'm getting a failure
in Geronimo Derby Connector:
Done - sorry about that, used the wrong goal.
--
Jeremy
Great, it worked now, thanks.
Aaron
On Sat, 16 Jul 2005, Jeremy Boynes wrote:
Aaron Mulder wrote:
Can you put up a JAR as well as the RAR? I think they need to
have the same version String. I got the RAR OK, but I'm getting a failure
in Geronimo Derby Connector:
Done -
I think it might be possible to divide this proposal into several
pieces, and have different opinions about different aspects of them.
1). supply management interfaces for our important gbeans. these
are java interfaces that are exposed by the gbean through its gbean
info. These would be
On Sat, 16 Jul 2005, David Jencks wrote:
I think it might be possible to divide this proposal into several
pieces, and have different opinions about different aspects of them.
1). supply management interfaces for our important gbeans. these
are java interfaces that are exposed by the
10 matches
Mail list logo
