[JBoss Web Services Development] - New dev: Problem building stack-native
by karypid
Hi,
I've just successfully built JBossWS-CXF trunk and now need to build JBossWS-Native trunk. With exactly the same environment (WinXP-32 system, Sun JDK 1.6.0_16, Maven 2.2.1) I get an error while building the SAAJ module of Native. I've configured by JBoss AS 5.1.0 location and running "ant deploy-jboss510" fails, saying something about not being able to execute the java compiler:
| D:\cxf-dev\projects\jbossws-native-trunk>ant deploy-jboss510
| Buildfile: build.xml
|
| target-jboss510:
|
| os-init:
|
| mvn-settings:
| [mkdir] Created dir: D:\cxf-dev\projects\jbossws-native-trunk\target
| [exec] [INFO] Scanning for projects...
| [exec] [INFO] Reactor build order:
| [exec] [INFO] JBoss Web Services - Stack Native
| [exec] [INFO] JBoss Web Services - Stack Native SAAJ
| [exec] [INFO] JBoss Web Services - Stack Native JAX-RPC
| [exec] [INFO] JBoss Web Services - Stack Native JAX-WS
| [exec] [INFO] JBoss Web Services - Stack Native JAX-WS Ext
| [exec] [INFO] JBoss Web Services - Native Server
| [exec] [INFO] JBoss Web Services - Stack Native Client
| [exec] [INFO] JBoss Web Services - Stack Native Management
| [exec] [INFO] JBoss Web Services - Stack Native Resources
| [exec] [INFO] Searching repository for plugin with prefix: 'help'.
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] Building JBoss Web Services - Stack Native
| [exec] [INFO] task-segment: [help:effective-settings] (aggregator-style)
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] [help:effective-settings {execution: default-cli}]
| [exec] [INFO] Effective-settings written to: D:\cxf-dev\projects\jbossws-native-trunk\target\ef
| fective-settings.xml
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] BUILD SUCCESSFUL
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] Total time: 3 seconds
| [exec] [INFO] Finished at: Tue Nov 10 14:21:43 EET 2009
| [exec] [INFO] Final Memory: 10M/18M
| [exec] [INFO] ------------------------------------------------------------------------
| [echo]
| [echo] jboss500.home=${profiles.profile.properties.jboss500.home}
| [echo] jboss501.home=${profiles.profile.properties.jboss501.home}
| [echo] jboss510.home=D:\cxf-dev\runtime\jboss-5.1.0.GA
| [echo] jboss520.home=${profiles.profile.properties.jboss520.home}
| [echo] jboss600.home=${profiles.profile.properties.jboss600.home}
|
| prepare:
|
| init:
| [echo] java.version=1.6.0_16
| [echo] version.id=3.2.2-SNAPSHOT
| [echo] integration.target=jboss510
|
| undeploy-jboss510:
| [delete] Deleting directory D:\cxf-dev\runtime\jboss-5.1.0.GA\server\default\deploy\jbossws.sar
| [delete] Deleting directory D:\cxf-dev\runtime\jboss-5.1.0.GA\server\default\deploy\juddi-service
| .sar
|
| prepare-deploy:
| [echo]
| [echo] mvn.bat package assembly:directory
| [echo]
| [exec] [INFO] Scanning for projects...
| [exec] [INFO] Reactor build order:
| [exec] [INFO] JBoss Web Services - Stack Native
| [exec] [INFO] JBoss Web Services - Stack Native SAAJ
| [exec] [INFO] JBoss Web Services - Stack Native JAX-RPC
| [exec] [INFO] JBoss Web Services - Stack Native JAX-WS
| [exec] [INFO] JBoss Web Services - Stack Native JAX-WS Ext
| [exec] [INFO] JBoss Web Services - Native Server
| [exec] [INFO] JBoss Web Services - Stack Native Client
| [exec] [INFO] JBoss Web Services - Stack Native Management
| [exec] [INFO] JBoss Web Services - Stack Native Resources
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] Building JBoss Web Services - Stack Native
| [exec] [INFO] task-segment: [package]
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] [antrun:run {execution: validate-jboss-home}]
| [exec] [INFO] Executing tasks
| [exec] [echo]
| [exec] [echo] profile=${jbossws.integration.target}
| [exec] [echo] jboss.home=${jboss.home}
| [exec] [echo]
| [exec] [INFO] Executed tasks
| [exec] [INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
| [exec] [INFO] Preparing source:jar
| [exec] [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
| [exec] [INFO] [antrun:run {execution: validate-jboss-home}]
| [exec] [INFO] Executing tasks
| [exec] [echo]
| [exec] [echo] profile=${jbossws.integration.target}
| [exec] [echo] jboss.home=${jboss.home}
| [exec] [echo]
| [exec] [INFO] Executed tasks
| [exec] [INFO] [source:jar {execution: attach-sources}]
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] Building JBoss Web Services - Stack Native SAAJ
| [exec] [INFO] task-segment: [package]
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] [antrun:run {execution: validate-jboss-home}]
| [exec] [INFO] Executing tasks
| [exec] [echo]
| [exec] [echo] profile=${jbossws.integration.target}
| [exec] [echo] jboss.home=${jboss.home}
| [exec] [echo]
| [exec] [INFO] Executed tasks
| [exec] [INFO] [resources:resources {execution: default-resources}]
| [exec] [WARNING] Using platform encoding (Cp1253 actually) to copy filtered resources, i.e. bui
| ld is platform dependent!
| [exec] [INFO] Copying 3 resources
| [exec] [INFO] [compiler:compile {execution: default-compile}]
| [exec] [INFO] Compiling 28 source files to D:\cxf-dev\projects\jbossws-native-trunk\modules\saa
| j\target\classes
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [ERROR] BUILD FAILURE
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] Compilation failure
| [exec] Failure executing javac, but could not parse the error:
| [exec] The system cannot find the path specified.
| [exec]
| [exec]
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] For more information, run Maven with the -e switch
| [exec] [INFO] ------------------------------------------------------------------------
| [exec] [INFO] Total time: 3 seconds
| [exec] [INFO] Finished at: Tue Nov 10 14:21:48 EET 2009
| [exec] [INFO] Final Memory: 16M/29M
| [exec] [INFO] ------------------------------------------------------------------------
|
| BUILD FAILED
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264804#4264804
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264804
14 years, 7 months
[Embedded JBoss Development] - Re: JbossWS in embbeded
by manuel.chinea
Hi,
i applied the patch in the jira ticket https://jira.jboss.org/jira/browse/EMB-61. I checked the code for the system property java.endorsed.libs. I changed the line in ServerTestCase.java
final File lib = new File(jbossHome,"endorsed");
to
final File lib = new File(jbossHome,"lib");
so the path were something like this: ...lib/endorsed.
Then i ran the test with no luck.
I was curious about the java.endorsed.dirs property and what jboss does with it. I put an iteration over the jboss config properties after the server.start() and saw the property jboss.bootstrap.url is set to server/default/conf/bootstrap.xml, aren't we running in the "all" config?
The code i put in the ServerTestCase.startEmbedddedASAndSetNamingContext() method, after server.start() is:
Map<String, String> props = server.getConfiguration().getProperties();
for (Iterator iterator = props.keySet().iterator(); iterator.hasNext();)
{
String key = (String) iterator.next();
log.info("key[" + key + "],value[" + props.get(key) + "]");
}
Also saw the java.endorsed.libs is not modified in jboss, according to the logs in my run.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264803#4264803
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264803
14 years, 7 months
[JBoss OSGi Development] - Re: Service integration with MC
by alesj
I'm actually wondering what's the best or proper way to expose or use this services in MC.
What should be the keys that we expose or match.
"alesj" wrote :
| * Service --> MC
|
In OSGi service we expose classes and properties.
Probably the key could look something like this:
* org.jboss.acme.X,org.jboss.acme.Y;(a=b)
a set of FQNs and a filter.
Only matching services that expose all the FQNs and match the filter.
Perhaps if there are no properties, we could directly expose service under registered classes?
"alesj" wrote :
| * MC --> Service
|
This looks easier from matching pov - simply do an intersection on the contexts that type match given FQNs (classes).
But how to mock (or even get) beans bundle?
Where this mock could be done, what about its "using bundles"?
Only count this in previous mock bundle, but ignore plain MC bean injection / usage?
"adrian(a)jboss.org" wrote :
| The proper way to do this would be to push the OSGi Filter into kernel project
| and use the MDR INSTANCE scope as the attributes.
| There would be a gotcha in that OSGi expect attributes to have case insensitive names,
| but we would only have to enforce that for OSGi created services.
|
Or what exactly did you have in mind here?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264706#4264706
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264706
14 years, 7 months
[JBoss Microcontainer Development POJO Server] - Re: AS weld-int
by kabir.khan＠jboss.com
As discussed privately I have changed things a bit. Here's the current state of play.
In the deployers, I create WeldKernelControllerContexts for the MC beans if they are part of a deployment that contains weld deployments. The WeldKernelControllerContext has a reference to the BeanManager which is then used for injection from Weld to MC beans.
Only MC beans with the @WeldEnabled annotation are available for injection from MC to Weld (you can/should of course use qualifier annotations etc. in addition to this). I created a WeldEnabled annotation plugin to handle this annotation and add the beans to the McFromWeldRegistry. This means that @WeldEnabled MC beans that are not part of a deployment containing Weld beans are available for injection to Weld beans in later deployments.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264682#4264682
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264682
14 years, 7 months
[Embedded JBoss Development] - Re: JbossWS in embbeded
by ALRubinger
Looks still outta-sync.
/home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[30,23] package javax.validation does not exist
|
| /home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[31,23] package javax.validation does not exist
|
| /home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[54,9] cannot find symbol
| symbol : class ValidatorFactory
| location: class org.jboss.as.jpa.builder.JPA2CEMFBuilder
|
| /home/deployer/.hudson/jobs/jboss-embedded/workspace/jbossas/ejb3/src/main/org/jboss/as/jpa/builder/JPA2CEMFBuilder.java:[54,50] cannot find symbol
| symbol : variable Validation
| location: class org.jboss.as.jpa.builder.JPA2CEMFBuilder
S,
ALR
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264638#4264638
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264638
14 years, 7 months