Hi,
Rickard �berg wrote:
> Rolando Rivera wrote:
> > I downloaded the new version of EJX and my complements to you, looks very
>nice. Know you have both jboss-xml and ejb-jar.xml under the same document. Which
>brings me to my question, How do I configure jaws.xml. There is not apparent new
>jaws.xml document type.
>
> ToDo :-) it's coming..
>
> /Rickardjava.lang.
I downloaded the new EJX and ran it from its own bin file ...
java -jar ejx.jar ... and got these messages:
ClassNotFoundException: org.jboss.ejb.metadata.Configuration
java.lang.ClassNotFoundException: org.jboss.ejb.metadata.Configuration
java.lang.ClassNotFoundException: org.jboss.ejb.metadata.StatefulSessionInstance
In the notes I found this:
>This plugin primarily edits jar-files that contains EJB 1.1 XML files.
>However, if you want you can edit XML-files that have not been packaged. In this case
>there
>are two options.
>If you decide to call it "ejb-jar.xml" then the plugin will assume that it is in a
>directory META-INF (i.e. as it would have been in a jar-file), and that
>all classes are available from the parent directory.
The editor must be started from its bin directory, unless I miss something. But it
contains no means for switching to another
directory .... also where do we call the file we want to edit ejb-jar.xml?
>This lets the plugin locate the classes that your beans are made of, and may thus
>show more info in the GUI, such as
> a list of methods in the container-transaction listing. Also, some wizard-style
>functionality is based on the plugins' ability
> to introspect your EJB-classes. This functionality will not be able if the plugin
>cannot locate these classes.
Seems to me that EJX can never locate classes ...
I make these points as someone entirely fresh to these tools. Six months from now it
all might look obvious to me.
As I am sure it no doubt looks obvious to many of the list members currently. For the
moment I think EJX badly
needs some coherant help or a user manual or a HOW-TO. No point writing editors
that are so incomprehensible
and so almost completely undocumented that people keep doing things by hand. And
where not even its own author
uses it. Even I am confused ;)
Another bad implication of this lack of documentation is that it gets propogated
through other parts of jBoss
help and documentation. For example, in the 'Getting Started' documents there is the
comment: "jBoss does
have an XML editor, which runs like this: ... " But there is no indication of HOW
one must use it to create
the ejb-jar.xml file described In other words, the ESSENTIAL problem is ignored,
while assuming that the problem
is solved! Contrast this to the DETAIL that Sun provides with its examples, including
step-by-step instructions
for using its Wizards and DeploymentTool!
Regards
Fred
>
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
