It seems you are exposing in your web service some methods
that maybe you should be expose.  I don't think the JBI API
is part of your service interface.  You can either disable the
jbi.xml generation using

                        <plugin>
                                <groupId>org.apache.servicemix.tooling</groupId>
                                <artifactId>jbi-maven-plugin</artifactId>
                        <version>${servicemix-version}</version>
                                <extensions>true</extensions>
                                <configuration>
                                        
<generateJbiDescriptor>false</generateJbiDescriptor>
                                </configuration>
                        </plugin>

but the problem will still appear at runtime when generating the wsdl.

So i would suggest that your use a protected method, or add some web services
annotations to hide the methods that should not be exposed.
Another way is to define service interface that will be exposed.
Take a look at the classes generated by the wsdl-first example : all you need
is to define an interface with a @WebService annotation, and also add this
annotation on your service implementation.

On 1/25/07, denisB <[EMAIL PROTECTED]> wrote:


gnodet wrote:
>
> The problem is that it expects a WSDL to generate the classes.
> If you want to start from a pojo, you need to remove the pom section
> which generate the classes.
>

I removed the plugin part
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
        ...
Is that the part I had to remove ?

Now I got this error

[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to generate jbi.xml

Embedded error: Unable to generate service unit descriptor!
<component-task-result
xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
        <component-name>null</component-name>
        <component-task-result-details>
                <task-result-details>
                        <task-id>deploy</task-id>
                        <task-result>FAILED</task-result>
                        <message-type>ERROR</message-type>

<task-status-msg><msg-loc-info><loc-token/><loc-message>org.codehaus.xfire.XFireRuntimeException:
Couldn't create type for property propertyNames on interface
javax.jbi.messaging.MessageExchange: Cannot create mapping for
java.util.Set, unspecified component type for interface
java.util.Set</loc-message></msg-loc-info></task-status-msg>
                        <exception-info>
                                <nesting-level>1</nesting-level>
                                <msg-loc-info>
                                        <loc-token />
                                        <loc-message>Couldn't create type
for property propertyNames on interface javax.jbi.messaging.MessageExchange:
Cannot create mapping for java.util.Set, unspecified component type for
interface java.util.Set</loc-message>

<stack-trace><![CDATA[org.codehaus.xfire.XFireRuntimeException: Couldn't
createtype for property propertyNames on interface
javax.jbi.messaging.MessageExchange: Cannot create mapping for
java.util.Set, unspecified component type for interface java.util.Set
        at
org.codehaus.xfire.aegis.type.DefaultTypeCreator.createCollectionType(DefaultTypeCreator.java:43)
        at
org.codehaus.xfire.aegis.type.java5.Java5TypeCreator.createCollectionType(Java5TypeCreator.java:138)



Here is my jsr181-su
http://www.nabble.com/file/5915/bridge-jsr181-su.rar bridge-jsr181-su.rar

--
View this message in context: 
http://www.nabble.com/noob-has-a-problem-with-JSR-181-tf3081863s12049.html#a8598269
Sent from the ServiceMix - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Reply via email to