Jax-WS - wsimport -p option (package)

I'm using the -p option to specify a package name. The wsimport code places ALL the generated .java files in this one package.
My question is: How dangerous is it to refactor some of the classes into different packages?
It looks like a lot of the Javadoc annotations may break, but it looks like the other annotations will be okay. I should add; all the WS annotations reference other classes w/o and package statements, but that may be b/c they all live in the same package.
Should I be updating the annotations as well?
All help is very welcome,
Frank

It is pretty safe to refactor generated classes into as many packages as you want. Also you can remove all javadoc annotations and XMLs without breaking anything. IMO touching generated code is not a good idea, in case you want to re-generate the code again then you have to do the same refacroting again.

Similar Messages

Generic Connection Framework Optional Package for J2SE

i have learnt that the Generic Connection Framework Optional Package can be used to make J2SE able to use J2ME classes. However, how can i implement the package so that i can do so.
Thank you for your advice.

http://developers.sun.com/techtopics/mobility/midp/articles/genericframework/

Optional Package - startup behavior

Hi guys,
Hi have an optional package (similar to a shared library) that is referenced by two different applications. This optional package is a jar file.
When I 've a web application (WAR) I know that WebLogic will use the exploded directory in .../tmp/_WL_user to load the application, but which is the behavior when i'm using a jar file?
Thanks

Hi Amol,
WebLogic jDriver for Oracle fully supports the JDBC 2.0 Optional Package API for
distributed transactions.
Laurent Goldsztejn
Developer Relations Engineer
BEA Support
"amol desai" <[email protected]> wrote:
>
Do you support the optional package features? If yes , how?

Optional package

How can I add optional package (example the MMAPI) for a phone that does not implement it natively?
is it possible?
Example we have a P900 that does not support MMAPI for video... is it possible to extend its possibilities?
Many thanks
Greg

(oops, error in previous post... wrong tag...)
Hi Greg,
In theory this would be possible, yes... However, this might be a lot of work because you will have to develop it in Java (as you cannot use a native language like C, there's no public native interface). This means that you will need to write things like playing back a video (from a stream), etc etc... All in Java; with its limitations. Sound playback (probably?) can be covered by the MMAPI (so you might need to extend a few pieces from MMAPI and use that within your Java Video MMAPI).
Cheers

Optional package feature supported

Do you support the optional package features? If yes , how?

Hi Amol,
WebLogic jDriver for Oracle fully supports the JDBC 2.0 Optional Package API for
distributed transactions.
Laurent Goldsztejn
Developer Relations Engineer
BEA Support
"amol desai" <[email protected]> wrote:
>
Do you support the optional package features? If yes , how?

Restart deployment (.ear) does not load optional package

Hello everybody,
In our 10.3.5 WLS domains, we are using optional packages for sharing libraries between applications see [http://docs.oracle.com/cd/E24329_01/web.1211/e24368/libraries.htm|Creating Shared Java EE Libraries and Optional Packages]
The problem is that if I redeploy the library I have to redeploy the deployment. This issue only happens with the applications packaged as *.ear*. If the application has been deployed as a .war, with restarting the deployment is enough.
Would be possible to load the referenced library from an *.ear* just restarting the deployment?
Thanks in advance,
Luis

Thanks Vimala,
I have 1 ear project and 1 web service project.
Attached my ant output when I run the build.xml.
C:\wivWorkSpace\wivApp>ant build -Dworkspace=C:/wivWorkSpace
Buildfile: build.xml
init.env:
init.typedefs:
init:
build:
[echo] project.name = wivApp
init:
build:
[echo] wivWS: C:\wivWorkSpace\wivWS\build.xml
BUILD SUCCESSFUL
Total time: 23 seconds
C:\wivWorkSpace\wivApp>ant build -Dworkspace=C:/wivWorkSpace archive
Buildfile: build.xml
init.env:
init.typedefs:
init:
build:
[echo] project.name = wivApp
init:
build:
[echo] wivWS: C:\wivWorkSpace\wivWS\build.xml
init.env:
init.typedefs:
init:
stage:
[delete] Deleting directory C:\wivWorkSpace\wivApp\.staging
[mkdir] Created dir: C:\wivWorkSpace\wivApp\.staging
[copy] Copying 13 files to C:\wivWorkSpace\wivApp\.staging
BUILD FAILED
C:\wivWorkSpace\wivApp\build.xml:192: The following error occurred while executing this line:
jar:file:/C:/BEAPLA%7e1/WEBLOG%7e1/workshop/lib/wlw-antlib.jar!/com/bea/wlw/antlib/antlib.xml:91: The follow
ng this line:
C:\wivWorkSpace\wivApp\build.xml:204: The following error occurred while executing this line:
Target `stage.to.ear' does not exist in this project.
Total time: 15 seconds

Use of Optional Packages

Hello,
I would like to know if there is any way to include in my application an optional package just in case the device does not have it in its Runtime Environment.
What I was thinking is more like including all the classes from a jar file (e.g j2me-ws.jar JSR172) in my application's jar file.
Thanks in advance,
Nick

Hi there,
The reason it did not work is because it failed to decode doubles. But once I replaced the doubles in my WS with Strings everything went smoothly.
Note: I was using CLDC1.1 so doubles should have been supported(The WTK emulators worked just fine, but the Nokia and Sony Ericsson emulators didn't).
SO for everybody out there: try not to use doubles in your WS for the moment :) (WTK 2.2)
Cheers, Nick

Confusion with JDBC Optional Package for CDC.

I am somewhat confused as to where this optional package fits.
1. Is the implementation of this optional package to be COMPLETELY supplied by the database vendor(e.g. hsqdb, Oracle)?
OR
2. Is there an implementation available from Sun?
OR
3. Has Sun simply not released an implementation yet?
OR
4. Am I completely missing something here and losing my mind :)
OR
Is the JVM supposed to supply the implementation?
Thanks for any enlightenment.
J

The actual specification can be written without actually talking to a database (the spec is mostly interfaces). However, you are write in that along with these classes (which must pass the TCK) the database vendor must provide the rest. Unlike normal java.sql where there is a DriverManager class, that is not the case in JSR-169.

Optional Package class reference at server startup...gives class not found

I have a enterprise app having a webservice..the webservice (servlet) gets instantiated on server startup…It has reference of a class which is an optional package
All the manifest entries are correctly added to the ear..manifest.mf..
When the servlet is initialized at startup.. gives me a class not found error…
However, the app works fine..this is just a one time error(whenever the app is deployed fresh..)..
Any help would be appreciated
Thanks

I have a enterprise app having a webservice..the webservice (servlet) gets instantiated on server startup…It has reference of a class which is an optional package
All the manifest entries are correctly added to the ear..manifest.mf..
When the servlet is initialized at startup.. gives me a class not found error…
However, the app works fine..this is just a one time error(whenever the app is deployed fresh..)..
Any help would be appreciated
Thanks

Is it possible to redeploy Optional Package(J2EELibrary)without versioning?

Currently, I decided to use Optional Package feature for one of our common shared jar file as it is referenced by our multiple applications (ear files). I can understand, how I can deploy multiple version of the optional package in order for the referencing application to use it. I am planning to use this version feature for optional package in our Production Environment. However, my issue is I don't want to use this version feature in our development environment as it involves more work for the developers (overhead on the developers to specify the optional package version in their referencing application). Is there any way I can redeploy optional package in development environment? I can only redeploy only after undeploying all my 6 referencing applications, which is taking more time.

Does any one have an example to implement Optional Package and versioning it?

Persistence Layer deployed as Optional Package

Environment:
- WebLogic 11g which consequently means EJB 3.0
- Application has 3 modules: Web (referencing EJB and Persistence), EJB (referencing Persistence) and Persistence
Could I deploy my persistence layer as an Optional Package or does it have to be a Shared Library?
The reason I'm asking is that when I try to deploy my EJB module, WLS can't find the persistence unit being inject to it:
Unable to deploy EJB: StocksBean from BLayer-1.0.0-SNAPSHOT.jar: No persistence unit named 'internalAppsPU' is available in scope BLayer-1.0.0-SNAPSHOT.jar. Available persistence units: []
Persistence module is basically a JAR file deployed as an Optional Package with following in its Manifest:
Extension-Name: PersistenceLayer
Implementation-Version: 1.0.0-SNAPSHOT
Specification-Version: 1.6
in EJB's code I have:
@Stateless(name="StocksBean", mappedName="StocksBean")
public class StocksBean implements Stocks {
@PersistenceContext(unitName = "internalAppsPU")
private EntityManager em;
and in EJB's JAR file I have:
pLayer-Extension-Name: PersistenceLayer
pLayer-Implementation-Version: 1.0.0-SNAPSHOT
pLayer-Specification-Version: 1.6
I'm deploying these one by one and not as an Application.

Hi Arun,
Thank you so much for taking time and responding. I'm still having the same issue.
You see, I had the exact same problem when my persistence Entities were in the same Jar file as EJBs and I found out the problem was the name of the persistence.xml file (which was "Persistence.xml") and also the version of the namespace used in the XML file which conflicted with version of JPA's spi (version of JPA's spi in JEE1.6 is 1.0 and I was using version 2.0 of the namespace).
However, I got that fixed and now I'm trying to separate the layers (just moved the files around and didn't change the content). Here is what I have so far:
Name of Persistence Layer's JAR file: PLayer.jar
Manifest of Persistence Layer's JAR file:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: bm03043
Build-Jdk: 1.6.0_18
Extension-Name: PersistenceLayer
Implementation-Version: 1.0.0-SNAPSHOT
Specification-Version: 1.6
Name of EJB's JAR file: BLayer-1.0.0-SNAPSHOT.jar
Manifest of EJB's JAR file:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: bm03043
Build-Jdk: 1.6.0_18
Extension-List: PLayer
PLayer-Extension-Name: PersistenceLayer
PLayer-Implementation-Version: 1.0.0-SNAPSHOT
PLayer-Specification-Version: 1.6
I didn't know that Extension-List entry in EJB's jar file should match with the name of Persistence layer's jar file.
As for deployment, I deploy the Player and then EJB.
Appreciate any input.
Edited by: Keibi on Apr 26, 2012 11:30 AM

Link to download the RMI optional package reference implementation

Hi,
I could not find any links for downloading the reference implementation of the RMI optional package. Is this package available for download? Pls give me the link if you find the same. Thanks in advance..
regards,
Anand
Edited by: Anand.Raman on Apr 22, 2009 2:48 AM

This is a deprecated URL that will be retired soon.
You can download this RI here:
https://java-partner.sun.com/support/login.action
Assuming that you have a Java Partner login.

Optional packages

hi,
i'm new in J2me, and trying to understand which phone supports what.
Are these apis and supports:
* Mobile Media API for J2ME
* Wireless Messaging API
* Support for Multimedia Messaging Service (MMS) in the WMA console
* Simulated Bluetooth environment for JSR 82 support
* Network monitor support for MMS and Bluetooth
installable or located in phones like midp apis?
if they are installable, why can't i find any instructions?
if they are not installable why do we call them optional packages?

They are not installable. They are optional because a phone doesn't necessarilly need to have them in order to be MIDP compliant. You have to check each device's specifications to see which of these APIs it supports.
shmoove

Optional Package - does it decrease memory size for war

We have around 10+ war files running within WLS 10.3.4.
Each of the war files are around 40 megs each.
I am looking at building a frameworks jar (via Apache Shade) and make that jar an optional package (which includes all my 3rd party frameworks like Spring/CXF/etc).
By deploying this jar as an optional package, I can cut the size of the war file in half.
The question is, does this really save the size of the war in memory?
When I deploy a war with a reference to an optional package, does WLS explode the war, import the optional package, and rebuild the war for deployment so that in the end, it equates to the same size war as if I had never utilized the optional package? The documentation seems to allude to this.
I want to know (before I do all the work), if decreasing the size of the war by excluding 3rd party libraries into an optional package will actually reduce the size of memory for each war.
Thanks,
Jay

One option is: use the c6/c7/c8 parameters if the INSTALL APDU. Start with a high value and work your way down. That will tell you how much mem you have.
The other option is to load an applet that allocates a large byte array. Work your way down and when it can successfuly allocate the memory, that's whats available on the card for you to use.
Third option: Get a 2.2 card and just call the API ! ! !

Jeode and CDC RMI optional package?

Does anybody know if Jeode implements the RMI optional package specification for J2ME Personal Profile 1.0? If they don't, is there any alternative to Jeode that does? Also, have they implemented the JDBC optional package?

WSDD contains a beta version of the RMI optional package with the certified one awaiting submission to the web updates (Eclipse way for getting new features).
The JDBC optional package (JSR-169) has not submitted a final spec, RI or TCK and therefore IBM cannot provide an implementation. Once a TCK is available there will likely be and implementation and a driver from the DB2 group.

Jax-WS - wsimport -p option (package)

Similar Messages

Maybe you are looking for